Application crash via self-referencing catalog recursion
Published Jan 15, 2026 · Updated Jan 15, 2026
Uncontrolled recursion in libxml2 before 2.15.2 allows remote attackers to crash applications with a self-referencing XML catalog. xmlCatalogXMLResolveURI recursively resolves the same delegate URI entry without detecting that its catalog points back to itself. Exposure requires an application to process an attacker-supplied XML catalog containing the cycle; stack exhaustion ends in a segmentation fault.
Summary
What happened
Uncontrolled recursion in libxml2 before 2.15.2 allows remote attackers to crash applications with a self-referencing XML catalog. xmlCatalogXMLResolveURI recursively resolves the same delegate URI entry without detecting that its catalog points back to itself. Exposure requires an application to process an attacker-supplied XML catalog containing the cycle; stack exhaustion ends in a segmentation fault.
The record
- CVE
- CVE-2026-0990
- Published
- Jan 15, 2026
- Updated
- Jan 15, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat JBoss Core Services
- Classifications
- CWE-674, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2026CVE publishedPublication date reported by the CVE source.
- Jan 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GNOME libxml2 issue 1018 reproducerproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo