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