CVE-2015-6626
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedlibstagefright in Android before 5.1.1 LMY48Z and 6.0 before 2015-12-01 allows remote attackers to obtain sensitive information, and consequently bypass an unspecified protection mechanism, via unknown vectors, as demonstrated by obtaining Signature or SignatureOrSystem access, aka internal bug 24310423.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencelibstagefright in Android before 5.1.1 LMY48Z and 6.0 before December 2015 contains an information disclosure vulnerability that allows remote attackers to obtain sensitive information enabling bypass of Signature or SignatureOrSystem protection mechanisms. This is a logic/initialization flaw in the media framework rather than memory corruption, allowing privilege escalation through disclosed sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.0, < 5.1.1= 6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version is 5.0, 5.1.0, or exactly 6.0 (the affected versions)
-
Check security patch levelGo to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Patch level is earlier than December 2015 or not set (the fix requires December 2015 or later patch level)
-
Confirm libstagefright component presenceCheck for libstagefright.so in /system/lib/ or run 'pm list packages -i android.media' via ADB to verify media framework is installedAffected if libstagefright is present (this is the component with the vulnerability; it is present on all standard Android devices)
-
Verify build fingerprint matches fixed buildsRun 'getprop ro.build.fingerprint' via ADB and check if it contains 'LMY48Z' for 5.1.1 branch or a December 2015+ date for 6.0Affected if Build does not contain LMY48Z or a December 2015+ date marker
User is affected if the device runs Android 5.0 through 5.1.0 or exactly Android 6.0, and the security patch level is earlier than December 2015.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.1.1
Apply Android system updates to version 5.1.1 LMY48Z or 6.0 with December 2015 security patch level or later. This is a platform-level fix requiring OS updates from device vendors; no application-level mitigation is available.
- Consultation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6626 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data