Skip to content
Fencer Intel
medium 6.8

CVE-2011-3146 json

librsvg before 2.34.1 uses the node name to identify the type of node, which allows context-dependent attackers to cause a denial of servic…

published 2012-09-05 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3114

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.4%
EPSS 4.4% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

librsvg before 2.34.1 uses the node name to identify the type of node, which allows context-dependent attackers to cause a denial of service (NULL pointer dereference) and possibly execute arbitrary code via a SVG file with a node with the element name starting with "fe," which is misidentified as a RsvgFilterPrimitive.

Patch / fix

  • librsvg Debian 14, Debian 13, Debian 12 2.34.1-1

debian advisories DEBIAN-CVE-2011-3146

  • librsvg2 RHEL 6 2.26.0-5.el6_1.1

red hat advisories RHSA-2011:1289

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-3146 updated cvss 6.8

librsvg: object type mismatch leading to invalid pointer dereference

  • Red Hat Enterprise Linux Server (v. 6) librsvg2 2.26.0-5.el6_1.1
    fixed: vendor fix RHSA-2011:1289
  • Red Hat Enterprise Linux 4 librsvg2 Red Hat Enterprise Linux 5 librsvg2
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.42% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • git.gnome.org http://git.gnome.org/browse/librsvg/commit/?id=34c95743ca692ea0e44778e41a7c0a129363de84 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.