CVE-2026-50719
Received Received - Intake

Ingenic T41 SoC Boot ROM Secure Boot Bypass

Vulnerability report for CVE-2026-50719, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-19

Last updated on: 2026-08-19

Assigner: MITRE

Description

The Ingenic T41, and probably also T32, T40, and A1 SoC boot ROMs parse and execute an attacker-controlled init table from the SPL header before checking the secure boot state and before invoking signature verification. The init table parser supports full-address 32-bit write operations, allowing modification of SRAM-resident secure boot state prior to the verification decision. An attacker with physical write access to boot media can inject an init-table entry that disables the secure boot check, causing the ROM to accept unsigned or modified first-stage boot code. This has been hardware-validated on a secureboot-enabled T41 device; ROM analysis confirms closely related behavior on T32, T40, and A1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-19
Last Modified
2026-08-19
Generated
2026-08-19
AI Q&A
2026-08-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
ingenic t41 *
ingenic t32 *
ingenic t40 *
ingenic a1 *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-50719 is a vulnerability in Ingenic T41, T32, T40, and A1 SoC boot ROMs. The boot ROM's init table parser executes before secure boot checks and signature verification. An attacker with physical access to boot media can inject a malicious init table entry that clears SRAM security flags, bypassing secure boot and allowing unsigned code execution.

Detection Guidance

Detection requires physical inspection of boot media for unauthorized modifications to the SPL header or init table. Check for unexpected writes to SRAM security flags or boot state changes. Use tools like flashrom to read and verify the SPI NOR boot media contents against known-good images.

Impact Analysis

This vulnerability allows an attacker with physical access to boot media to execute unsigned code, replace firmware, and achieve persistence across reboots. Since the flaw is in mask ROM, it cannot be patched via firmware updates, requiring hardware changes or physical access restrictions.

Compliance Impact

This vulnerability could lead to unauthorized code execution and firmware tampering, potentially violating data integrity and confidentiality requirements in GDPR and HIPAA. Compliance may be compromised if secure boot is bypassed, allowing unauthorized access to sensitive data.

Mitigation Strategies

Immediately restrict physical access to boot media and SPI NOR flash. Disable or remove write permissions for unauthorized users. If secure boot is enabled, verify its functionality and consider migrating to unaffected hardware since the flaw is in mask ROM and cannot be patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-50719. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart