# CVE-2026-119737: Amlogic pppoe_wrapper Command Injection via AF_UNIX Socket


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/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:** 2 Nov 2026
- **Also known as:** GHSA-cqfv-369w-xpwm

## What is CVE-2026-119737?

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

### Official description

The pppoe_wrapper vendor daemon from the Amlogic Android SDK, as shipped on Nexbox A95X (Amlogic S905/S905X) TV boxes, contains a command injection vulnerability that allows local attackers to execute arbitrary commands as root by sending crafted messages to a world-writable AF_UNIX datagram socket at /dev/socket/pppoe_wrapper. Attackers can send a message beginning with 'pppd pty' followed by shell metacharacters and arbitrary commands, which are passed unfiltered to system(3) and executed by /system/bin/sh -c as root, resulting in full privilege escalation.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-119737 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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