In multiple locations, there is a possible use-after-free due to a race condition. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2026-55318
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(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 computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
Advisory Details (1)
Auto-updated Sep 15, 2026Pixel Update Bulletin—September 2026 | Android Open Source Project
https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01Vendor Advisories for CVE-2026-55318(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 24× 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.
- 2026-09-20 07:52 UTCGHSA enrichment
- 2026-09-19 19:47 UTCEG score recompute
- 2026-09-19 19:47 UTCGHSA enrichment
- 2026-09-19 07:45 UTCGHSA enrichment
- 2026-09-18 19:42 UTCEG score recompute
- 2026-09-18 19:42 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 07:40 UTCGHSA enrichment
- 2026-09-17 19:38 UTCEG score recompute
- 2026-09-17 19:38 UTCGHSA enrichment
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 07:36 UTCGHSA enrichment
- 2026-09-16 19:34 UTCGHSA enrichment
- 2026-09-16 17:54 UTCEG score recompute
- 2026-09-16 17:54 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 04:26 UTCGHSA enrichment
- 2026-09-16 04:16 UTCEG score recompute
- 2026-09-16 04:16 UTCGHSA enrichment
- 2026-09-15 20:35 UTCEG score recompute▲ 8.80
- 2026-09-15 20:27 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
- 2026-09-15 19:32 UTCNVD update
- 2026-09-15 18:39 UTCEG score recompute
- 2026-09-15 18:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-362 · CWE-416
Frequently asked(5)
What is CVE-2026-55318?
When was CVE-2026-55318 disclosed?
Is CVE-2026-55318 actively exploited?
What is the CVSS score of CVE-2026-55318?
How do I remediate CVE-2026-55318?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55318
Is Your Infrastructure Affected by CVE-2026-55318?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.