CVE-2026-21887 is a server-side request forgery vulnerability in OpenCTI prior to version 6.8.16. The issue affects the platform’s data ingestion feature, which accepts user-supplied URLs without validating the destination and fetches them using the Axios HTTP client with its default behavior permitting absolute URLs. As a result, an authenticated attacker with access to ingestion configuration can cause the OpenCTI server to issue requests to arbitrary endpoints, including localhost, private-network services, and link-local addresses such as cloud metadata endpoints. The vulnerability is described as semi-blind because full response contents may not always be exposed to the attacker, but the attacker can still trigger requests and interact with reachable internal services. Supporting context indicates the vulnerable implementation performed axios.get on attacker-controlled URLs without destination validation, while the fix added hostname resolution and blocking of private and link-local IP ranges.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.