CVE-2026-79771

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-25. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Nokogiri versions before 1.19.3 contain a memory leak in the XSLT Stylesheet transform method when processing Ruby strings containing null bytes. Attackers can exploit this by passing attacker-controlled input with null bytes to transform parameters, causing heap allocations to leak and enabling denial of service against long-running processes.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/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 computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 25, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Aug 25, 2026
Patch available. Sources: github.
github Patch Available

Memory leak in Nokogiri XSLT transform · Advisory · sparklemotion/nokogiri · GitHub

https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-v2fc-qm4h-8hqv

Vendor Advisories for CVE-2026-79771(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-nokogiri1.13.10+dfsg-2 ... 1.19.4+dfsg-1 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-nokogiri1.18.10+dfsg-1 ... 1.19.4+dfsg-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-nokogiri1.18.10+dfsg-1, 1.18.10+dfsg-2, 1.18.10+dfsg-3, 1.18.2+dfsg-1, 1.19.1+dfsg-11.19.3+dfsg-1—
RubyGems(1)
PackageVulnerable rangeFixed inDependents
nokogiri1.0.0 ... 1.9.1 (193 versions)1.19.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 51× 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.

  1. 2026-09-18 22:49 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 21:09 UTCEG score recompute
  4. 2026-09-16 15:42 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 13:54 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 12:13 UTCEG score recompute
  11. 2026-09-13 10:31 UTCEG score recompute
  12. 2026-09-12 08:49 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 07:08 UTCEG score recompute
  16. 2026-09-09 03:46 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 02:06 UTCEG score recompute
  19. 2026-09-07 00:24 UTCEG score recompute
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-05 22:30 UTCEG score recompute
  22. 2026-09-04 20:49 UTCEG score recompute
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-02 16:46 UTCEG score recompute
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 26 more
  1. 2026-09-01 15:04 UTCEG score recompute
  2. 2026-09-01 15:04 UTCGHSA enrichment
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-09-01 00:09 UTCGHSA enrichment
  7. 2026-08-30 22:29 UTCEG score recompute
  8. 2026-08-30 22:29 UTCGHSA enrichment
  9. 2026-08-30 19:18 UTCEPSS rescore
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 20:48 UTCEG score recompute
  13. 2026-08-29 20:48 UTCGHSA enrichment
  14. 2026-08-28 21:42 UTCEPSS rescore
  15. 2026-08-28 19:07 UTCGHSA enrichment
  16. 2026-08-27 21:51 UTCEG score recompute
  17. 2026-08-27 21:51 UTCGHSA enrichment
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 20:11 UTCEG score recompute
  20. 2026-08-26 20:11 UTCGHSA enrichment
  21. 2026-08-26 14:47 UTCEPSS rescore
  22. 2026-08-25 18:28 UTCEG score recompute
  23. 2026-08-25 17:55 UTCEG score recompute
  24. 2026-08-25 16:24 UTCEG score recompute
  25. 2026-08-25 15:30 UTCEG score recompute
  26. 2026-08-25 15:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-79771?
CVE-2026-79771 is a medium vulnerability published on August 25, 2026. Nokogiri versions before 1.19.3 contain a memory leak in the XSLT Stylesheet transform method when processing Ruby strings containing null bytes. Attackers can exploit this by passing attacker-controlled input with null bytes to transform parameters, causing heap allocations to leak and enabling…
When was CVE-2026-79771 disclosed?
CVE-2026-79771 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79771 actively exploited?
CVE-2026-79771 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.6% of all scored CVEs.
What is the CVSS score of CVE-2026-79771?
CVE-2026-79771 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-79771?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79771, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-79771

Explore →

Is Your Infrastructure Affected by CVE-2026-79771?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs