CVE-2026-11979

HIGHNVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: LOW) published 2026-06-29. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.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: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow internal buffers (command, arg, and argv) during input parsing. This results in memory corruption within the stack frame. Successful exploitation may cause a crash or potentially allow arbitrary code execution in the context of the xmlcatalog process.

This issue has been fixed in the commit c2e233fc.

NOTE: The maintainers of this project did not agree that this issue is a vulnerability and considered it a bug.

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

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

Client Challenge

https://gitlab.gnome.org/GNOME/libxml2/-/commit/c2e233fc1b341685fc99621b2768b503f777a72e
generic

Vulnerability in libxml2 software | CERT Polska

https://cert.pl/en/posts/2026/06/CVE-2026-11979

Vendor Advisories for CVE-2026-11979(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibxml2-main-2.15.3-0.1.1.hum12026-06-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 99× 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-07-27 16:55 UTCEG score recompute
  2. 2026-07-27 16:55 UTCVendor advisory
  3. 2026-07-27 16:55 UTCGHSA enrichment
  4. 2026-07-27 14:13 UTCEPSS rescore
  5. 2026-07-27 02:46 UTCEG score recompute
  6. 2026-07-27 02:46 UTCVendor advisory
  7. 2026-07-27 02:46 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 14:17 UTCEG score recompute
  11. 2026-07-26 14:17 UTCVendor advisory
  12. 2026-07-26 14:17 UTCGHSA enrichment
  13. 2026-07-25 14:17 UTCEPSS rescore
  14. 2026-07-24 14:17 UTCEPSS rescore
  15. 2026-07-23 14:18 UTCEPSS rescore
  16. 2026-07-23 03:05 UTCEG score recompute
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-21 15:24 UTCEPSS rescore
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-19 14:30 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-16 18:36 UTCVendor advisory
  23. 2026-07-16 18:36 UTCGHSA enrichment
  24. 2026-07-16 17:02 UTCEPSS rescore
  25. 2026-07-16 06:07 UTCVendor advisory
Show 74 more
  1. 2026-07-16 06:07 UTCGHSA enrichment
  2. 2026-07-15 17:38 UTCVendor advisory
  3. 2026-07-15 17:37 UTCGHSA enrichment
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 05:09 UTCVendor advisory
  6. 2026-07-15 05:09 UTCGHSA enrichment
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-14 15:46 UTCVendor advisory
  9. 2026-07-14 15:46 UTCGHSA enrichment
  10. 2026-07-14 03:17 UTCVendor advisory
  11. 2026-07-14 03:17 UTCGHSA enrichment
  12. 2026-07-13 22:30 UTCEPSS rescore
  13. 2026-07-13 14:49 UTCVendor advisory
  14. 2026-07-13 14:49 UTCGHSA enrichment
  15. 2026-07-13 06:12 UTCEPSS rescore
  16. 2026-07-13 02:21 UTCVendor advisory
  17. 2026-07-13 02:21 UTCGHSA enrichment
  18. 2026-07-12 13:53 UTCVendor advisory
  19. 2026-07-12 13:53 UTCGHSA enrichment
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-12 01:20 UTCVendor advisory
  22. 2026-07-12 01:20 UTCGHSA enrichment
  23. 2026-07-11 12:52 UTCVendor advisory
  24. 2026-07-11 12:52 UTCGHSA enrichment
  25. 2026-07-11 08:27 UTCEPSS rescore
  26. 2026-07-11 00:23 UTCVendor advisory
  27. 2026-07-11 00:23 UTCGHSA enrichment
  28. 2026-07-10 11:55 UTCVendor advisory
  29. 2026-07-10 11:54 UTCGHSA enrichment
  30. 2026-07-09 23:26 UTCVendor advisory
  31. 2026-07-09 23:26 UTCGHSA enrichment
  32. 2026-07-09 19:10 UTCEPSS rescore
  33. 2026-07-09 10:57 UTCVendor advisory
  34. 2026-07-09 10:56 UTCGHSA enrichment
  35. 2026-07-08 22:27 UTCVendor advisory
  36. 2026-07-08 22:27 UTCGHSA enrichment
  37. 2026-07-08 15:15 UTCEPSS rescore
  38. 2026-07-08 15:15 UTCEPSS rescore
  39. 2026-07-08 09:58 UTCVendor advisory
  40. 2026-07-08 09:58 UTCGHSA enrichment
  41. 2026-07-07 21:30 UTCVendor advisory
  42. 2026-07-07 21:30 UTCGHSA enrichment
  43. 2026-07-07 13:46 UTCEPSS rescore
  44. 2026-07-07 09:00 UTCVendor advisory
  45. 2026-07-07 09:00 UTCGHSA enrichment
  46. 2026-07-06 20:25 UTCVendor advisory
  47. 2026-07-06 20:25 UTCGHSA enrichment
  48. 2026-07-06 07:52 UTCVendor advisory
  49. 2026-07-06 07:52 UTCGHSA enrichment
  50. 2026-07-06 02:23 UTCEPSS rescore
  51. 2026-07-05 19:23 UTCVendor advisory
  52. 2026-07-05 19:23 UTCGHSA enrichment
  53. 2026-07-05 06:54 UTCVendor advisory
  54. 2026-07-05 06:54 UTCGHSA enrichment
  55. 2026-07-05 02:30 UTCEPSS rescore
  56. 2026-07-05 02:30 UTCEPSS rescore
  57. 2026-07-04 18:25 UTCVendor advisory
  58. 2026-07-04 18:25 UTCGHSA enrichment
  59. 2026-07-04 06:31 UTCEPSS rescore
  60. 2026-07-04 05:56 UTCVendor advisory
  61. 2026-07-04 05:56 UTCGHSA enrichment
  62. 2026-07-03 17:26 UTCVendor advisory
  63. 2026-07-03 17:26 UTCGHSA enrichment
  64. 2026-07-03 04:58 UTCVendor advisory
  65. 2026-07-03 04:58 UTCGHSA enrichment
  66. 2026-07-02 16:29 UTCEG score recompute▲ 6.00
  67. 2026-07-02 16:29 UTCVendor advisory
  68. 2026-07-02 16:29 UTCGHSA enrichment
  69. 2026-07-01 15:06 UTCEPSS rescore
  70. 2026-07-01 15:06 UTCEPSS rescore
  71. 2026-06-30 23:22 UTCEPSS rescore
  72. 2026-06-30 20:33 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  73. 2026-06-29 13:33 UTCEG score recompute
  74. 2026-06-29 13:32 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-11979?
CVE-2026-11979 is a high vulnerability published on June 29, 2026. libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow…
When was CVE-2026-11979 disclosed?
CVE-2026-11979 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11979 actively exploited?
CVE-2026-11979 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 95.5% of all scored CVEs.
What is the CVSS score of CVE-2026-11979?
CVE-2026-11979 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-11979?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11979, 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-2026-11979

Explore →

Is Your Infrastructure Affected by CVE-2026-11979?

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

Start Free Scan →Browse All CVEs