CVE-2024-31328

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
8.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: 8.8Exploit: None knownExposed: 0

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

In broadcastIntentLockedTraced of BroadcastController.java, there is a possible way to launch arbitrary activities from the background on the paired companion phone 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
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

March 2, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

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

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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 15:40 UTCEPSS rescore
  2. 2026-09-18 19:26 UTCEPSS rescore
  3. 2026-09-16 14:06 UTCEPSS rescore
  4. 2026-09-16 14:06 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-15 03:08 UTCEPSS rescore
  7. 2026-09-13 16:45 UTCEPSS rescore
  8. 2026-09-12 14:59 UTCEPSS rescore
  9. 2026-09-11 14:51 UTCEPSS rescore
  10. 2026-09-11 09:35 UTCEPSS rescore
  11. 2026-09-08 21:58 UTCEPSS rescore
  12. 2026-09-07 15:59 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-05 15:26 UTCEPSS rescore
  16. 2026-09-04 13:58 UTCEPSS rescore
  17. 2026-09-04 05:05 UTCEPSS rescore
  18. 2026-09-01 13:52 UTCEPSS rescore
  19. 2026-08-30 19:15 UTCEPSS rescore
  20. 2026-08-30 01:20 UTCEPSS rescore
  21. 2026-08-28 21:39 UTCEPSS rescore
  22. 2026-08-27 14:23 UTCEPSS rescore
  23. 2026-08-26 14:44 UTCEPSS rescore
  24. 2026-08-25 13:47 UTCEPSS rescore
  25. 2026-08-24 14:15 UTCEPSS rescore
Show 52 more
  1. 2026-08-23 00:17 UTCEPSS rescore
  2. 2026-08-21 23:47 UTCEPSS rescore
  3. 2026-08-20 22:53 UTCEPSS rescore
  4. 2026-08-19 17:02 UTCEPSS rescore
  5. 2026-08-19 17:02 UTCEPSS rescore
  6. 2026-08-18 13:46 UTCEPSS rescore
  7. 2026-08-18 13:46 UTCEPSS rescore
  8. 2026-08-17 13:45 UTCEPSS rescore
  9. 2026-08-16 14:54 UTCEPSS rescore
  10. 2026-08-16 02:13 UTCEPSS rescore
  11. 2026-08-15 01:28 UTCEPSS rescore
  12. 2026-08-14 21:26 UTCGHSA enrichment
  13. 2026-08-14 08:43 UTCEG score recompute
  14. 2026-08-14 08:43 UTCGHSA enrichment
  15. 2026-08-13 21:59 UTCEPSS rescore
  16. 2026-08-13 00:35 UTCEG score recompute
  17. 2026-08-13 00:35 UTCGHSA enrichment
  18. 2026-08-12 13:49 UTCEPSS rescore
  19. 2026-08-11 23:25 UTCEG score recompute
  20. 2026-08-11 23:24 UTCGHSA enrichment
  21. 2026-08-11 13:40 UTCEPSS rescore
  22. 2026-08-11 05:59 UTCEG score recompute
  23. 2026-08-11 05:59 UTCGHSA enrichment
  24. 2026-08-10 23:58 UTCEPSS rescore
  25. 2026-08-10 09:29 UTCGHSA enrichment
  26. 2026-08-09 20:56 UTCEG score recompute
  27. 2026-08-09 20:56 UTCGHSA enrichment
  28. 2026-08-09 13:45 UTCEPSS rescore
  29. 2026-08-09 08:21 UTCEG score recompute
  30. 2026-08-09 08:21 UTCGHSA enrichment
  31. 2026-08-08 16:35 UTCEPSS rescore
  32. 2026-08-08 08:52 UTCGHSA enrichment
  33. 2026-08-07 20:18 UTCEG score recompute
  34. 2026-08-07 20:18 UTCGHSA enrichment
  35. 2026-08-07 16:25 UTCEPSS rescore
  36. 2026-08-06 13:45 UTCEPSS rescore
  37. 2026-08-06 02:50 UTCEG score recompute
  38. 2026-08-06 02:50 UTCGHSA enrichment
  39. 2026-08-05 19:16 UTCEPSS rescore
  40. 2026-08-04 15:08 UTCEPSS rescore
  41. 2026-08-04 04:36 UTCEG score recompute
  42. 2026-08-04 04:36 UTCGHSA enrichment
  43. 2026-08-03 10:34 UTCEPSS rescore
  44. 2026-08-02 19:11 UTCEG score recompute
  45. 2026-08-02 19:11 UTCGHSA enrichment
  46. 2026-08-02 02:25 UTCEPSS rescore
  47. 2026-08-02 02:25 UTCEPSS rescore
  48. 2026-08-01 04:14 UTCEPSS rescore
  49. 2026-07-28 15:34 UTCEPSS rescore
  50. 2026-07-27 14:11 UTCEPSS rescore
  51. 2026-07-27 13:57 UTCEG score recompute
  52. 2026-07-27 13:57 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-31328?
CVE-2024-31328 is a high vulnerability published on March 2, 2026. In broadcastIntentLockedTraced of BroadcastController.java, there is a possible way to launch arbitrary activities from the background on the paired companion phone due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed.…
When was CVE-2024-31328 disclosed?
CVE-2024-31328 was first published in the National Vulnerability Database on March 2, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-31328 actively exploited?
CVE-2024-31328 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.2% of all scored CVEs.
What is the CVSS score of CVE-2024-31328?
CVE-2024-31328 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2024-31328?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-31328, 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-2024-31328

Explore →

Is Your Infrastructure Affected by CVE-2024-31328?

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

Start Free Scan →Browse All CVEs