CVE-2026-49881

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

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

In serviceClassExists of InCallController.java, there is a possible arbitrary code execution due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
51(Track)
EG Risk 51/100SSVC: Track

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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 10, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
No patch confirmed yet.
generic

Android Security Bulletin—September 2026  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/2026/2026-09-01

Vendor Advisories for CVE-2026-49881(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 42× 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-09-19 20:01 UTCGHSA enrichment
  2. 2026-09-19 07:00 UTCEG score recompute
  3. 2026-09-19 07:00 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 17:58 UTCGHSA enrichment
  6. 2026-09-18 04:57 UTCEG score recompute
  7. 2026-09-18 04:57 UTCGHSA enrichment
  8. 2026-09-17 15:56 UTCGHSA enrichment
  9. 2026-09-17 02:55 UTCEG score recompute
  10. 2026-09-17 02:55 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 13:54 UTCEG score recompute
  13. 2026-09-16 13:54 UTCGHSA enrichment
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-16 00:41 UTCGHSA enrichment
  16. 2026-09-15 11:30 UTCEG score recompute
  17. 2026-09-15 11:30 UTCGHSA enrichment
  18. 2026-09-14 22:29 UTCGHSA enrichment
  19. 2026-09-14 09:28 UTCGHSA enrichment
  20. 2026-09-13 20:27 UTCEG score recompute
  21. 2026-09-13 20:27 UTCGHSA enrichment
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-13 07:26 UTCGHSA enrichment
  24. 2026-09-12 18:25 UTCGHSA enrichment
  25. 2026-09-12 05:24 UTCGHSA enrichment
Show 17 more
  1. 2026-09-11 16:23 UTCEG score recompute
  2. 2026-09-11 16:23 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 03:22 UTCEG score recompute
  5. 2026-09-11 03:22 UTCGHSA enrichment
  6. 2026-09-10 14:21 UTCGHSA enrichment
  7. 2026-09-10 13:45 UTCEG score recompute▲ 7.80
  8. 2026-09-10 13:45 UTCGHSA enrichment
  9. 2026-09-10 13:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-10 04:37 UTCGHSA enrichment
  12. 2026-09-10 04:33 UTCNVD update
  13. 2026-09-10 04:04 UTCGHSA enrichment
  14. 2026-09-10 04:00 UTCMITRE cvelistV5
  15. 2026-09-08 19:30 UTCNVD update
  16. 2026-09-08 18:31 UTCEG score recompute
  17. 2026-09-08 18:29 UTCMITRE cvelistV5first tracked

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCSupersonic/TLPE
    First seen Sep 9, 2026

    CVE-2026-49881, a logic issue in the InCallController class in Android 17's Telecom service that allows an unprivileged app to gain arbitrary code execution as UID 1000 system_server

    Open source ↗
  • GitHub PoCLSPosed/LSPromise
    First seen Jul 23, 2026

    Android complete exploit chain that enables privilege escalation from a local untrusted app to root/kernel, combined of CVE-2026-49881 and CVE-2026-43284

    Open source ↗

Frequently asked(5)

What is CVE-2026-49881?
CVE-2026-49881 is a high vulnerability published on September 8, 2026. In serviceClassExists of InCallController.java, there is a possible arbitrary code execution due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-49881 disclosed?
CVE-2026-49881 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49881 actively exploited?
CVE-2026-49881 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-49881?
CVE-2026-49881 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49881?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49881, 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-2026-49881

Explore →

Is Your Infrastructure Affected by CVE-2026-49881?

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

Start Free Scan →Browse All CVEs