CVE-2026-58704: In Cellular Modem, there is a possible permission bypass due to a logic error in the code.
Noroxi assessment
Priority: This week (action score 65/100)
- CISA has confirmed exploitation in the wild (Sep 16, 2026). Remediation deadline for US federal agencies: Sep 19, 2026.
- Probability of exploitation in the next 30 days: 0.62% (FIRST EPSS); higher than 50.4% of all records.
- Someone on the same network segment can trigger it. No account or password is required. 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).
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and 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 · CISA KEV · FIRST EPSS
In Cellular Modem, there is a possible permission bypass due to a logic error in the code. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- Published
- Sep 15, 2026
- Updated
- Oct 7, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- CWE-285
Report tools
Action score
65
Don’t wait for the next maintenance window.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Sep 16, 2026. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Sep 19, 2026.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- 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-58767Sep 15, 2026 · In multiple functions of arm-smmu-v3.c, there is a possible escalation of privilege due to a logic error in the code.26Monitor
- ← EarlierCVE-2026-58773Sep 15, 2026 · In link_load_gnss_image of link_device.c, there is a possible out-of-bounds write due to a missing bounds check.26Monitor
- Later →CVE-2026-28625Oct 5, 2026 · In multiple locations, there is a possible permission bypass due to a logic error in the code.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
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
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.
- Published
- CISA KEVsame day
- TodayNov 14, 2026+59 d
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-2025-26430376 days apartIn getDestinationForApp of SpaAppBridgeActivity, there is a possible cross-user file reveal due to a logic error in the code.31Monitor
- CVE-2026-0017197 days apartIn onChange of BiometricService.java, there is a possible way to enable fingerprint unlock due to a logic error in the code.30Monitor
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
- Someone on the same network segment can trigger it.
- No account or password is required.
- 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
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-285 · Improper AuthorizationCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/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)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Manipulating Opaque Client-based Data TokensCAPEC-39likelihood: High · Medium
- Bypassing ATA Password SecurityCAPEC-402
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
- Data from Local SystemT1005
- Query RegistryT1012
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Unsecured Credentials: Credentials in RegistryT1552.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Data Manipulation: Transmitted Data ManipulationT1565.002
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.