PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-0177 Google CVE debrief

A possible out-of-bounds read due to a missing bounds check in crypto-aes.c could lead to local information disclosure with System execution privileges needed. This vulnerability affects Google Android systems, specifically in the do_sss_aes_gcm_256_op function of crypto-aes.c. The vulnerability has a CVSS score of 4.4 and is classified as MEDIUM severity. Defenders and system administrators should assess exposure and verify patches to prevent potential local information disclosure. The CVE record and NVD vulnerability detail page provide information on the vulnerability, its CVSS score, and potential impact.

Vendor
Google
Product
Android
CVSS
MEDIUM 4.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-15
Original CVE updated
2026-09-21
Advisory published
2026-09-15
Advisory updated
2026-09-21

Who should care

Defenders and system administrators responsible for Google Android systems should assess exposure and verify patches to prevent potential local information disclosure. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Additionally, they should plan vendor-supported updates or mitigations through normal change control where exposure is con-

Why it matters

Defenders and system administrators responsible for Google Android systems should assess exposure and verify patches to prevent potential local information disclosure.

  • Local information disclosure with System execution privileges needed

Technical summary

A possible out-of-bounds read due to a missing bounds check in crypto-aes.c could lead to local information disclosure with System execution privileges needed. The vulnerability is specifically located in the do_sss_aes_gcm_256_op function and affects Google Android systems. The CVSS score of 4.4 indicates a MEDIUM severity level. To address this vulnerability, defenders and system administrators should assess exposure and verify patches.

Defensive priority

Verify and apply patches according to vendor advisories, assess System execution privilege requirements, and monitor for potential information disclosure.

Recommended defensive actions

  • Verify and apply patches according to vendor advisories
  • Assess System execution privilege requirements
  • Monitor for potential information disclosure

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, its CVSS score, and potential impact. The vulnerability is in the do_sss_aes_gcm_256_op function of crypto-aes.c, which could lead to local information disclosure with System execution privileges needed. The source-provided CVE metadata and official NIST NVD detail page offer further details on the vulnerability and its potential impact. Defenders should verify patches according to vendor adviso-

Sources and references

Verified primary and authoritative sources

  • CVE-2026-0177 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-0177

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-0177 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-0177

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.