CVE-2020-25614 json
xmlquery lacks check for whether LoadURL response is in XML format, causing denial of service
published 2020-09-16 6 y ago modified 2026-06-17 4 mo ago also GHSA-93m7-c69f-5cfj , GO-2020-0048 , EUVD-2022-7060
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/antchfx/xmlquery 1.3.1
- xmlquery_project xmlquery 1.3.1
- golang-github-antchfx-xmlquery Debian 14, Debian 13, Debian 12 1.3.3-1
debian advisories DEBIAN-CVE-2020-25614
Exploit prediction
1.94% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/antchfx/xmlquery/issues/39 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/antchfx/xmlquery | <1.3.1 |
1.3.1 |
Classification
References
-
github.com
/antchfx/xmlquery/compare/v1.3.0...v1.3.1
web, patch, third-party-advisory
-
github.com
/antchfx/xmlquery/commit/5648b2f39e8d5d3fc903c45a4f1274829df71821
web, patch
-
github.com
/antchfx/xmlquery/issues/39
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-25614
advisory
-
github.com
/antchfx/xmlquery
package
-
pkg.go.dev
/vuln/GO-2020-0048
web
Sources
- CVE List CVE-2020-25614
- GitHub Advisory GHSA-93m7-c69f-5cfj
- NVD CVE-2020-25614
- OSV GO-2020-0048
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.