# CVE-2025-2172: Command injection in Controller

> Attackers can execute arbitrary commands on Aviatrix Controller by injecting special characters into filenames due to insufficient input sanitization.

- **Severity:** Medium 6.6 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-wr65-2r27-crgw

## What is CVE-2025-2172?

CVE-2025-2172 is a medium-severity command injection vulnerability in Aviatrix Controller, published on 23 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Aviatrix Controller versions prior to 7.1.4208, 7.2.5090, and 8.0.0 fail to sanitize user input prior to passing the input to command line utilities, allowing command injection via special characters in filenames

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

## Which versions are affected by CVE-2025-2172?


## How do I fix CVE-2025-2172?

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

## Is CVE-2025-2172 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2172 and fix it if it is affected.

What it is: CVE-2025-2172 is a medium-severity command injection vulnerability in Aviatrix Controller, published on 23 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2172 exists.

Affected product: Aviatrix Controller. 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-2025-2172/ (Markdown: https://insights.sbomify.com/CVE-2025-2172/index.md)
```

## Sources

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

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