Impact Analysis

The vulnerability can cause a denial of service condition by making the affected application consume 100% CPU resources indefinitely.

This can degrade system performance, cause application crashes, or make services unavailable to legitimate users.

Useful 0 Not Useful 0

Executive Summary

CVE-2026-32287 is a vulnerability in the Go package github.com/antchfx/xpath, specifically in the logicalQuery.Select function. When Boolean XPath expressions that always evaluate to true, such as "1=1" or "true()", are used as top-level selectors, they can cause an infinite loop.

This infinite loop leads to 100% CPU usage, effectively causing the application to hang or become unresponsive.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by monitoring for processes using 100% CPU caused by the evaluation of Boolean XPath expressions such as "1=1" or "true()" in the affected Go package github.com/antchfx/xpath before version v1.3.6.

Specifically, detection involves identifying if the logicalQuery.Select function is triggered with these expressions, leading to an infinite loop.

While no explicit commands are provided, you can use system monitoring tools to detect high CPU usage by processes running this package, for example:

• Use top or htop on Linux to identify processes with 100% CPU usage.
• Use pstack or gdb to attach to the process and inspect stack traces to see if logicalQuery.Select or Expr.Evaluate functions are involved.
• Use strace or equivalent to monitor system calls if applicable.

Useful 0 Not Useful 0

Mitigation Strategies

The immediate mitigation step is to upgrade the github.com/antchfx/xpath package to version v1.3.6 or later, where the vulnerability has been fixed.

Avoid using or processing Boolean XPath expressions that evaluate to true at the top-level selectors such as "1=1" or "true()" until the package is updated.

Monitor your systems for unusual CPU usage patterns that may indicate exploitation attempts.

Useful 0 Not Useful 0

Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Useful 0 Not Useful 0