Is there a public exploit for CVE-2026-55348?

No public exploit for CVE-2026-55348 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-55348?

CVE-2026-55348 scores CVSS 2.3 (v3.1), rated low. EPSS puts the chance of exploitation in the next 30 days at 0.12%.

What does CVE-2026-55348 affect?

CVE-2026-55348 affects Google Android.

2.3 Low

In GetSharedMemory of trustysharedmemorymanager.cc, there is a possible way to trigger an out of bounds read via sign extension of a…

CVE-2026-55348

In GetSharedMemory of trustysharedmemorymanager.cc, there is a possible way to trigger an out of bounds read via sign extension of a negative buffer size due to an improper or implicit cast. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.

Assessment

CVSS: 2.3 (v3.1)
Severity: Low
EPSS: 0.12% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 10 November 2026
Last updated: 13 November 2026
Affected: Google · Android
Assigner: Google_Devices

CVSS vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

At the source

EUVD (ENISA)

References

https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 3 + 2? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-55348