{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45702 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-45702 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45702 is a medium-severity memory corruption vulnerability in OP-TEE optee_os, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45702 and fix it if it is affected.\n\nWhat it is: CVE-2026-45702 is a medium-severity memory corruption vulnerability in OP-TEE optee_os, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-45702 in the wild and no public exploit code.\n\nAffected product: OP-TEE optee_os. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45702/ (Markdown: https://insights.sbomify.com/CVE-2026-45702/index.md)","id":"CVE-2026-45702","markdown":"https://insights.sbomify.com/CVE-2026-45702/index.md","name":"CVE-2026-45702","record":{"aliases":["DEBIAN-CVE-2026-45702","GHSA-86pj-8xgw-66p5","UBUNTU-CVE-2026-45702"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"OP-TEE OS","requires_auth":"high_privilege","summary":"A type confusion in OP-TEE OS causes a kernel panic when processing specific memory share requests, requiring a version upgrade to fix.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"op-tee","vendor":"trustedfirmware"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"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 4.3.0 and prior to version 4.11.0, a type confusion vulnerability exists in OP-TEE OS when processing an FFA_MEM_SHARE request from the normal world. This only applies when OP-TEE is configured as an SPMC for S-EL0 SPs, that is, with `CFG_CORE_SEL1_SPMC=y` and `CFG_SECURE_PARTITION=y`. Version 4.11.0 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OP-TEE has FF-A type confusion in SPMC tmem path that causes S-EL1 kernel panic","id":"CVE-2026-45702","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Pimcore: WordExport Authorization Bypass for Unauthorized Document Export","id":"CVE-2026-45703"},"packages":[],"prev":{"headline":"Sulu: Weak Cryptographical usage for API Key generation and Reset Tokens","id":"CVE-2026-45701"},"products":["optee_os"],"published":"2026-06-03","related":[{"cvss_score":9.8,"headline":"Memory corruption in OP-TEE","id":"CVE-2019-1010292","kev_date_added":null,"published":"2019-07-16"},{"cvss_score":9.8,"headline":"Memory corruption in OP-TEE","id":"CVE-2019-1010293","kev_date_added":null,"published":"2019-07-15"},{"cvss_score":9.8,"headline":"Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Buffer Overflow.","id":"CVE-2019-1010295","kev_date_added":null,"published":"2019-07-15"},{"cvss_score":9.8,"headline":"Memory corruption in OP-TEE","id":"CVE-2019-1010296","kev_date_added":null,"published":"2019-07-15"},{"cvss_score":9.8,"headline":"Memory corruption in OP-TEE","id":"CVE-2019-1010297","kev_date_added":null,"published":"2019-07-15"},{"cvss_score":9.8,"headline":"Memory corruption in OP-TEE","id":"CVE-2019-1010298","kev_date_added":null,"published":"2019-07-15"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2019-25052","kev_date_added":null,"published":"2021-08-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-04","vendors":["OP-TEE"]},"summary":"A type confusion in OP-TEE OS causes a kernel panic when processing specific memory share requests, requiring a version upgrade to fix.","url":"https://insights.sbomify.com/CVE-2026-45702/"}