Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

GHSA-93m7-c69f-5cfj

HIGHFix: antchfx/xmlquery@5648b2f

GHSA-93m7-c69f-5cfj is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in github.com/antchfx/xmlquery. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-93m7-c69f-5cfj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

xmlquery lacks check for whether LoadURL response is in XML format, causing denial of service

Also known asCVE-2020-25614GO-2020-0048
Published
Oct 7, 2022
Updated
Jan 22, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Jan 22, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/antchfx/xmlquery

Real-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

xmlquery before 1.3.1 lacks a check for whether a LoadURL response is in the XML format, which allows attackers to cause a denial of service (SIGSEGV) at xmlquery.(*Node).InnerText or possibly have unspecified other impact.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/antchfx/xmlqueryall versions1.3.1
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/antchfx/xmlquery. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/antchfx/xmlquery to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-93m7-c69f-5cfj is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-93m7-c69f-5cfj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-93m7-c69f-5cfj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

xmlquery before 1.3.1 lacks a check for whether a LoadURL response is in the XML format, which allows attackers to cause a denial of service (SIGSEGV) at xmlquery.(*Node).InnerText or possibly have unspecified other impact.
O3 Security · Impact-Aware SCA

Is GHSA-93m7-c69f-5cfj in your dependencies?

O3 detects GHSA-93m7-c69f-5cfj across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-93m7-c69f-5cfj: xmlquery Denial of… | O3 Security