Nokogiri before 1.18.3 contains a stack buffer overflow vulnerability in libxml2 when reporting DTD validation errors with long QName prefixes, and a use-after-free vulnerability during validation against untrusted XML Schemas. Attackers can trigger these vulnerabilities by providing malicious DTD content or untrusted XSD files to cause denial of service or potential code execution.
CVE-2025-71407
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. a secondary CVSS source baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
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 computedSeverity98% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026Nokogiri before 1.18.3 Stack Buffer Overflow and Use-After-Free | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nokogiri-before-stack-buffer-overflow-and-use-after-freeNokogiri updates packaged libxml2 to 2.13.6 to resolve CVE-2025-24928 and CVE-2024-56171 · Advisory · sparklemotion/nokogiri · GitHub
https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-vvfq-8hwr-qm4mVendor Advisories for CVE-2025-71407(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
RubyGems(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nokogiri | 1.0.0 ... 1.9.1 (182 versions) | 1.18.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 39× in last 7d / 39× 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.
- 2026-08-30 04:41 UTCEG score recompute
- 2026-08-30 04:41 UTCGHSA enrichment
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-30 00:39 UTCGHSA enrichment
- 2026-08-29 20:37 UTCGHSA enrichment
- 2026-08-29 16:33 UTCGHSA enrichment
- 2026-08-29 12:26 UTCGHSA enrichment
- 2026-08-29 08:23 UTCGHSA enrichment
- 2026-08-29 04:21 UTCGHSA enrichment
- 2026-08-29 00:16 UTCEG score recompute
- 2026-08-29 00:16 UTCGHSA enrichment
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-28 19:07 UTCGHSA enrichment
- 2026-08-28 18:37 UTCGHSA enrichment
- 2026-08-28 14:27 UTCGHSA enrichment
- 2026-08-28 10:25 UTCGHSA enrichment
- 2026-08-28 06:20 UTCGHSA enrichment
- 2026-08-28 02:15 UTCGHSA enrichment
- 2026-08-27 22:12 UTCGHSA enrichment
- 2026-08-27 18:11 UTCEG score recompute
- 2026-08-27 18:11 UTCGHSA enrichment
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-27 14:09 UTCGHSA enrichment
- 2026-08-27 10:08 UTCGHSA enrichment
- 2026-08-27 06:05 UTCGHSA enrichment
Show 14 moreShow fewer
- 2026-08-27 01:56 UTCGHSA enrichment
- 2026-08-26 21:55 UTCGHSA enrichment
- 2026-08-26 17:50 UTCEG score recompute
- 2026-08-26 17:50 UTCGHSA enrichment
- 2026-08-26 14:45 UTCEPSS rescore
- 2026-08-26 13:48 UTCGHSA enrichment
- 2026-08-26 09:45 UTCGHSA enrichment
- 2026-08-26 05:43 UTCGHSA enrichment
- 2026-08-26 01:41 UTCGHSA enrichment
- 2026-08-25 21:40 UTCEG score recompute
- 2026-08-25 21:40 UTCGHSA enrichment
- 2026-08-25 16:24 UTCEG score recompute
- 2026-08-25 15:30 UTCEG score recompute
- 2026-08-25 15:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-787
Frequently asked(5)
What is CVE-2025-71407?
When was CVE-2025-71407 disclosed?
Is CVE-2025-71407 actively exploited?
What is the CVSS score of CVE-2025-71407?
How do I remediate CVE-2025-71407?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71407
Is Your Infrastructure Affected by CVE-2025-71407?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.