Skip to main content
VulnerabilityPublished Updated

CVE-2025-2172: Aviatrix Controller · OS Command Injection

Affects Aviatrix ControllerSource CVE Database V5

0

Public exploit available · 12% EPSS · CVSS 6.6 Medium · fixed in 8.0.0 : patch Aviatrix Controller as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
12.2% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.0.0, 7.2.5090, 7.1.4208
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade aviatrix/controller to 8.0.0, 7.2.5090 or 7.1.4208.

Affected software

ProductAffectedFixed in
GitHubaviatrix/controllerpkg:github/aviatrix/controllerOther threatsAffected
  • <7.1.4208
  • <7.2.5090
  • <8.0.0
Fixed in
  • 7.1.4208
  • 7.2.5090
  • 8.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade Aviatrix Controller to versions 7.1.4208, 7.2.5090, 8.0.0, or later, where the vulnerability is fixed.
  2. Implement strict input validation and sanitization on all user-supplied data before passing it to command line utilities, ensuring special characters are neutralized or escaped properly.
  3. Restrict access to the Aviatrix Controller interface and underlying systems to only trusted administrators with necessary privileges, minimizing the attack surface.
  4. Employ application-layer firewalls or intrusion detection systems to monitor and block suspicious command execution patterns or anomalous inputs.
  5. Conduct regular security audits and code reviews focusing on command execution paths within the controller to identify and remediate similar injection risks.
  6. Use role-based access controls and multi-factor authentication to reduce the likelihood of privilege escalation to the high privileges required for exploitation.
  7. Monitor logs for unusual command execution or errors related to input processing that could indicate attempted exploitation.
  8. Isolate the Aviatrix Controller in a secure network segment to limit potential lateral movement if compromised.

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

References

Community reviews

Loading reviews…