Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2012-2893

libxslt: Heap-double-free in xmlFreeNodeList

Overview

Published
26 Sep 2012
Modified
29 Apr 2026
Medium CVE
0 Registry packages
6 OS packages
4 Linux distributions
Yes Fix available

Description

Double free vulnerability in libxslt, as used in Google Chrome before 22.0.1229.79, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to XSL transforms.

Source: OX vulnerability database

Severity

6.8 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Medium
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Weakness: CWE-399

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 10 fixes

debian 4 releases · 1 package

fixed 4
libxslt
debian fixes for CVE-2012-2893
ReleasePackageFixed in
11 libxslt 1.1.26-14
12 libxslt 1.1.26-14
13 libxslt 1.1.26-14
14 libxslt 1.1.26-14

echo 1 release · 1 package

fixed 1
libxslt
echo fixes for CVE-2012-2893
ReleasePackageFixed in
libxslt 1.1.26-14

openSUSE 1 release · 2 packages

fixed 2
ungoogled-chromium chromedriver
openSUSE fixes for CVE-2012-2893
ReleasePackageFixed inAdvisory
Tumbleweed ungoogled-chromium +1 113.0.5672.92-1.1 openSUSE-SU-2024:12948-1
Tumbleweed chromedriver +1 55.0.2883.75-3.1 openSUSE-SU-2024:10171-1

root.io debian 3 releases · 1 package

fixed 3
rootio-libxslt
root.io debian fixes for CVE-2012-2893
ReleasePackageFixed in
11 rootio-libxslt 1.1.26-14
12 rootio-libxslt 1.1.26-14
13 rootio-libxslt 1.1.26-14

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.