# CVE-2026-119740: Nexbox A95X Amlogic S905X UART Unauthenticated Console Access


- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-7prp-vrqq-87rq

## What is CVE-2026-119740?

CVE-2026-119740 is a high-severity vulnerability in Nexbox A95X, published on 2 Nov 2026. 

### Official description

Nexbox A95X TV boxes built on the Amlogic S905X platform contain an unauthenticated console exposed via an internal UART header on the PCB that allows physical attackers to obtain an interactive shell as uid 2000 (system) without any credentials. Attackers with physical access and a USB-to-TTL adapter can leverage this shell to reach the pppoe_wrapper vendor daemon, which contains an OS command injection vulnerability executed as root, resulting in full root-level compromise of the device.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-119740 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119740 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119740 is a high-severity vulnerability in Nexbox A95X, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119740 exists.

Affected product: Nexbox A95X. 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-119740/ (Markdown: https://insights.sbomify.com/CVE-2026-119740/index.md)
```

## Sources

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

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