CVE-2026-49883

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

In checkReadPermission of PermissionsManager.java, there is a possible way to monitor sensitive device state data due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
40(Track)
EG Risk 40/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
Severity55% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 14, 2026

Advisory Details (1)

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

Wear OS Security Bulletin—September 2026  |  Android Open Source Project

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

Vendor Advisories for CVE-2026-49883(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 15× in last 7d / 75× 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-24 16:18 UTCEG score recompute
  2. 2026-09-24 16:18 UTCGHSA enrichment
  3. 2026-09-23 17:53 UTCEPSS rescore
  4. 2026-09-23 16:08 UTCGHSA enrichment
  5. 2026-09-22 15:57 UTCEG score recompute
  6. 2026-09-22 15:57 UTCGHSA enrichment
  7. 2026-09-21 15:45 UTCEG score recompute
  8. 2026-09-21 15:45 UTCGHSA enrichment
  9. 2026-09-20 20:16 UTCEPSS rescore
  10. 2026-09-20 15:34 UTCEG score recompute
  11. 2026-09-20 15:34 UTCGHSA enrichment
  12. 2026-09-19 15:24 UTCEG score recompute
  13. 2026-09-19 15:24 UTCGHSA enrichment
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-18 15:13 UTCGHSA enrichment
  16. 2026-09-17 15:03 UTCGHSA enrichment
  17. 2026-09-16 14:53 UTCEG score recompute
  18. 2026-09-16 14:53 UTCGHSA enrichment
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 14:42 UTCEG score recompute
  22. 2026-09-15 14:42 UTCGHSA enrichment
  23. 2026-09-14 14:32 UTCEG score recompute▼ 4.50
  24. 2026-09-14 14:32 UTCGHSA enrichment
  25. 2026-09-14 14:29 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
Show 50 more
  1. 2026-09-14 11:19 UTCGHSA enrichment
  2. 2026-09-14 07:03 UTCGHSA enrichment
  3. 2026-09-14 02:47 UTCGHSA enrichment
  4. 2026-09-13 22:30 UTCGHSA enrichment
  5. 2026-09-13 18:14 UTCEG score recompute
  6. 2026-09-13 18:14 UTCGHSA enrichment
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-13 13:57 UTCGHSA enrichment
  9. 2026-09-13 09:41 UTCGHSA enrichment
  10. 2026-09-13 05:25 UTCGHSA enrichment
  11. 2026-09-13 01:09 UTCGHSA enrichment
  12. 2026-09-12 20:53 UTCGHSA enrichment
  13. 2026-09-12 16:36 UTCEG score recompute
  14. 2026-09-12 16:36 UTCGHSA enrichment
  15. 2026-09-12 12:20 UTCGHSA enrichment
  16. 2026-09-12 08:03 UTCGHSA enrichment
  17. 2026-09-12 03:46 UTCGHSA enrichment
  18. 2026-09-11 23:30 UTCGHSA enrichment
  19. 2026-09-11 19:13 UTCGHSA enrichment
  20. 2026-09-11 14:56 UTCEG score recompute
  21. 2026-09-11 14:56 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 10:39 UTCEG score recompute
  24. 2026-09-11 10:38 UTCGHSA enrichment
  25. 2026-09-11 06:20 UTCGHSA enrichment
  26. 2026-09-11 02:03 UTCGHSA enrichment
  27. 2026-09-10 21:47 UTCGHSA enrichment
  28. 2026-09-10 17:30 UTCGHSA enrichment
  29. 2026-09-10 13:13 UTCEG score recompute
  30. 2026-09-10 13:13 UTCGHSA enrichment
  31. 2026-09-10 09:35 UTCEPSS rescore
  32. 2026-09-10 08:56 UTCGHSA enrichment
  33. 2026-09-10 04:36 UTCEG score recompute
  34. 2026-09-10 04:36 UTCGHSA enrichment
  35. 2026-09-10 04:04 UTCEG score recompute
  36. 2026-09-10 04:04 UTCGHSA enrichment
  37. 2026-09-10 01:49 UTCGHSA enrichment
  38. 2026-09-09 21:32 UTCEG score recompute
  39. 2026-09-09 21:32 UTCGHSA enrichment
  40. 2026-09-09 20:49 UTCEG score recompute
  41. 2026-09-09 20:49 UTCGHSA enrichment
  42. 2026-09-09 19:10 UTCGHSA enrichment
  43. 2026-09-09 14:54 UTCGHSA enrichment
  44. 2026-09-09 10:36 UTCGHSA enrichment
  45. 2026-09-09 06:20 UTCGHSA enrichment
  46. 2026-09-09 02:04 UTCGHSA enrichment
  47. 2026-09-08 21:44 UTCGHSA enrichment
  48. 2026-09-08 20:37 UTCEG score recompute
  49. 2026-09-08 19:21 UTCEG score recompute
  50. 2026-09-08 19:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49883?
CVE-2026-49883 is a medium vulnerability published on September 8, 2026. In checkReadPermission of PermissionsManager.java, there is a possible way to monitor sensitive device state data due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-49883 disclosed?
CVE-2026-49883 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49883 actively exploited?
CVE-2026-49883 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 94.0% of all scored CVEs.
What is the CVSS score of CVE-2026-49883?
CVE-2026-49883 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-49883?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49883, 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-49883

Explore →

Is Your Infrastructure Affected by CVE-2026-49883?

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

Book a Demo →Browse All CVEs