Server-side request forgery in OpenCTI JSON ingestion pagination
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
OpenCTI is affected before 7.260604.0. The JSON ingestion pagination feature takes the URL for the next page from the API response body using a user-configured JSONPath expression, and the server requests that URL without checking whether it points to private, loopback or cloud metadata addresses. An authenticated user holding the INGESTION_SETINGESTIONS capability can make the server send requests to arbitrary internal URLs (CWE-918). TLS certificate verification was also disabled by default on this path (CWE-295).
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary A Server-Side Request Forgery (SSRF) vulnerability in the JSON ingestion pagination feature allows authenticated users with the `INGESTION_SETINGESTIONS` capability to force the OpenCTI server to execute HTTP requests to arbitrary internal URLs. Unlike standard SSRF where the target URI is statically configured, the destination URL in this scenario is extracted dynamically at runtime from the API response body via pagination attributes, evading static feed configuration reviews. ### Details In the JSON ingestion pagination workflow, the URL for subsequent page requests is extracted from incoming API responses using a user-configured JSONPath expression (`pagination_with_sub_page_attribute_path`). The resulting URL was queried directly without validation against private IP ranges, loopback addresses, or cloud metadata endpoints. Furthermore, TLS certificate verification was disabled by default on this path. ### Impact - **Vulnerability Class**: Server-Side Request Forgery (SSRF) (CWE-918), Improper Certificate Validation (CWE-295) - **Attacker Requirements**: Authenticated user holding the `INGESTION_SETINGESTIONS` capability. - **Consequences**: - Exfiltration of cloud provider metadata and credentials (e.g. AWS/GCP metadata at `169.254.169.254`). - Accessing unauthenticated internal backend services (such as Elasticsearch, Redis, or RabbitMQ). - Internal network port scanning via response error behavior. - Evasion of feed configuration reviews, as the malicious target is only injected at runtime via pagination responses. ### Patches Fixed in OpenCTI **7.260604.0** with the implementation of a configurable URI deny list mechanism for ingestion feeds, as well as configuration options to enforce TLS certificate validation. For more details on configuring ingestion protections, see the [OpenCTI URI Deny List Documentation](https://docs.opencti.io/latest/usage/import/advanced-feed-configuration/?h=deny#uri-deny-list).
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | opencti (npm) | < 7.260604.0 | >= 7.260604.0 | Patch available | GHSA-w3h6-4frq-fgm7 |
- opencti (npm) Vendor— Affected < 7.260604.0 Fixed in >= 7.260604.0 Patch available GHSA-w3h6-4frq-fgm7
Remediation
Upgrade OpenCTI to 7.260604.0 or later. The fix adds a configurable URI deny list for ingestion feeds and options to enforce TLS certificate validation.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-w3h6-4frq-fgm7 opencti (npm) Fixed in >= 7.260604.0 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-w3h6-4frq-fgm7
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences