CVE-2024-8954: composiohq/composio · Missing Critical Step in Authentication
Affects composiohq/composioSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubcomposiohq/composiopkg:github/composiohq/composioOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately restrict API access to trusted IP ranges or VPNs to limit exposure. 2. Implement additional authentication mechanisms such as OAuth tokens or mutual TLS to supplement or replace x-api-key authentication. 3. Monitor API logs for anomalous or unexpected x-api-key values and unauthorized access attempts. 4. Apply network-level controls such as Web Application Firewalls (WAFs) to detect and block suspicious API requests. 5. Engage with composiohq for official patches or updates and plan for rapid deployment once available. 6. Conduct a thorough audit of all API keys and rotate them where possible. 7. Educate developers and administrators about the vulnerability and enforce secure coding and authentication validation practices. 8. Consider isolating or segmenting systems running composiohq/composio to contain potential breaches. 9. Prepare incident response plans specifically addressing unauthorized API access scenarios. 10. Regularly review and update security policies to ensure comprehensive API security.
Description
In composiohq/composio version 0.5.10, the API does not validate the `x-api-key` header's value during the authentication step. This vulnerability allows an attacker to bypass authentication by providing any random value in the `x-api-key` header, thereby gaining unauthorized access to the server.