OpenCTI’s data ingestion feature allowed user-supplied URLs to be requested without validation, using Axios with default settings that accept absolute URLs. The result is a semi‑blind SSRF: while the attacker may not receive the full response, the request can reach internal services and cause unintended actions. The primary impact is unauthorized access to internal resources and potential disruption of internal services.

All OpenCTI-Platform opencti deployments running a version older than 6.8.16 are affected. The vulnerability is fixed in release 6.8.16, so any earlier version is considered vulnerable.

The CVSS score of 7.7 indicates a high severity. EPSS is very low (<1%) and the vulnerability is not listed in KEV, suggesting a low current exploitation probability, but the potential impact is significant. An attacker can exploit the vulnerability by sending a crafted ingestion request through an internet-facing OpenCTI instance, triggering internal HTTP calls that may affect internal services. The risk is moderate to high in environments where the ingestion feature is exposed to untrusted users.