Server-side request forgery in OpenCTI ingestion testers
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-295.
Summary
OpenCTI before 7.260604.0 has a server-side request forgery flaw in the ingestionJsonTester and ingestionCsvTester GraphQL mutations (CWE-918). An authenticated user with the INGESTION_SETINGESTIONS or CSVMAPPERS capability can make the OpenCTI server send HTTP requests to internal hosts and cloud metadata endpoints. The same code also disables TLS certificate verification by default (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 exists in OpenCTI's `ingestionJsonTester` and `ingestionCsvTester` GraphQL mutations. Authenticated users with the `INGESTION_SETINGESTIONS` or `CSVMAPPERS` capability can force the OpenCTI backend server to issue arbitrary HTTP requests to internal network hosts and cloud metadata endpoints. ### Details The testing functions for JSON and CSV ingestion mappings (`testJsonIngestionMapping`, `executeJsonQuery`) dispatched HTTP requests directly to user-supplied URIs without destination IP or hostname validation against private, loopback, or link-local address spaces. In addition, TLS certificate verification was disabled by default. ### Impact - **Vulnerability Class**: Server-Side Request Forgery (SSRF) (CWE-918), Improper Certificate Validation (CWE-295) - **Attacker Requirements**: Authenticated account holding `INGESTION_SETINGESTIONS` or `CSVMAPPERS` capabilities. - **Consequences**: - Scanning and fingerprinting internal services and network ports. - Querying internal-only HTTP services or cloud provider metadata services (e.g. AWS IMDS) from the OpenCTI server context. - Potential interaction with internal services (such as Elasticsearch, RabbitMQ, MinIO, or Redis) depending on network isolation and internal authentication configurations. ### Patches Fixed in OpenCTI **7.260604.0** with the implementation of a configurable URI deny list mechanism for ingestion feeds, as well as options to enforce TLS certificate validation. For more details on configuring ingestion protection, 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 | <7.260604.0 | >=7.260604.0 | Patch available | GHSA-gmv2-pc7f-c2qh |
- opencti Vendor— Affected <7.260604.0 Fixed in >=7.260604.0 Patch available GHSA-gmv2-pc7f-c2qh
Remediation
Upgrade OpenCTI to version 7.260604.0 or later, which adds a configurable URI deny list for ingestion feeds and options to enforce TLS certificate validation. See the OpenCTI URI Deny List documentation for configuring ingestion protection.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-gmv2-pc7f-c2qh opencti Fixed in >=7.260604.0 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-gmv2-pc7f-c2qh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences