CVE-2023-54354

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.

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

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

Nokogiri before 1.14.3 (CRuby implementation only, when using the packaged libxml2) bundles libxml2 v2.10.3, which is vulnerable to NULL pointer dereferences in XML Schema processing (xmlSchemaFixupComplexType, CVE-2023-28484, and xmlSchemaCheckCOSSTDerivedOK). An attacker who supplies a crafted/malformed XML schema can cause libxml2 to dereference a NULL pointer and potentially segfault, resulting in a denial of service. Nokogiri 1.14.3 upgrades the packaged libxml2 to v2.10.4 to resolve these issues.

CVSS v3
7.5
EG Score
7.5(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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 28, 2026

Advisory Details (1)

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

Update packaged libxml2 to v2.10.4 to resolve multiple CVEs · Advisory · sparklemotion/nokogiri · GitHub

https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-pxvg-2qj5-37jq

Vendor Advisories for CVE-2023-54354(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 (154 versions)1.14.3—

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.

  1. 2026-08-30 01:20 UTCEPSS rescore
  2. 2026-08-29 21:13 UTCGHSA enrichment
  3. 2026-08-29 08:10 UTCEG score recompute
  4. 2026-08-29 08:10 UTCGHSA enrichment
  5. 2026-08-28 21:39 UTCEPSS rescore
  6. 2026-08-28 19:07 UTCGHSA enrichment
  7. 2026-08-28 16:42 UTCEG score recompute
  8. 2026-08-28 16:41 UTCGHSA enrichment
  9. 2026-08-28 15:52 UTCEG score recompute
  10. 2026-08-28 15:52 UTCGHSA enrichment
  11. 2026-08-28 10:37 UTCGHSA enrichment
  12. 2026-08-27 21:35 UTCEG score recompute
  13. 2026-08-27 21:35 UTCGHSA enrichment
  14. 2026-08-27 14:23 UTCEPSS rescore
  15. 2026-08-27 08:33 UTCGHSA enrichment
  16. 2026-08-26 19:30 UTCEG score recompute
  17. 2026-08-26 19:30 UTCGHSA enrichment
  18. 2026-08-26 14:44 UTCEPSS rescore
  19. 2026-08-26 06:29 UTCEG score recompute
  20. 2026-08-26 06:29 UTCGHSA enrichment
  21. 2026-08-25 16:24 UTCEG score recompute
  22. 2026-08-25 15:30 UTCEG score recompute
  23. 2026-08-25 15:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-54354?
CVE-2023-54354 is a high vulnerability published on August 25, 2026. Nokogiri before 1.14.3 (CRuby implementation only, when using the packaged libxml2) bundles libxml2 v2.10.3, which is vulnerable to NULL pointer dereferences in XML Schema processing (xmlSchemaFixupComplexType, CVE-2023-28484, and xmlSchemaCheckCOSSTDerivedOK). An attacker who supplies a…
When was CVE-2023-54354 disclosed?
CVE-2023-54354 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-2023-54354 actively exploited?
CVE-2023-54354 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 72.3% of all scored CVEs.
What is the CVSS score of CVE-2023-54354?
CVE-2023-54354 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-54354?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54354, 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-2023-54354

Explore →

Is Your Infrastructure Affected by CVE-2023-54354?

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

Start Free Scan →Browse All CVEs