# CVE-2026-50719: Security feature bypass in n/a

> Attackers with physical access can bypass secure boot on Ingenic SoCs by modifying boot media, allowing execution of unsigned code.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-46j4-pvjg-4r6r

## What is CVE-2026-50719?

CVE-2026-50719 is a medium-severity vulnerability in n/a, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-474 (Use of Function with Inconsistent Implementations), CWE-347 (Improper Verification of Cryptographic Signature), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-50719?


## How do I fix CVE-2026-50719?

No fix has been published for CVE-2026-50719 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-50719 being exploited?

There is no known exploitation of CVE-2026-50719 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50719 and fix it if it is affected.

What it is: CVE-2026-50719 is a medium-severity vulnerability in n/a, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50719 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50719/ (Markdown: https://insights.sbomify.com/CVE-2026-50719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50719
- OSV: https://osv.dev/vulnerability/CVE-2026-50719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50719/
Summaries are generated and may contain mistakes; the official description above is the record.