Quick answers
- Is CVE-2026-58701 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58701 being exploited in the wild.
- How severe is CVE-2026-58701?
- High severity, with a CVSS score of 7, published 15 September 2026.
- Which products and versions are affected?
- Google Trusty Unspecified; patch available as of 2026-09-05 security patch level.
- Is there a fix for CVE-2026-58701?
- A patch was published on 2026-09-05: Google Pixel devices received updates to 2026-09-05 patch level addressing this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58701 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-58701?
- Check whether you run Google Android or Google Trusty at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A race condition exists in the trusty_dputc function of generic-arm64-smcall.c in Google Trusty, leading to an out-of-bounds write vulnerability. The vulnerability is reachable locally with System execution privileges and does not require user interaction for exploitation. An attacker with system-level access can exploit this race condition to write beyond memory boundaries, achieving local privilege escalation within the Trusty environment.
Affected products
- Google Trusty Unspecified; patch available as of 2026-09-05 security patch level
Timeline
- 2026-09-15: disclosed
- 2026-09-05: patched: Google Pixel devices received updates to 2026-09-05 patch level addressing this issue