CVE-2014-7911

HIGHCVSS v2 · 7.27.2
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.2 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:L/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 25% exploitation probability in the next 30 days; it does not lift the v2 base. EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated) sets EG Risk's exploitation input, not EPSS. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Elevated
7.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 25%CVSS v2: 7.2Exploit: Public PoCExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2014 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

The CVE record's description, written by its CNA (Chrome), states the affected versions: "luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.0 does not verify that deserialization will result in an object that met the requirements for seria…" No release containing a fix is confirmed on record.

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.0 does not verify that deserialization will result in an object that met the requirements for serialization, which allows attackers to execute arbitrary code via a crafted finalize method for a serialized object in an ArrayMap Parcel within an intent sent to system_service, as demonstrated by the finalize method of android.os.BinderProxy, aka Bug 15874291.

CVSS v2.0 (legacy)
7.2HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.2HIGHlow confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2014. If the vendor still supports the product, apply the fixed version it names within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
25%
EPSS %ILE
97th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix has been recorded since the CVE record was published in 2014. If the vendor still supports the product, apply the fixed version it names within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 15, 2014

Last Modified

May 6, 2026

References (2)

Data Freshness Timeline

(refreshed 7× in last 7d / 18× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 87 of 120 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 13 repeat rows among the latest 100 are merged into the row they repeat. The 33 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 01:21 UTCEG score recompute
  2. 2026-10-11 13:40 UTCEPSS rescoreEPSS 25% · 97th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 25% · 97th percentile
  4. 2026-10-09 20:01 UTCEPSS rescoreEPSS 25% · 97th percentile
  5. 2026-10-08 16:34 UTCEPSS rescoreEPSS 25% · 97th percentile
  6. 2026-10-07 23:39 UTCEPSS rescoreEPSS 25% · 97th percentile
  7. 2026-10-06 15:11 UTCEPSS rescoreEPSS 25% · 97th percentile
  8. 2026-10-04 23:17 UTCEPSS rescoreEPSS 25% · 97th percentile
  9. 2026-10-03 14:21 UTCEPSS rescoreEPSS 25% · 97th percentile
  10. 2026-10-01 19:43 UTCEPSS rescoreEPSS 25% · 97th percentile
  11. 2026-09-30 14:58 UTCEPSS rescoreEPSS 25% · 97th percentile
  12. 2026-09-30 08:58 UTCEG score recompute
  13. 2026-09-27 13:39 UTCEPSS rescoreEPSS 25% · 97th percentile
  14. 2026-09-26 15:53 UTCEPSS rescoreEPSS 25% · 97th percentile
  15. 2026-09-18 19:21 UTCEPSS rescoreEPSS 25% · 97th percentile
  16. 2026-09-17 19:21 UTCEPSS rescoreEPSS 25% · 97th percentile
  17. 2026-09-15 03:04 UTCEPSS rescoreEPSS 25% · 97th percentile
  18. 2026-09-13 16:41 UTCEPSS rescoreEPSS 25% · 97th percentile
  19. 2026-09-12 14:55 UTCEPSS rescoreEPSS 25% · 97th percentile
  20. 2026-09-11 09:31 UTCEPSS rescoreEPSS 25% · 97th percentile
  21. 2026-09-07 15:56 UTCEPSS rescoreEPSS 25% · 97th percentile
  22. 2026-09-06 13:42 UTCEPSS rescoreEPSS 25% · 97th percentile
  23. 2026-09-05 15:23 UTCEPSS rescoreEPSS 25% · 97th percentile
  24. 2026-09-04 13:55 UTCEPSS rescoreEPSS 25% · 97th percentile
  25. 2026-09-02 14:07 UTCEPSS rescoreEPSS 25% · 97th percentile
Show 62 more
  1. 2026-09-01 13:48 UTCEPSS rescoreEPSS 25% · 97th percentile
  2. 2026-08-30 19:12 UTCEPSS rescoreEPSS 25% · 97th percentile
  3. 2026-08-28 21:34 UTCEPSS rescoreEPSS 25% · 97th percentile
  4. 2026-08-27 14:20 UTCEPSS rescoreEPSS 25% · 97th percentile
  5. 2026-08-26 14:41 UTCEPSS rescoreEPSS 25% · 97th percentile
  6. 2026-08-25 13:44 UTCEPSS rescoreEPSS 25% · 97th percentile
  7. 2026-08-21 23:44 UTCEPSS rescoreEPSS 25% · 97th percentile
  8. 2026-08-20 22:50 UTCEPSS rescoreEPSS 25% · 97th percentile
  9. 2026-08-19 16:59 UTCEPSS rescoreEPSS 25% · 97th percentile
  10. 2026-08-18 13:43 UTCEPSS rescoreEPSS 25% · 97th percentile
  11. 2026-08-16 14:51 UTCEPSS rescoreEPSS 25% · 97th percentile
  12. 2026-08-16 02:09 UTCEPSS rescoreEPSS 25% · 97th percentile
  13. 2026-08-15 01:25 UTCEPSS rescoreEPSS 25% · 97th percentile
  14. 2026-08-12 13:46 UTCEPSS rescoreEPSS 25% · 97th percentile
  15. 2026-08-08 16:31 UTCEPSS rescoreEPSS 25% · 97th percentile
  16. 2026-08-07 16:21 UTCEPSS rescoreEPSS 25% · 97th percentile
  17. 2026-08-06 13:42 UTCEPSS rescoreEPSS 25% · 97th percentile
  18. 2026-08-05 19:12 UTCEPSS rescoreEPSS 25% · 97th percentile
  19. 2026-08-04 15:04 UTCEPSS rescoreEPSS 25% · 97th percentile
  20. 2026-08-02 02:22 UTCEPSS rescoreEPSS 25% · 97th percentile
  21. 2026-08-01 04:11 UTCEPSS rescoreEPSS 25% · 97th percentile
  22. 2026-07-30 16:23 UTCEPSS rescoreEPSS 25% · 97th percentile
  23. 2026-07-30 01:26 UTCEPSS rescoreEPSS 25% · 97th percentile
  24. 2026-07-28 15:31 UTCEPSS rescoreEPSS 25% · 97th percentile
  25. 2026-07-26 14:50 UTCEPSS rescoreEPSS 25% · 97th percentile
  26. 2026-07-26 13:52 UTCEG score recomputeFirst assessed: 7.2 HIGH
  27. 2026-07-24 14:13 UTCEPSS rescoreEPSS 25% · 97th percentile
  28. 2026-07-23 14:14 UTCEPSS rescoreEPSS 25% · 97th percentile
  29. 2026-07-23 01:14 UTCEG score recompute
  30. 2026-07-23 00:17 UTCEG score recompute
  31. 2026-07-22 21:56 UTCEG score recompute
  32. 2026-07-22 14:04 UTCEPSS rescoreEPSS 25% · 97th percentile
  33. 2026-07-21 15:21 UTCEPSS rescoreEPSS 25% · 97th percentile
  34. 2026-07-20 17:03 UTCEPSS rescoreEPSS 25% · 97th percentile
  35. 2026-07-19 14:27 UTCEPSS rescoreEPSS 25% · 97th percentile
  36. 2026-07-19 02:26 UTCEPSS rescoreEPSS 25% · 97th percentile
  37. 2026-07-18 10:00 UTCEPSS rescoreEPSS 25% · 97th percentile
  38. 2026-07-16 16:59 UTCEPSS rescoreEPSS 25% · 97th percentile
  39. 2026-07-15 16:54 UTCEPSS rescoreEPSS 25% · 97th percentile
  40. 2026-07-15 01:56 UTCEPSS rescoreEPSS 25% · 97th percentile
  41. 2026-07-13 22:26 UTCEPSS rescoreEPSS 24% · 97th percentile
  42. 2026-07-13 06:08 UTCEPSS rescoreEPSS 24% · 97th percentile
  43. 2026-07-12 05:42 UTCEPSS rescoreEPSS 24% · 97th percentile
  44. 2026-07-11 08:23 UTCEPSS rescoreEPSS 24% · 97th percentile
  45. 2026-07-09 19:05 UTCEPSS rescoreEPSS 24% · 97th percentile
  46. 2026-07-08 15:10 UTCEPSS rescoreEPSS 24% · 97th percentile
  47. 2026-07-07 13:42 UTCEPSS rescoreEPSS 24% · 97th percentile
  48. 2026-07-06 16:24 UTCEPSS rescoreEPSS 24% · 97th percentile
  49. 2026-07-06 02:20 UTCEPSS rescoreEPSS 24% · 97th percentile
  50. 2026-07-05 02:26 UTCEPSS rescoreEPSS 24% · 97th percentile
  51. 2026-07-04 06:27 UTCEPSS rescoreEPSS 24% · 97th percentile
  52. 2026-07-01 15:02 UTCEPSS rescoreEPSS 24% · 97th percentile
  53. 2026-06-30 23:19 UTCEPSS rescoreEPSS 24% · 97th percentile
  54. 2026-06-28 04:53 UTCEPSS rescoreEPSS 24% · 97th percentile
  55. 2026-06-27 03:05 UTCEPSS rescoreEPSS 24% · 97th percentile
  56. 2026-06-25 13:47 UTCEPSS rescoreEPSS 24% · 97th percentile
  57. 2026-06-24 14:02 UTCEPSS rescoreEPSS 24% · 97th percentile
  58. 2026-06-23 21:30 UTCEPSS rescoreEPSS 24% · 97th percentile
  59. 2026-06-22 14:22 UTCEPSS rescoreEPSS 24% · 97th percentile
  60. 2026-06-21 01:57 UTCEPSS rescoreEPSS 24% · 97th percentile
  61. 2026-06-19 19:23 UTCEPSS rescoreEPSS 24% · 97th percentile
  62. 2026-06-18 17:49 UTCEPSS rescoreEPSS 24% · 97th percentile

Publicly available exploits

(5 references)

Public exploit code is referenced for this CVE (5 GitHub PoCs). No fix has been recorded since the CVE record was published in 2014. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system or retire the product.

  • GitHub PoCkoozxcv/CVE-2014-7911-CVE-2014-4322_get_root_privilege
    Published Mar 23, 2016

    CVE-2014-7911 vulnerability and CVE-2014-4322 vulnerability to get root privilege!

    Open source ↗
  • GitHub PoCGeneBlue/cve-2014-7911-exp
    Published Dec 29, 2015

    exploit for cve-2014-7911; android; java deserialization ;system privilege;ace;

    Open source ↗
  • GitHub PoCheeeeen/CVE-2014-7911poc
    Published Nov 3, 2015
    Open source ↗
  • GitHub PoCele7enxxh/CVE-2014-7911
    Published Jul 3, 2015
    Open source ↗
  • GitHub PoCretme7/CVE-2014-7911_poc
    Published Jan 26, 2015

    Local root exploit for Nexus5 Android 4.4.4(KTU84P)

    Open source ↗

Frequently asked(4)

What is CVE-2014-7911?
CVE-2014-7911 is a high-severity vulnerability; its CVE record was published on December 15, 2014. luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.0 does not verify that deserialization will result in an object that met the requirements for serialization, which allows attackers to execute arbitrary code via a crafted…
When was CVE-2014-7911 made public?
CVE-2014-7911 was made public on November 19, 2014: that is the date its CVE record's CNA, Chrome, gives for when the vulnerability was made public. The CVE record itself was published on December 15, 2014. EchelonGraph's copy of the record carries a last-modified date of May 6, 2026; the record at its source may have been updated since.
Is CVE-2014-7911 actively exploited?
CVE-2014-7911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
How do I remediate CVE-2014-7911?
No fix for CVE-2014-7911 has been recorded since its CVE record was published in 2014. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product. The CVE record's description, written by its CNA (Chrome), states the affected versions: "luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.0 does not verify that deserialization will result in an object that met the requirements for seria…" No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2014-7911

Explore →

Is Your Infrastructure Affected by CVE-2014-7911?

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