CVE-2024-58377

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under the CNA's CVSS v4.0 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cvss_v4, epss
Trending — 5 sources updated this week
9.3EG
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.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.16.5 bundle libxml2 2.12.6, which is affected by CVE-2024-34459 in libxml2's xmllint tool. Nokogiri 1.16.5 upgrades the bundled libxml2 to 2.12.7 to address this. Per the maintainers, there is no impact to Nokogiri users because Nokogiri does not provide or expose the xmllint tool where the issue occurs.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity93% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 25, 2026

Advisory Details (1)

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

Nokogiri updates packaged libxml2 to 2.12.7 to resolve CVE-2024-34459 · Advisory · sparklemotion/nokogiri · GitHub

https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-r95h-9x8f-r3f7

Vendor Advisories for CVE-2024-58377(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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-26 14:59 UTCEG score recompute
  2. 2026-08-26 14:59 UTCGHSA enrichment
  3. 2026-08-26 14:44 UTCEPSS rescore
  4. 2026-08-26 10:53 UTCGHSA enrichment
  5. 2026-08-26 06:47 UTCGHSA enrichment
  6. 2026-08-26 02:41 UTCGHSA enrichment
  7. 2026-08-25 22:34 UTCGHSA enrichment
  8. 2026-08-25 18:28 UTCEG score recompute
  9. 2026-08-25 18:24 UTCNVD update
  10. 2026-08-25 17:25 UTCEG score recompute
  11. 2026-08-25 17:24 UTCMITRE cvelistV5CVSS v3 → 9.3 · severity → CRITICAL
  12. 2026-08-25 16:24 UTCEG score recompute
  13. 2026-08-25 16:22 UTCNVD update
  14. 2026-08-25 15:30 UTCEG score recompute
  15. 2026-08-25 15:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-58377?
CVE-2024-58377 is a critical vulnerability published on August 25, 2026. Nokogiri versions before 1.16.5 bundle libxml2 2.12.6, which is affected by CVE-2024-34459 in libxml2's xmllint tool. Nokogiri 1.16.5 upgrades the bundled libxml2 to 2.12.7 to address this. Per the maintainers, there is no impact to Nokogiri users because Nokogiri does not provide or expose the…
When was CVE-2024-58377 disclosed?
CVE-2024-58377 was first published in the National Vulnerability Database on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-58377 actively exploited?
CVE-2024-58377 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 91.0% of all scored CVEs.
What is the CVSS score of CVE-2024-58377?
CVE-2024-58377 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2024-58377?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-58377, 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

Explore the affected products and dependency analysis for CVE-2024-58377

Explore →

Is Your Infrastructure Affected by CVE-2024-58377?

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

Start Free Scan →Browse All CVEs