dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-30312

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
DSAI-Cline's command auto-approval module contains a critical OS command injection vulnerability that renders its whitelist security mechanism completely ineffective. The system relies on string-based parsing to validate commands; while it intercepts dangerous operators such as ;, &&, ||, |, and command substitution patterns, it fails to account for raw newline characters embedded within the input. An attacker can construct a payload by embedding a literal newline between a whitelisted command and malicious code (e.g., git log malicious_command), forcing DSAI-Cline to misidentify it as a safe operation and automatically approve it. The underlying PowerShell interpreter treats the newline as a command separator, executing both commands sequentially, resulting in Remote Code Execution without any user interaction.

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 · high confidence

DSAI-Cline's command auto-approval module uses string-based parsing to whitelist commands but fails to filter newline characters. Attackers can bypass the whitelist by embedding a literal newline between a whitelisted command and malicious payload (e.g., 'git log\nmalicious_command'), causing PowerShell to execute both commands sequentially and achieve unauthenticated RCE.

MitigationReplace string-based command validation with proper parser-based validation that normalizes or rejects inputs containing any command separators including newlines, and implement explicit allowlist validation at the token/argument level rather than string matching.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify DSAI-Cline installation and version
    Run 'cline --version' or check the installed package via package manager (npm list dsai-cline, pip show dsai-cline, etc.) depending on how it was installed
    Affected if The installed version falls within any affected version range (compare to any published vulnerable versions)
  2. Locate command auto-approval configuration
    Search for configuration files named 'auto-approve', 'approval-config', or similar in the DSAI-Cline config directory (~/.cline/, ./config/, or project-specific config)
    Affected if The auto-approval module configuration file exists and is enabled (contains 'enabled: true' or similar)
  3. Inspect the command validation logic
    Examine the source code or compiled module responsible for command validation. Look for functions that check for dangerous operators (;, &&, ||, |, command substitution) using string matching methods
    Affected if The validation uses string-based operator filtering (e.g., str.contains, regex searching for operators) rather than proper command parsing
  4. Verify newline handling in validation
    Search the validation code for newline character handling. Look for checks on '\n', '\r', or 'newline' within the command validation function
    Affected if The validation logic contains no explicit check for newline characters as potential command separators
  5. Test whitelist bypass behavior (if possible)
    Create a test command string containing a whitelisted command prefix followed by a literal newline and a malicious payload (e.g., 'git\nwhoami'). Observe whether both parts are executed
    Affected if The system executes the payload after the newline without triggering approval, demonstrating the bypass

You are affected if DSAI-Cline is installed with the command auto-approval module enabled and the validation uses whitelist-based operator filtering without explicit newline character checks.

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

Replace string-based command validation with proper parser-based validation that normalizes or rejects inputs containing any command separators including newlines, and implement explicit allowlist validation at the token/argument level rather than string matching.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30312 — 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-30312 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