CVE-2011-2939

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 3%CVSS: Exploit: NoneExposed: 0

A fix is available — apply it.

Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow.

CVSS v3
EG Score
0.0(none)
EPSS
83.8%
KEV
Not listed

Published

January 13, 2012

Last Modified

April 29, 2026

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuperl (5.8.8-12ubuntu0.7) @ hardy2026-05-29ubuntu
redhatperl-4:5.10.1-119.el6_1.12011-11-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Frequently asked(4)

What is CVE-2011-2939?
CVE-2011-2939 is a none vulnerability published on January 13, 2012. Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow.
When was CVE-2011-2939 disclosed?
CVE-2011-2939 was first published in the National Vulnerability Database on January 13, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-2939 actively exploited?
CVE-2011-2939 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2011-2939?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-2939, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2011-2939

Explore →

Is Your Infrastructure Affected by CVE-2011-2939?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.