CVE-2026-55318: In multiple locations, there is a possible use-after-free due to a race condition.
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 15, 2026
- Updated
- Sep 21, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-362
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| android | cpe:2.3:o:google:android |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Google_Devices). Independent of NVD's CPE analysis and usually ahead of it.
Google Android
- Android kernelaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- google androidall versions
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-2215A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel.KEV83Now
- CVE-2011-1823The vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trusts messages that are received from a PF_NETLINK socket, which allows…KEV73This week
- CVE-2015-1538Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android before 5.1.1 LMY48I…70This week
Published before and after this one in the same product
- ← EarlierCVE-2026-55306Sep 15, 2026 · In Cellular Modem, there is a possible denial of service due to improper input validation.30Monitor
- ← EarlierCVE-2026-55317Sep 15, 2026 · In printf of printf.c, there is a possible out-of-bounds write due to improper input validation.26Monitor
- Later →CVE-2026-55323Sep 15, 2026 · In gf_base_update_finger_base of gf_base.c, there is a possible out-of-bounds write due to a heap buffer overflow.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-006890 days apartIn createSessionInternal of PackageInstallerService.java, there is a possible method to remove a DPC app from a managed device without DO…40Plan
- CVE-2026-008390 days apartIn Nfc::eventCallback() of Nfc.h, there is a possible use after free due to a race condition.40Plan
- CVE-2026-5885748 days apartIn decrypt of CryptoHalHidl.cpp, there is a possible use-after-free due to a race condition.32Monitor
- CVE-2026-286047 days apartIn multiple locations, there is a possible use after free due to a race condition.30Monitor
- CVE-2026-5904248 days apartIn __pkvm_pages_to_ppages of mmu.c, there is a possible out-of-bounds write due to a race condition.29Monitor
- CVE-2026-5904548 days apartIn multiple locations, there is a possible memory corruption due to a race condition.29Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-553660 days apartIn IP Multimedia Subsystem, there is a possible authentication bypass due to a logic error in the code.39Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1105 · Sep 16, 2026(Google Android/Pixel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.