● Not verified

How to Fix CVE-2026-32287: Denial of Service in github.com/antchfx/xpath

Q: Is CVE-2026-32287 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-32287?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for github.com/antchfx/xpath run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-7678: SQL Injection in yudao-cloud — SQL Injection in yudao-cloud
How to Fix CVE-2026-23850: Path Traversal in siyuan — Path Traversal in siyuan
How to Fix CVE-2026-22664: prompts.chat (Bundle Sibling) , prompts.chat (Bundle Sibling)
How to Fix CVE-2026-1673: Cross-Site Request Forgery (CSRF) , Cross-Site Request Forgery (CSRF)
How to Fix CVE-2026-2137: Critical Vulnerability in TX3 , Critical Vulnerability in TX3

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	Not verified - see advisory
Actively exploited?	Not currently listed in CISA KEV
Affected	0 < 1.3.6
Fixed in	See vendor advisory
Type (CWE)	Not verified

What is CVE-2026-32287?

CVE-2026-32287 is a denial of service flaw in github.com/antchfx/xpath. A crafted request triggers a code path that crashes or hangs the service, taking the product offline for legitimate users. Vendor 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()".

Why this CVE matters

Denial-of-service flaws in a network gateway or firewall have an outsize operational impact. A single packet that reboots an inline device takes down everything behind it, which is why even non-RCE bugs on these products warrant priority patching.

For deployments of github.com/antchfx/xpath that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

github.com/antchfx/xpath: 0 < 1.3.6

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Run git --version to confirm the installed Git release and compare against the affected ranges.

How to fix CVE-2026-32287

Read the vendor advisory in full: https://github.com/antchfx/xpath/issues/121
Upgrade github.com/antchfx/xpath to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

The commands below are runnable starting points. Adapt the package name, target version, and host paths to your environment using the vendor advisory linked under References.

npm / Yarn / pnpm


# Vendor advisory: https://github.com/antchfx/xpath/issues/121
# Update to the patched release named in the advisory
npm install github-com-antchfx-xpath@latest
# or pin to the exact fixed version from the vendor advisory
npm install github-com-antchfx-xpath@<patched-version>
npm ls github-com-antchfx-xpath

PyPI (pip / Poetry)


# Vendor advisory: https://github.com/antchfx/xpath/issues/121
pip install --upgrade github-com-antchfx-xpath
pip show github-com-antchfx-xpath | grep -i version
# Poetry:
poetry add github-com-antchfx-xpath@^<patched-version>

Docker / container


# Vendor advisory: https://github.com/antchfx/xpath/issues/121
docker pull <your-registry>/github-com-antchfx-xpath:<patched-tag>
docker stop <app> && docker rm <app>
docker run -d --name <app> <your-registry>/github-com-antchfx-xpath:<patched-tag>

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2026-32287 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-32287-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'github.com/antchfx/xpath' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2026-32287-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'github.com/antchfx/xpath' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)


#!/usr/bin/env bash
# CVE-2026-32287 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-32287-fix.log; }

log "Detect: current git version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' git 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' git 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2026-32287-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/git ] && cp -a /etc/git "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade git
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y git
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y git
fi

log "Verify: re-reading git version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' git)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' git)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: git upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

If you cannot patch immediately

Front the service with rate limiting and drop malformed packets at a load balancer or IPS. Patch to remove the underlying crash condition.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-32287.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one.

Frequently asked questions

Is CVE-2026-32287 being exploited in the wild?