Nokogiri before 1.18.4 bundles a vulnerable version of libxslt (prior to 1.1.43) that contains two use-after-free vulnerabilities: CVE-2025-24855 (use-after-free of the XPath context node due to xsltEvalXPathStringNs leaking xpathCtxt->node) and CVE-2024-55549 (use-after-free related to excluded result prefixes/namespaces). Processing crafted XSLT can trigger memory corruption. Nokogiri 1.18.4 upgrades the bundled libxslt to 1.1.43 to resolve these issues.
CVE-2025-71406
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 7.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
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 50(Track)EG Risk 50/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 computedSeverity78% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026Nokogiri updates packaged libxslt to v1.1.43 to resolve multiple CVEs · Advisory · sparklemotion/nokogiri · GitHub
https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-mrxw-mxhj-p664Vendor Advisories for CVE-2025-71406(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 (183 versions) | 1.18.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 23× 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:36 UTCEG score recompute
- 2026-08-30 04:36 UTCGHSA enrichment
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-29 17:29 UTCGHSA enrichment
- 2026-08-29 06:14 UTCEG score recompute
- 2026-08-29 06:14 UTCGHSA enrichment
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-28 19:07 UTCGHSA enrichment
- 2026-08-28 13:52 UTCGHSA enrichment
- 2026-08-28 02:45 UTCGHSA enrichment
- 2026-08-27 15:40 UTCGHSA enrichment
- 2026-08-27 04:30 UTCGHSA enrichment
- 2026-08-26 17:23 UTCEG score recompute
- 2026-08-26 17:23 UTCGHSA enrichment
- 2026-08-26 16:23 UTCEG score recompute
- 2026-08-26 16:23 UTCGHSA enrichment
- 2026-08-26 14:45 UTCEPSS rescore
- 2026-08-26 14:36 UTCGHSA enrichment
- 2026-08-26 03:29 UTCEG score recompute
- 2026-08-26 03:29 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)
Frequently asked(5)
What is CVE-2025-71406?
When was CVE-2025-71406 disclosed?
Is CVE-2025-71406 actively exploited?
What is the CVSS score of CVE-2025-71406?
How do I remediate CVE-2025-71406?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71406
Is Your Infrastructure Affected by CVE-2025-71406?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.