Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.6amended

Cybersecurity AI (CAI) vulnerable to Command Injection in run_ssh_command_with_credentials Agent tool

CVE-2025-67511GHSA-4c65-9gqf-4w8h

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI cai-framework

    Affected
    <= 0.5.9
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
  • CVE-2025-67511: 2.02% estimated exploitation activity in the next 30 days; percentile 80.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A command injection vulnerability is present in the function tool runsshcommandwithcredentials() available to AI agents. Details This is the source code of the function tool runsshcommandwithcredentials() (code): Note how only password and command inputs are escaped to prevent shell injection; while username, host and port values are left injectable. PoC Create an index.html file with the following content: Serve the file using a web server, as example: Launch cai framework: <br <img width="1913" height="929" alt="poc1" src="https://github.com/user-attachments/assets/faf33665-a014-4081-a847-cc15741d0333" / <br <img width="1913" height="929" alt="poc2" src="https://github.com/user-attachments/assets/e0d3f762-4293-4373-8903-d4f4daedbd45" / <br <br As result we successfully created the file /tmp/username, but not /tmp/password (since shell injection prevention is applied). <img width="898" height="139" alt="poc3"…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-4c65-9gqf-4w8h

  2. Revision 2 · amended ·

    Amended from osv record GHSA-4c65-9gqf-4w8h

  3. Revision 1 · created ·

    Published from ghsa record GHSA-4c65-9gqf-4w8h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-67511

Advisory: Cybersecurity AI (CAI) vulnerable to Command Injection in run_ssh_command_with_credentials Agent tool
IDs: CVE-2025-67511, GHSA-4c65-9gqf-4w8h
Record: https://patchnext.com/advisories/cve-2025-67511 (revision 3, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI cai-framework: affected <= 0.5.9

## Suggested inspection (read-only)
- `python -m pip show cai-framework`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cai-framework.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4c65-9gqf-4w8h (GitHub-reviewed advisory GHSA-4c65-9gqf-4w8h lists affected ranges: PyPI cai-framework >=0 <=0.5.9)
- Verified: https://osv.dev/vulnerability/GHSA-4c65-9gqf-4w8h (OSV record GHSA-4c65-9gqf-4w8h lists affected ranges: PyPI cai-framework >=0 <=0.5.9)

Commands are suggestions: review each one before running it.

Loading voting…