CVE-2026-11979: CWE-121: Stack-based Buffer Overflow in xmlsoft libxml2
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.
AI Analysis
Technical Summary
The libxml2 library's xmlcatalog utility in --shell mode is vulnerable to multiple stack-based buffer overflows due to the usershell() function processing user input with fixed-size stack buffers without proper bounds checking. Overly long input lines can overflow internal buffers such as command, arg, and argv, causing stack memory corruption. This may result in a crash or potentially arbitrary code execution within the xmlcatalog process context. The vulnerability has been addressed in commit c2e233fc. The maintainers do not classify this as a security vulnerability but as a bug. No explicit remediation level or patch advisory is provided in the available data.
Potential Impact
Exploitation of this vulnerability can cause a crash of the xmlcatalog utility or potentially allow arbitrary code execution within its process context. The CVSS 4.0 score of 1.8 indicates low severity with local attack vector, low complexity, and partial attack impact. No known exploits in the wild have been reported.
Mitigation Recommendations
The vulnerability has been fixed in commit c2e233fc. Users should update libxml2 to a version that includes this fix. Since no official vendor advisory or patch link is provided, users should verify the presence of this commit in their libxml2 version or obtain an updated release from the maintainers. No additional mitigation guidance is available from the vendor, and the maintainers consider this a bug rather than a security vulnerability.
CVE-2026-11979: CWE-121: Stack-based Buffer Overflow in xmlsoft libxml2
Description
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 v4.0
Score 1.8low
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The libxml2 library's xmlcatalog utility in --shell mode is vulnerable to multiple stack-based buffer overflows due to the usershell() function processing user input with fixed-size stack buffers without proper bounds checking. Overly long input lines can overflow internal buffers such as command, arg, and argv, causing stack memory corruption. This may result in a crash or potentially arbitrary code execution within the xmlcatalog process context. The vulnerability has been addressed in commit c2e233fc. The maintainers do not classify this as a security vulnerability but as a bug. No explicit remediation level or patch advisory is provided in the available data.
Potential Impact
Exploitation of this vulnerability can cause a crash of the xmlcatalog utility or potentially allow arbitrary code execution within its process context. The CVSS 4.0 score of 1.8 indicates low severity with local attack vector, low complexity, and partial attack impact. No known exploits in the wild have been reported.
Mitigation Recommendations
The vulnerability has been fixed in commit c2e233fc. Users should update libxml2 to a version that includes this fix. Since no official vendor advisory or patch link is provided, users should verify the presence of this commit in their libxml2 version or obtain an updated release from the maintainers. No additional mitigation guidance is available from the vendor, and the maintainers consider this a bug rather than a security vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CERT-PL
- Date Reserved
- 2026-06-11T13:20:24.839Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4274e727e9c79719eeb048
Added to database: 06/29/2026, 13:36:39 UTC
Last enriched: 07/13/2026, 10:02:55 UTC
Last updated: 08/13/2026, 17:25:04 UTC
Views: 161
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.