Vulnerability in xmllint utility (CVE-2026-1757)
Summary
Vulnerability in xmllint utility (CVE-2026-1757). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-1757 has been found in xmllint utility.
Risk of unauthorized operations or information disclosure. CVSS score: 6.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "xmllint utility CVE-2026-1757" on the vendor's site.
CVE-2026-1757 (xmllint utility) — CWE-401 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-401) exists in xmllint utility.
Check the vendor advisory for the affected versions of xmllint utility.
Severity: Medium (CVSS 6.2/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで xmllint utility を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-1757 libxml2 Fixed in: 2.9.10+dfsg-6.7+deb11u10
- Ubuntu UBUNTU-CVE-2026-1757 libxml2 Fixed in: 2.14.5+dfsg-0.2ubuntu0.2
References
- web secalert@redhat.com
- web secalert@redhat.com
- web secalert@redhat.com
- web secalert@redhat.com