Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.22% for the current model date.
BlackTreeCVE IntelligenceRed Hat · Red Hat Hardened Images
Official source article: Red Hat RHSA-2026:7519 ↗. Check the applicable product and release in the original source.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.14+dfsg-1.3~deb12u6 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.15.2+dfsg-0.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.15.2+dfsg-0.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch availableA 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.
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.
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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.
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 2 Feb 2026 · Last source change 1 Sept 2026, 11:54 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime
Core structured fields are present and their contributing authorities are shown above.