CVE-2009-0136

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

A fix is available — apply it.

Multiple array index errors in the Audible::Tag::readTag function in metadata/audible/audibletag.cpp in Amarok 1.4.10 through 2.0.1 allow remote attackers to cause a denial of service (application crash) or execute arbitrary code via an Audible Audio (.aa) file with a crafted (1) nlen or (2) vlen Tag value, each of which can lead to an invalid pointer dereference, or the writing of a 0x00 byte to an arbitrary memory location, after an allocation failure.

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

Published

January 16, 2009

Last Modified

April 23, 2026

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuamarok (2:1.4.10-0ubuntu3.1) @ intrepid2026-05-30ubuntu

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.

Frequently asked(4)

What is CVE-2009-0136?
CVE-2009-0136 is a none vulnerability published on January 16, 2009. Multiple array index errors in the Audible::Tag::readTag function in metadata/audible/audibletag.cpp in Amarok 1.4.10 through 2.0.1 allow remote attackers to cause a denial of service (application crash) or execute arbitrary code via an Audible Audio (.aa) file with a crafted (1) nlen or (2) vlen…
When was CVE-2009-0136 disclosed?
CVE-2009-0136 was first published in the National Vulnerability Database on January 16, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-0136 actively exploited?
CVE-2009-0136 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2009-0136?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-0136, 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-2009-0136

Explore →

Is Your Infrastructure Affected by CVE-2009-0136?

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