CVE-2026-30635
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 · uneditedCommand injection vulnerability in automagik-genie 2.5.27 MCP Server allows attackers to execute arbitrary commands via the view_task (aka view) in the readTranscriptFromCommit function in dist/mcp/server.js when a user reads from an external FORGE_BASE_URL.
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 confidenceCommand injection vulnerability in the automagik-genie MCP Server's readTranscriptFromCommit function allows remote attackers to execute arbitrary OS commands via the view_task/view parameter when processing an external FORGE_BASE_URL. User-supplied input is apparently passed unsanitized to a shell execution context.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if automagik-genie MCP Server is installedSearch for the package in your environment using: npm list automagik-genie, pip list | grep -i automagik, or check your project dependencies (package.json, requirements.txt, go.mod)Affected if The package appears in your dependency list
-
Determine the installed versionRun npm list automagik-genie version, pip show automagik-genie, or check your lockfiles (package-lock.json, Pipfile.lock) for the exact version numberAffected if The installed version matches any version known to contain the vulnerable readTranscriptFromCommit function
-
Check if FORGE_BASE_URL environment variable is configuredInspect your runtime environment variables: printenv | grep FORGE_BASE_URL, or check your application configuration files and deployment manifests for this variableAffected if FORGE_BASE_URL is set and points to an external or untrusted endpoint
-
Verify exposure of the readTranscriptFromCommit functionReview your MCP Server configuration and API endpoints to determine if readTranscriptFromCommit is exposed via HTTP/JSON-RPC, check your server logs for calls to this endpointAffected if The function is accessible over the network without authentication or additional access controls
-
Inspect the view_task parameter handlingIf you have access to source code, grep for 'readTranscriptFromCommit' and examine how the view_task or view parameter is processed - look for direct shell command execution patternsAffected if User-supplied view_task/view input is passed directly to exec(), system(), popen(), or similar shell execution functions without sanitization
You are affected if the automagik-genie MCP Server is installed, the readTranscriptFromCommit function is exposed, and FORGE_BASE_URL can be controlled by untrusted users who could inject shell commands via the view_task parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataSanitize and validate all user-supplied input (especially the view_task parameter and FORGE_BASE_URL) before use in any system command execution; prefer parameterized APIs over shell commands; implement allowlist validation for permitted values.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30635 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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