dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-3964

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A weakness has been identified in OpenAkita up to 1.24.3. This impacts the function run of the file src/openakita/tools/shell.py of the component Chat API Endpoint. Executing a manipulation of the argument Message can lead to os command injection. The attack is restricted to local execution. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OS command injection vulnerability in OpenAkita's Chat API Endpoint. The run function in src/openakita/tools/shell.py fails to properly sanitize the Message argument, allowing injection of OS commands. The vulnerability is restricted to local execution only.

MitigationImplement strict input validation and sanitization for the Message argument in the run function. Consider using parameterized approaches or allowlists instead of passing user input directly to shell commands.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable shell.py file
    Search for the file src/openakita/tools/shell.py in your OpenAkita installation directory. Use: find / -path '*/openakita/tools/shell.py' 2>/dev/null or locate the file via your package manager if installed via package.
    Affected if The file exists in your installation, indicating the vulnerable code is present.
  2. Verify OpenAkita Chat API is installed
    Check if OpenAkita Chat API component is installed. Use package manager queries (pip list, apt list, etc.) or check for OpenAkita directories. Look for any Chat API service or component.
    Affected if OpenAkita Chat API is installed and the Chat API Endpoint feature is enabled.
  3. Inspect the run function for unsanitized input handling
    Examine the contents of src/openakita/tools/shell.py. Look at the run function and verify if the Message argument is passed directly to shell execution functions (e.g., os.system, subprocess with shell=True) without sanitization.
    Affected if The run function passes the Message argument directly to shell commands without input validation or sanitization.
  4. Check if shell execution feature is enabled
    Review your OpenAkita configuration files (e.g., config.yaml, settings.py, environment variables) to determine if shell tool execution is enabled for the Chat API. Look for flags like 'enable_shell', 'allow_command_execution', or similar.
    Affected if Shell command execution is enabled for the Chat API Endpoint.
  5. Review API access controls
    Examine access controls and authentication settings for the Chat API Endpoint. Check if the endpoint accepting Message arguments is exposed to untrusted users or external access.
    Affected if The Chat API Endpoint accepting Message arguments is accessible without strict access controls.

You are affected if OpenAkita Chat API is installed with the shell.py tool present, the run function contains unsanitized Message argument handling, and the shell execution feature is enabled for an accessible API endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for the Message argument in the run function. Consider using parameterized approaches or allowlists instead of passing user input directly to shell commands.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3964 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data