CVE-2017-13156

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 20%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An elevation of privilege vulnerability in the Android system (art). Product: Android. Versions: 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0. Android ID A-64211847.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
97.1%
KEV
Not listed

Published

December 6, 2017

Last Modified

May 13, 2026

References (6)

Data Freshness Timeline

(refreshed 9× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-28 14:04 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-22 14:23 UTCEPSS rescore
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-21 14:54 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-18 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-16 17:50 UTCEPSS rescore
Show 36 more
  1. 2026-06-15 17:45 UTCEPSS rescore
  2. 2026-06-14 23:14 UTCEPSS rescore
  3. 2026-06-14 23:14 UTCEPSS rescore
  4. 2026-06-13 22:57 UTCEPSS rescore
  5. 2026-06-12 23:09 UTCEPSS rescore
  6. 2026-06-10 22:15 UTCEPSS rescore
  7. 2026-06-07 15:22 UTCEPSS rescore
  8. 2026-06-07 15:22 UTCEPSS rescore
  9. 2026-06-06 13:45 UTCEPSS rescore
  10. 2026-06-06 13:45 UTCEPSS rescore
  11. 2026-06-05 22:44 UTCEPSS rescore
  12. 2026-06-05 06:08 UTCEPSS rescore
  13. 2026-06-05 06:08 UTCEPSS rescore
  14. 2026-06-04 13:10 UTCEPSS rescore
  15. 2026-06-04 13:10 UTCEPSS rescore
  16. 2026-06-02 20:11 UTCEPSS rescore
  17. 2026-06-02 20:11 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-05-31 00:14 UTCEPSS rescore
  21. 2026-05-29 13:41 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-28 13:42 UTCEPSS rescore
  24. 2026-05-27 13:38 UTCEPSS rescore
  25. 2026-05-27 13:38 UTCEPSS rescore
  26. 2026-05-26 07:17 UTCEPSS rescore
  27. 2026-05-26 07:17 UTCEPSS rescore
  28. 2026-05-22 21:15 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-22 21:15 UTCEPSS rescore
  31. 2026-05-22 07:28 UTCEG score recompute
  32. 2026-05-22 07:28 UTCGHSA enrichment
  33. 2026-05-20 22:37 UTCEPSS rescore
  34. 2026-05-20 22:37 UTCEPSS rescore
  35. 2026-05-18 21:30 UTCEPSS rescore
  36. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(8 references)

Working exploit code is in the public domain (1 Metasploit module) (6 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCnictjh/threatDemos
    First seen Aug 1, 2025

    Comprehensive Android security vulnerability demonstrations featuring CVE-2017-13156 (Janus), broadcast receiver exploitation, external storage threats, and rooted device attacks. Educational PoCs with working code, exploitation scripts, and security controls for developers and researchers. To be updated...

    Open source ↗
  • GitHub PoCl1ackerronin/Janus-Vulnerability-CVE-2017-13156-Exploit
    First seen Feb 20, 2024

    Android Application Vulnerability Exploit

    Open source ↗
  • GitHub PoCM507/CVE-2017-13156
    First seen Jun 10, 2022

    To determine if an APK is vulnerable to CVE-2017-13156

    Open source ↗
  • GitHub PoCtea9/CVE-2017-13156-Janus
    First seen Sep 3, 2020

    CVE-2017-13156-Janus复现

    Open source ↗
  • Exploit-DBEDB-47601✓ verified
    First seen Nov 8, 2019

    Android Janus - APK Signature Bypass (Metasploit)

    Open source ↗
  • GitHub PoCgiacomoferretti/janus-toolkit
    First seen Aug 25, 2019

    A collection of tools for the Janus exploit [CVE-2017-13156].

    Open source ↗
  • GitHub PoCxyzAsian/Janus-CVE-2017-13156
    First seen Dec 29, 2017
    Open source ↗
  • Metasploitexploit/android/local/janus✓ verified
    First seen Jul 31, 2017

    Android Janus APK Signature bypass

    Open source ↗

Frequently asked(5)

What is CVE-2017-13156?
CVE-2017-13156 is a high vulnerability published on December 6, 2017. An elevation of privilege vulnerability in the Android system (art). Product: Android. Versions: 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0. Android ID A-64211847.
When was CVE-2017-13156 disclosed?
CVE-2017-13156 was first published in the National Vulnerability Database on December 6, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-13156 actively exploited?
CVE-2017-13156 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-13156?
CVE-2017-13156 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2017-13156?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-13156, 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-2017-13156

Explore →

Is Your Infrastructure Affected by CVE-2017-13156?

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

Start Free Scan →Browse All CVEs