# CVE-2026-55348: Google Trusty out-of-bounds read via sign extension in shared memory

Source: https://junglewise.ai/threats/cve-2026-55348-in-getsharedmemory-of-trusty-shared-memory-manager-cc-there-is-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-55348 · Severity: info · Published 2026-11-10

Trusty is a secure operating system that runs on Google Pixel devices and protects sensitive functions like fingerprint authentication and encryption keys. A flaw in the shared memory manager could allow a local attacker with system privileges to read sensitive data from memory by exploiting a sign-extension bug in buffer size validation. No user interaction is required to exploit this vulnerability.

Technologies: [Google Trusty](https://junglewise.ai/threats/technologies/trusty). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-55348 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-55348 being exploited in the wild.

**How severe is CVE-2026-55348?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Trusty.

**Is there a fix for CVE-2026-55348?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-55348 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-55348?** Check whether you run Google Trusty. 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

An improper or implicit cast of a negative buffer size in GetSharedMemory of trusty_shared_memory_manager.cc allows sign-extension to cause an out-of-bounds read. The vulnerability requires local access with system execution privileges. This is a classic integer handling issue that can leak confidential data stored in memory.

## Affected products

- Google Trusty

## Timeline

- 2026-11-10: disclosed

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01)

## Related threats

- [Google Trusty TOCTOU race condition in vqueue](https://junglewise.ai/threats/cve-2026-56916-in-vqueue-get-avail-buf-locked-of-trusty-kernel-lib-trusty-vqueue)
- [ARM64_TLBI memory corruption in Trusty kernel](https://junglewise.ai/threats/cve-2026-58728-arm64-tlbi-memory-corruption-in-trusty-kernel)
- [Google Trusty out-of-bounds write via race condition](https://junglewise.ai/threats/cve-2026-58701-google-trusty-out-of-bounds-write-via-race-condition)