PatchTheCVECVE-2026-32287: Boolean XPath expressions that evaluate to true can cause an infinite loop in logicalQuery.Select, leading to
CVE-2026-32287 is a high-severity flaw (CVSS 7.5) affecting xpath. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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()".
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.5% (top 55%) |
| CISA exploited list | No |
| Weakness | CWE-835 |
| Published | 2026-03-26 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-32287?
xpath: upgrade to 1.3.6. Exact commands for each OS are on this page.
Is CVE-2026-32287 being exploited?
CVE-2026-32287 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-32287 affect?
CVE-2026-32287 affects xpath. Severity is high (CVSS 7.5). 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()".
How urgent is CVE-2026-32287?
Priority 48/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action