CVE-2026-32287 is a high-severity (CVSS 7.5) CWE-835 vulnerability in github.com/antchfx/xpath. A fix is available for github.com/antchfx/xpath — see the affected versions and patch details below.
Infinite loop in github.com/antchfx/xpath
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32287.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/antchfx/xpathReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Boolean XPath expressions that evaluate to true can cause an infinite loop in logicalQuery.Select, leading to 100% CPU usage. This can be triggered by top-level selectors such as "1=1" or "true()".
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/antchfx/xpath | all versions | 1.3.6go get github.com/antchfx/xpath@v1.3.6 |
Affected Products
xpathantchfxDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/antchfx/xpath, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/antchfx/xpath to 1.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32287 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift distributed tracing 3.9.3 | rhosdt/opentelemetry-collector-rhel9:1776185379 | RHSA-2026:9388 |
Frequently Asked Questions
Is CVE-2026-32287 in your dependencies?
Find it across Go, including transitive dependencies.