CVE-2026-53763

Integrity bypass via wrapped AES-GCM length counters

Published Jul 6, 2026 · Updated Jul 6, 2026

Integer overflow in OP-TEE OS 3.0.0 through 4.10.0 allows local users to bypass AES-GCM integrity checks via oversized inputs. The ghash_update_lengths routine multiplies 32-bit byte counts by eight before GHASH, so payload or AAD lengths above 512 MiB overflow; 32-bit accumulated-length fields also wrap beyond 4 GiB. Exploitation requires a local low-privileged user to reach a TA that accepts arbitrary oversized AES-GCM operations, producing an incorrect tag that collides across lengths separated by multiples of 512 MiB.

CVSS severity3.8
Low
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Integer overflow in OP-TEE OS 3.0.0 through 4.10.0 allows local users to bypass AES-GCM integrity checks via oversized inputs. The ghash_update_lengths routine multiplies 32-bit byte counts by eight before GHASH, so payload or AAD lengths above 512 MiB overflow; 32-bit accumulated-length fields also wrap beyond 4 GiB. Exploitation requires a local low-privileged user to reach a TA that accepts arbitrary oversized AES-GCM operations, producing an incorrect tag that collides across lengths separated by multiples of 512 MiB.

The record

CVE
CVE-2026-53763
Published
Jul 6, 2026
Updated
Jul 6, 2026
Vendor
OP-TEE
Product
OP-TEE OS
Classifications
CWE-190
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 6, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 6, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 3.0.0, < 4.11.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

OP-TEE · OP-TEE OSversion=>= 3.0.0, < 4.11.0

Published CVSS scores

3.8GitHubCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-190Integer Overflow or Wraparound

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo