CVE-2026-32287

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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()".

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

Published

March 26, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit.
generic

Infinite Loop DoS in antchfx/xpath logicalQuery.Select() | SecurityInfinity

https://securityinfinity.com/research/infinite-loop-dos-in-antchfx-xpath-logicalquery-select
generic

GO-2026-4526 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4526
generic

x/vulndb: potential Go vuln in github.com/antchfx/xpath · Issue #4526 · golang/vulndb · GitHub

https://github.com/golang/vulndb/issues/4526
generic

Infinite loop in logicalQuery.Select() when boolean XPath expression evaluates to true · Issue #121 · antchfx/xpath · GitHub

https://github.com/antchfx/xpath/issues/121
github_commit Patch Available

commit afd4762cc342 (antchfx/xpath)

Patch available: antchfx/xpath v1.3.6 (contains commit afd4762cc342)

https://github.com/antchfx/xpath/commit/afd4762cc342af56345a3fb4002a59281fcab494

Vendor Advisories for CVE-2026-32287(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhosdt/opentelemetry-collector-rhel9:17761853792026-04-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-antchfx-xpath1.1.2-2 ... 1.3.6-1 (7 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-antchfx-xpath1.1.2-2 ... 1.3.8-1 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-antchfx-xpath1.3.3-1, 1.3.5-1, 1.3.6-1, 1.3.8-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-antchfx-xpath1.3.3-1, 1.3.5-1
  • every version up to 1.3.6-1: fixed in 1.3.6-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/antchfx/xpath—
  • every version up to 1.3.6: fixed in 1.3.6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 220 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 00:26 UTCEPSS rescore
  15. 2026-09-21 16:49 UTCOSV refresh
  16. 2026-09-20 20:15 UTCEPSS rescore
  17. 2026-09-20 20:15 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 19:27 UTCEPSS rescore
  20. 2026-09-17 19:30 UTCEPSS rescore
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-13 16:47 UTCEPSS rescore
  24. 2026-09-12 15:01 UTCEPSS rescore
  25. 2026-09-11 14:52 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 09:34 UTCEPSS rescore
  2. 2026-09-08 22:00 UTCEPSS rescore
  3. 2026-09-07 16:01 UTCEPSS rescore
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:11 UTCEPSS rescore
  8. 2026-09-02 13:26 UTCOSV refresh
  9. 2026-09-01 13:53 UTCEPSS rescore
  10. 2026-09-01 04:39 UTCEPSS rescore
  11. 2026-09-01 04:39 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 14:17 UTCEPSS rescore
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-19 17:03 UTCEPSS rescore
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 13:47 UTCEPSS rescore
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 10:06 UTCEG score recompute
  28. 2026-08-16 10:06 UTCVendor advisory
  29. 2026-08-16 02:14 UTCEPSS rescore
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-14 19:26 UTCVendor advisory
  32. 2026-08-14 06:24 UTCEG score recompute
  33. 2026-08-14 06:24 UTCVendor advisory
  34. 2026-08-13 22:00 UTCEPSS rescore
  35. 2026-08-12 20:41 UTCEG score recompute
  36. 2026-08-12 20:41 UTCVendor advisory
  37. 2026-08-12 13:50 UTCEPSS rescore
  38. 2026-08-11 20:48 UTCEG score recompute
  39. 2026-08-11 20:48 UTCVendor advisory
  40. 2026-08-11 03:50 UTCEG score recompute
  41. 2026-08-11 03:50 UTCVendor advisory
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-10 03:58 UTCVendor advisory
  44. 2026-08-09 16:57 UTCEG score recompute
  45. 2026-08-09 16:57 UTCVendor advisory
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-09 05:57 UTCEG score recompute
  48. 2026-08-09 05:57 UTCVendor advisory
  49. 2026-08-08 16:37 UTCEPSS rescore
  50. 2026-08-08 03:24 UTCEG score recompute
  51. 2026-08-08 03:24 UTCVendor advisory
  52. 2026-08-07 16:22 UTCVendor advisory
  53. 2026-08-06 18:45 UTCEG score recompute
  54. 2026-08-06 18:45 UTCVendor advisory
  55. 2026-08-06 13:46 UTCEPSS rescore
  56. 2026-08-06 00:51 UTCEG score recompute
  57. 2026-08-06 00:51 UTCVendor advisory
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 10:38 UTCEPSS rescore
  61. 2026-08-03 23:16 UTCEG score recompute
  62. 2026-08-03 23:16 UTCVendor advisory
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-03 02:24 UTCVendor advisory
  65. 2026-08-02 15:21 UTCEG score recompute
  66. 2026-08-02 15:21 UTCVendor advisory
  67. 2026-08-02 02:27 UTCEPSS rescore
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-07-30 16:28 UTCEPSS rescore
  70. 2026-07-30 01:30 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-25 14:17 UTCEPSS rescore
  75. 2026-07-24 14:17 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2026:9388

Frequently asked(5)

What is CVE-2026-32287?
CVE-2026-32287 is a high vulnerability published on March 26, 2026. 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()".
When was CVE-2026-32287 disclosed?
CVE-2026-32287 was first published on March 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32287 actively exploited?
CVE-2026-32287 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32287?
CVE-2026-32287 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32287?
A fix for CVE-2026-32287 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32287 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32287

Explore →

Is Your Infrastructure Affected by CVE-2026-32287?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs