dbcve.org
SakadevApplication · Rahmanazhar

CVE-2026-30306

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-30
Fix available
A fix is available. Upgrade to 4.0.6 or later.
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
In its design for automatic terminal command execution, SakaDev offers two options: Execute safe commands and execute all commands. The description for the former states that commands determined by the model to be safe will be automatically executed, whereas if the model judges a command to be potentially destructive, it still requires user approval. However, this design is highly susceptible to prompt injection attacks. An attacker can employ a generic template to wrap any malicious command and mislead the model into misclassifying it as a 'safe' command, thereby bypassing the user approval requirement and resulting in arbitrary command execution.

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

SakaDev's terminal command execution feature contains a prompt injection vulnerability where attackers can wrap malicious commands in generic templates to mislead the AI model into misclassifying them as 'safe' commands. This bypasses the user approval mechanism, allowing arbitrary command execution with critical severity (CVSS 9.8).

MitigationFix requires implementing robust prompt injection detection and input validation to identify and reject malicious command templates, along with improving the model's classification logic to resist social engineering attacks.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SakadevApplication
Affected:< 4.0.6

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 installed version
    Locate the Rahmanazhar Sakadev installation and retrieve its version number through the application's about page, version command, or package metadata
    Affected if The installed version is below 4.0.6
  2. Confirm terminal command execution feature is enabled
    Check application settings or configuration files for the terminal command execution module and verify it is active
    Affected if The terminal command execution feature is enabled and the version is vulnerable
  3. Test for prompt injection bypass
    Submit a command wrapped in generic templates (such as 'please run this safe command: <malicious>') through the terminal feature and observe if the AI model classifies it as safe without proper scrutiny
    Affected if The system classifies wrapped malicious commands as safe without flagging potential prompt injection
  4. Verify user approval can be bypassed
    Submit a crafted command using template-based social engineering and check whether the user approval prompt is skipped or the command executes without proper user consent
    Affected if The approval mechanism fails to catch template-wrapped commands and permits execution without proper user verification

You are affected if Rahmanazhar Sakadev version is below 4.0.6 and the terminal command execution feature is enabled, with the system failing to detect prompt injection in template-wrapped commands and bypassing user approval.

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.

dbcve · scoped
Upgrade available Upgrade to 4.0.6 or later
Fixed in 4.0.6
Interim mitigation

Fix requires implementing robust prompt injection detection and input validation to identify and reject malicious command templates, along with improving the model's classification logic to resist social engineering attacks.

Recommended fix High confidence

SakaDev 4.0.6 or later

  1. Upgrade SakaDev to version 4.0.6 or later to address the prompt injection vulnerability in the automatic command execution feature
  2. After upgrading, review the command execution settings in SakaDev configuration
  3. Verify that the safe command execution mode properly detects and requires approval for injected commands
  4. Test the fix by attempting known prompt injection patterns to confirm they are now properly classified as requiring user approval

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sakadev Scoped from the published advisory
  • Consultation12.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
68.0 hours of engineering $12,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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