Remote code execution via unchecked SEI metadata write
Published Jun 16, 2026 · Updated Jun 16, 2026
Out-of-bounds write in Google Android's Exynos MFC kernel component allows remote attackers to execute code without user interaction. The __mfc_core_nal_q_get_dec_metadata_sei_nal function in mfc_core_nal_q.c processes decoder metadata SEI NAL data without a required bounds check and writes beyond its destination buffer. The published assessment requires low privileges but no user interaction, and successful memory corruption grants code execution on the affected device.
Summary
What happened
Out-of-bounds write in Google Android's Exynos MFC kernel component allows remote attackers to execute code without user interaction. The __mfc_core_nal_q_get_dec_metadata_sei_nal function in mfc_core_nal_q.c processes decoder metadata SEI NAL data without a required bounds check and writes beyond its destination buffer. The published assessment requires low privileges but no user interaction, and successful memory corruption grants code execution on the affected device.
The record
- CVE
- CVE-2026-0147
- Published
- Jun 16, 2026
- Updated
- Jun 16, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-120, CWE-787
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 16, 2026CVE publishedPublication date reported by the CVE source.
- Jun 16, 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.
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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