libtaxii Server-Side Request Forgery vulnerabilityGHSA-836c-xg97-8p4h
CRITICALFix: TAXIIProject/libtaxii#247GHSA-836c-xg97-8p4h is a critical-severity (CVSS 9.8) Server-Side Request Forgery (SSRF) vulnerability in libtaxii. 3 public exploit references exist, so weaponization risk is real. A fix is available for libtaxii — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-836c-xg97-8p4h by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
libtaxiiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
"TAXII libtaxii through 1.1.117, as used in EclecticIQ OpenTAXII through 0.2.0 and other products, allows SSRF via an initial http:// substring to the parse method, even when the no_network setting is used for the XML parser. NOTE: the vendor points out that the parse method "wraps the lxml library" and that this may be an issue to "raise ... to the lxml group.""
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | libtaxii | all versions | 1.1.118pip install --upgrade 'libtaxii==1.1.118' |
Affected Products
opentaxiieclecticiqlibtaxiilibtaxii_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libtaxii, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libtaxii to 1.1.118 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-836c-xg97-8p4h is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is GHSA-836c-xg97-8p4h in your dependencies?
Find it across PyPI, including transitive dependencies.