# CVE-2026-22621: Command injection in PADM

> An authenticated administrator can execute arbitrary commands in Eaton PADM firmware due to improper input validation in session management.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-pwxm-3jqh-j7gq

## What is CVE-2026-22621?

CVE-2026-22621 is a high-severity command injection vulnerability in Eaton PADM, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper input validation in one of the session management interface of Eaton's Tripp Lite Series PADM firmware could allow an authenticated administrator to execute arbitrary commands within a restricted environment.

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

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


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

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

## Is CVE-2026-22621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22621 is a high-severity command injection vulnerability in Eaton PADM, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22621 in the wild and no public exploit code.

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

## Sources

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

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