CVE-2013-1969

CVE-2013-1969 is a high-severity vulnerability in Xmlsoft Libxml2 with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-399.

Key facts

Description

Multiple use-after-free vulnerabilities in libxml2 2.9.0 and possibly other versions might allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via vectors related to the (1) htmlParseChunk and (2) xmldecl_done functions, as demonstrated by a buffer overflow in the xmlBufGetInputBase function.

Frequently asked questions

What is CVE-2013-1969?
Multiple use-after-free vulnerabilities in libxml2 2.9.0 and possibly other versions might allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via vectors related to the (1) htmlParseChunk and (2) xmldecl_done functions, as demonstrated by a buffer overflow in the xmlBufGetInputBase function.
How severe is CVE-2013-1969?
CVE-2013-1969 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2013-1969 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2013-1969?
CVE-2013-1969 affects Xmlsoft Libxml2. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2013-1969?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2013-1969 published?
CVE-2013-1969 was published on 2013-04-25 and last updated on 2026-06-16.

References

Affected products (1)

More vulnerabilities in Xmlsoft Libxml2

All CVEs affecting Xmlsoft Libxml2 →

Other CWE-399 (Resource Management Errors) vulnerabilities

Browse all CWE-399 (Resource Management Errors) vulnerabilities →