# CVE-2026-44099: Local Privilege Escalation via pppd password injection

> A local attacker can inject commands into pppd configuration to execute arbitrary code as root, leading to full system compromise on Phoenix Contact devices.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-6wx6-cj8g-h6jg

## What is CVE-2026-44099?

CVE-2026-44099 is a high-severity command injection vulnerability in Phoenix Contact CHARX SEC-3000, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A privilege escalation vulnerability in the system configuration allows a low-privileged local user to execute arbitrary commands as root, resulting in full system compromise.

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

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


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

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

## Is CVE-2026-44099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44099 is a high-severity command injection vulnerability in Phoenix Contact CHARX SEC-3000, published on 30 Jul 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-44099 in the wild and no public exploit code.

Affected product: Phoenix Contact CHARX SEC-3000. 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-44099/ (Markdown: https://insights.sbomify.com/CVE-2026-44099/index.md)
```

## Sources

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

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