Resource exhaustion via pre-auth body parsing in OpenCTI TAXII endpoint
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-400.
Summary
OpenCTI through versions before 7.260520.0 fully parses JSON request bodies on the TAXII 2.1 push endpoint before checking authentication. An unauthenticated remote attacker can send concurrent large requests, up to the default 50 MB body limit, to exhaust CPU and heap memory (CWE-400). This makes the GraphQL API unresponsive for all users, connectors and automated ingestors, and no credentials are required.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary The TAXII 2.1 push endpoint (`POST /taxii2/root/collections/:id/objects/`) fully parses the JSON request body **before** performing any authentication check. With a default body limit of 50 MB, an unauthenticated attacker can force the server to deserialize up to 50 MB of JSON per request. Sending concurrent requests saturates CPU and heap memory, degrading or denying service for all platform users with no credentials required. ### Impact - No credentials required: The attack surface is the public internet if the TAXII port is exposed, or any internal network segment that can reach the platform. - Service disruption: Repeated concurrent large-body requests exhaust Node.js heap, causing the GraphQL API to become unresponsive for all users, connectors, and automated ingestors. - Rate limiting bypass: Any rate limiting applied at the application layer runs post-auth and does not protect against unauthenticated pre-auth body parsing. - Cloud cost amplification: On auto-scaling infrastructure, the attack triggers unnecessary scale-out events increasing operational costs.
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.260520.0 | >=7.260520.0 | Patch available | GHSA-6crf-vqpj-hvr4 |
- opencti (npm) Vendor— Affected < 7.260520.0 Fixed in >=7.260520.0 Patch available GHSA-6crf-vqpj-hvr4
Remediation
Upgrade the opencti npm package to version 7.260520.0 or later.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-6crf-vqpj-hvr4 opencti (npm) Fixed in >=7.260520.0 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-6crf-vqpj-hvr4
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences