cve.bz

CVE-2026-53763 trustedfirmware op-tee: Year 2038 problem, Y2K38, Y2038, Epochalypse

3.8 lowEPSS 0.2%Fix available

Low (3.8) in trustedfirmware op-tee. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone technology. Starting in version 3.0.0 and prior to version 4.11.0, 32-bit integer overflows in OP-TEE core's AES-GCM implementation cause the authentication tag to be computed with incorrect bit-length values after processing more than 512 megabytes of payload or Additional Authenticated Data (AAD). Version 4.11.0 contains a patch. No known workarounds are available.

Severity

CVSS 3.0

3.8 low
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-53763 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53763?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53763?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53763 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-53763

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-53763](https://cve.bz/cve/badge/CVE-2026-53763.svg)](https://cve.bz/cve/CVE-2026-53763)

HTML:

<a href="https://cve.bz/cve/CVE-2026-53763"><img src="https://cve.bz/cve/badge/CVE-2026-53763.svg" alt="CVE-2026-53763"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
trustedfirmware:op-teefrom 3.0.0 through 4.10.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13optee-osno fix listedDEBIAN-CVE-2026-53763
Ubuntu25.10, 26.04:LTS, 26.10optee-osno fix listedUBUNTU-CVE-2026-53763

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON