CVE-2026-1757

MEDIUMNVD 6.26.2—
EchelonGraph scoreMEDIUM confidence

Score 6.2 from GitHub Security Advisory published 2026-02-02. NVD baseline CVSS 6.2; sources differ by 0.0.

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

A fix is available — apply it.

A flaw was identified in the interactive shell of the xmllint utility, part of the libxml2 project, where memory allocated for user input is not properly released under certain conditions. When a user submits input consisting only of whitespace, the program skips command execution but fails to free the allocated buffer. Repeating this action causes memory to continuously accumulate. Over time, this can exhaust system memory and terminate the xmllint process, creating a denial-of-service condition on the local system.

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

Published

February 2, 2026

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Aug 7, 2026
Patch available. Sources: redhat.
generic

(CVE-2026-1757) Memory leak in xmllint Shell - shell.c (#1009) · Issues · GNOME / libxml2 · GitLab

https://gitlab.gnome.org/GNOME/libxml2/-/issues/1009
redhat

2435940 – (CVE-2026-1757) CVE-2026-1757 libxml2: Memory Leak Leading to Local Denial of Service in xmllint Interactive Shell

https://bugzilla.redhat.com/show_bug.cgi?id=2435940
redhat Patch Available

CVE-2026-1757 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-1757
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:7519

Vendor Advisories for CVE-2026-1757(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-libxml2 (2.15.2+dfsg-0.1ubuntu0.1) @ resolute2026-08-21ubuntu
redhatlibxml2-main-2.15.2-0.3.hum12026-04-10redhat

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libxml22.9.10+dfsg-6.7 ... 2.9.10+dfsg-6.7+deb11u9 (10 versions)2.9.10+dfsg-6.7+deb11u10—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxml22.9.14+dfsg-1.2 ... 2.9.14+dfsg-1.3~deb12u5 (6 versions)2.9.14+dfsg-1.3~deb12u6—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1, 2.12.7+dfsg+really2.9.14-2.1+deb13u1, 2.12.7+dfsg+really2.9.14-2.1+deb13u22.12.7+dfsg+really2.9.14-2.1+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1 ... 2.15.1+dfsg-2 (25 versions)2.15.2+dfsg-0.1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Showing the most recent 100 of 182 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:11 UTCEPSS rescore
  3. 2026-09-01 13:53 UTCEPSS rescore
  4. 2026-09-01 12:28 UTCVendor advisory
  5. 2026-09-01 12:27 UTCGHSA enrichment
  6. 2026-09-01 12:02 UTCEG score recompute
  7. 2026-09-01 12:02 UTCVendor advisory
  8. 2026-09-01 12:02 UTCGHSA enrichment
  9. 2026-09-01 04:39 UTCEPSS rescore
  10. 2026-08-31 16:43 UTCEG score recompute
  11. 2026-08-31 16:43 UTCVendor advisory
  12. 2026-08-31 16:43 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:48 UTCEPSS rescore
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 12:20 UTCVendor advisory
  21. 2026-08-21 12:20 UTCGHSA enrichment
  22. 2026-08-21 12:15 UTCEG score recompute
  23. 2026-08-21 12:15 UTCVendor advisory
  24. 2026-08-21 12:15 UTCGHSA enrichment
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 11:42 UTCEG score recompute
  8. 2026-08-14 11:42 UTCVendor advisory
  9. 2026-08-14 11:42 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 03:52 UTCEG score recompute
  12. 2026-08-13 03:52 UTCVendor advisory
  13. 2026-08-13 03:52 UTCGHSA enrichment
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 13:42 UTCEPSS rescore
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-09 16:12 UTCEG score recompute
  18. 2026-08-09 16:12 UTCVendor advisory
  19. 2026-08-09 16:12 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 23:03 UTCEG score recompute
  23. 2026-08-07 23:03 UTCVendor advisory
  24. 2026-08-07 23:03 UTCGHSA enrichment
  25. 2026-08-06 13:46 UTCEPSS rescore
  26. 2026-08-06 04:34 UTCEG score recompute
  27. 2026-08-06 04:34 UTCVendor advisory
  28. 2026-08-06 04:34 UTCGHSA enrichment
  29. 2026-08-05 19:17 UTCEPSS rescore
  30. 2026-08-04 15:10 UTCEPSS rescore
  31. 2026-08-04 10:38 UTCEPSS rescore
  32. 2026-08-03 10:35 UTCEPSS rescore
  33. 2026-08-02 21:43 UTCEG score recompute
  34. 2026-08-02 21:43 UTCVendor advisory
  35. 2026-08-02 21:43 UTCGHSA enrichment
  36. 2026-08-02 02:26 UTCEPSS rescore
  37. 2026-08-01 04:15 UTCEPSS rescore
  38. 2026-07-31 01:21 UTCOSV refresh
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-27 14:13 UTCEPSS rescore
  41. 2026-07-26 14:54 UTCEPSS rescore
  42. 2026-07-26 14:54 UTCEPSS rescore
  43. 2026-07-25 14:17 UTCEPSS rescore
  44. 2026-07-25 14:17 UTCEPSS rescore
  45. 2026-07-24 14:17 UTCEPSS rescore
  46. 2026-07-23 14:18 UTCEPSS rescore
  47. 2026-07-23 14:18 UTCEPSS rescore
  48. 2026-07-23 03:06 UTCEG score recompute
  49. 2026-07-22 14:08 UTCEPSS rescore
  50. 2026-07-21 15:24 UTCEPSS rescore
  51. 2026-07-21 15:24 UTCEPSS rescore
  52. 2026-07-20 17:08 UTCEPSS rescore
  53. 2026-07-19 14:31 UTCEPSS rescore
  54. 2026-07-19 14:31 UTCEPSS rescore
  55. 2026-07-19 02:29 UTCEPSS rescore
  56. 2026-07-19 02:28 UTCEPSS rescore
  57. 2026-07-18 10:04 UTCEPSS rescore
  58. 2026-07-18 10:04 UTCEPSS rescore
  59. 2026-07-16 17:03 UTCEPSS rescore
  60. 2026-07-16 17:03 UTCEPSS rescore
  61. 2026-07-15 16:57 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 02:00 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-13 22:30 UTCEPSS rescore
  66. 2026-07-13 10:07 UTCOSV refresh
  67. 2026-07-13 06:12 UTCEPSS rescore
  68. 2026-07-12 05:46 UTCEPSS rescore
  69. 2026-07-11 08:27 UTCEPSS rescore
  70. 2026-07-09 19:10 UTCEPSS rescore
  71. 2026-07-08 15:15 UTCEPSS rescore
  72. 2026-07-08 15:15 UTCEPSS rescore
  73. 2026-07-07 13:46 UTCEPSS rescore
  74. 2026-07-06 16:27 UTCEPSS rescore
  75. 2026-07-06 02:23 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-1757?
CVE-2026-1757 is a medium vulnerability published on February 2, 2026. A flaw was identified in the interactive shell of the xmllint utility, part of the libxml2 project, where memory allocated for user input is not properly released under certain conditions. When a user submits input consisting only of whitespace, the program skips command execution but fails to free…
When was CVE-2026-1757 disclosed?
CVE-2026-1757 was first published in the National Vulnerability Database on February 2, 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-1757 actively exploited?
CVE-2026-1757 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 89.9% of all scored CVEs.
What is the CVSS score of CVE-2026-1757?
CVE-2026-1757 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-1757?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1757, 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-1757

Explore →

Is Your Infrastructure Affected by CVE-2026-1757?

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

Start Free Scan →Browse All CVEs