CVE-2026-1757 | Libxml2: memory leak leading to local denial of service in xmllint interactive shell

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.

Published: 2026-02-02 Last update: 2026-04-22 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-1757 is rated Low Risk (25.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-1757

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-03 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-1757

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.2 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.5 3.6 [email protected]

Weakness enumeration for CVE-2026-1757

GitHub Security Advisory for CVE-2026-1757

GHSA-7qq5-wfv8-hvvh · Severity: medium — A flaw was identified in the interactive shell of the xmllint utility, part of the libxml2...

OS Trackers for CVE-2026-1757

vendor priority summary link
debian unimportant CVE-2026-1757 unimportant priority: Debian including 1 source packages (libxml2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2026-1757
redhat medium — https://access.redhat.com/security/cve/CVE-2026-1757
suse low CVE-2026-1757 severity low: SUSE including 324 source package names (1.1.1-1.29:libxml2-2-2.12.10-150700.4.11.1, 13.2-9.72:libopenssl3-3.1.4-8.1, …), 588 product×package rows across 140 product lines (Container private-registry/harbor-portal, Container suse/ltss/sle12.5/sles12sp5, … (140 product lines)): Fixed 348, Known Affected 231, First Fixed 9. https://www.suse.com/security/cve/CVE-2026-1757/
ubuntu low CVE-2026-1757 low priority: Ubuntu including 1 source packages (libxml2), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): not-affected 6, needed 1, released 1. https://ubuntu.com/security/CVE-2026-1757

Affected software / configurations for CVE-2026-1757

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-1757

cvelogic Threat Intelligence