CVE-2022-51000

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

Nokogiri before 1.13.2 (CRuby, when using packaged libraries) ships vendored libxml2 2.9.12 and libxslt 1.1.34, which are affected by two upstream CVEs. Via CVE-2021-30560 in libxslt, an application transforming XML with untrusted XSL stylesheets is vulnerable to a denial-of-service attack. Via CVE-2022-23308 in libxml2, an application parsing an untrusted document with parse option DTDVALID set to true and NOENT set to false may be vulnerable to denial of service, memory disclosure, or code execution. Nokogiri 1.13.2 upgrades vendored libxml2 to 2.9.13 and libxslt to 1.1.35.

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

Published

August 25, 2026

Last Modified

August 28, 2026

Advisory Details (4)

Auto-updated Aug 28, 2026
Patch available. Sources: github_commit, github.
generic

Nokogiri before 1.13.2 Multiple Vulnerabilities via libxml2 libxslt | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nokogiri-before-multiple-vulnerabilities-via-libxml2-libxslt
github Patch Available

Update packaged libxml2 (2.9.12 → 2.9.13) and libxslt (1.1.34 → 1.1.35) · Advisory · sparklemotion/nokogiri · GitHub

https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-fq42-c5rg-92c2
github_commit

commit 50f9c9c (GNOME/libxslt)

Fix landed in GNOME/libxslt commit 50f9c9c — awaiting tagged release

https://github.com/GNOME/libxslt/commit/50f9c9c
github_commit

commit 652dd12 (GNOME/libxml2)

Fix landed in GNOME/libxml2 commit 652dd12 — awaiting tagged release

https://github.com/GNOME/libxml2/commit/652dd12

Vendor Advisories for CVE-2022-51000(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)
PackageVulnerable rangeFixed inDependents
nokogiri1.0.0 ... 1.9.1 (141 versions)1.13.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 44× in last 7d / 44× 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-08-30 05:41 UTCGHSA enrichment
  2. 2026-08-30 01:37 UTCEG score recompute
  3. 2026-08-30 01:37 UTCGHSA enrichment
  4. 2026-08-30 01:19 UTCEPSS rescore
  5. 2026-08-29 21:33 UTCGHSA enrichment
  6. 2026-08-29 17:29 UTCGHSA enrichment
  7. 2026-08-29 12:37 UTCGHSA enrichment
  8. 2026-08-29 08:30 UTCGHSA enrichment
  9. 2026-08-29 04:24 UTCGHSA enrichment
  10. 2026-08-29 00:16 UTCEG score recompute
  11. 2026-08-29 00:16 UTCGHSA enrichment
  12. 2026-08-28 21:38 UTCEPSS rescore
  13. 2026-08-28 19:07 UTCGHSA enrichment
  14. 2026-08-28 16:44 UTCEG score recompute
  15. 2026-08-28 16:43 UTCGHSA enrichment
  16. 2026-08-28 15:52 UTCEG score recompute
  17. 2026-08-28 15:52 UTCGHSA enrichment
  18. 2026-08-28 14:38 UTCGHSA enrichment
  19. 2026-08-28 10:30 UTCGHSA enrichment
  20. 2026-08-28 06:24 UTCGHSA enrichment
  21. 2026-08-28 02:19 UTCGHSA enrichment
  22. 2026-08-27 22:15 UTCGHSA enrichment
  23. 2026-08-27 18:11 UTCEG score recompute
  24. 2026-08-27 18:11 UTCGHSA enrichment
  25. 2026-08-27 14:22 UTCEPSS rescore
Show 19 more
  1. 2026-08-27 13:44 UTCGHSA enrichment
  2. 2026-08-27 09:40 UTCGHSA enrichment
  3. 2026-08-27 05:36 UTCGHSA enrichment
  4. 2026-08-27 01:30 UTCGHSA enrichment
  5. 2026-08-26 21:26 UTCGHSA enrichment
  6. 2026-08-26 17:23 UTCEG score recompute
  7. 2026-08-26 17:23 UTCGHSA enrichment
  8. 2026-08-26 16:23 UTCEG score recompute
  9. 2026-08-26 16:23 UTCGHSA enrichment
  10. 2026-08-26 14:43 UTCEPSS rescore
  11. 2026-08-26 12:54 UTCGHSA enrichment
  12. 2026-08-26 08:50 UTCGHSA enrichment
  13. 2026-08-26 04:44 UTCGHSA enrichment
  14. 2026-08-26 00:40 UTCGHSA enrichment
  15. 2026-08-25 20:37 UTCEG score recompute
  16. 2026-08-25 20:37 UTCGHSA enrichment
  17. 2026-08-25 16:24 UTCEG score recompute
  18. 2026-08-25 15:30 UTCEG score recompute
  19. 2026-08-25 15:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-51000?
CVE-2022-51000 is a critical vulnerability published on August 25, 2026. Nokogiri before 1.13.2 (CRuby, when using packaged libraries) ships vendored libxml2 2.9.12 and libxslt 1.1.34, which are affected by two upstream CVEs. Via CVE-2021-30560 in libxslt, an application transforming XML with untrusted XSL stylesheets is vulnerable to a denial-of-service attack. Via…
When was CVE-2022-51000 disclosed?
CVE-2022-51000 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-51000 actively exploited?
CVE-2022-51000 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 63.3% of all scored CVEs.
What is the CVSS score of CVE-2022-51000?
CVE-2022-51000 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-51000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-51000, 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-2022-51000

Explore →

Is Your Infrastructure Affected by CVE-2022-51000?

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

Start Free Scan →Browse All CVEs