Command InjectionWeakness · CWE-77

CVE-2026-7220

HIGH · 7.3 CVSS v3.1 Published 2026-04-28

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

82/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

A vulnerability has been found in jackwrichards FastlyMCP up to 6f3d0b0e654fc51076badc7fa16c03c461f95620. This impacts an unknown function of the file fastly-mcp.mjs of the component fastly_cli Tool. The manipulation of the argument command leads to os command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary

dbcve analysis · moderate confidence

OS command injection vulnerability in FastlyMCP's fastly_cli tool (fastly-mcp.mjs file). The application passes user-controlled input from the 'command' argument directly to shell execution without sanitization, allowing remote attackers to execute arbitrary OS commands.

MitigationUntil an official patch is released, avoid using FastlyMCP or restrict network access to it. The fix requires implementing strict input validation and using parameterized command execution instead of shell invocation.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

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

Am I affected?

dbcve checks

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

Locate fastly-mcp.mjs in your environment

Search for the file named 'fastly-mcp.mjs' in your project directories, node_modules, or installed packages using: find . -name 'fastly-mcp.mjs' or grep -r 'fastly-mcp' in your package directories

Affected if The file exists in your environment, meaning FastlyMCP is installed
Determine the installed version of FastlyMCP

Check package.json or the fastly-mcp package version using: npm list fastly-mcp or cat package.json | grep fastly

Affected if The version you find is earlier than the patched version released for CVE-2026-7220 (compare against the version that includes the fix)
Inspect fastly-mcp.mjs for command execution patterns

Open fastly-mcp.mjs and search for uses of child_process exec, spawn, or shell execution functions that process the 'command' argument

Affected if The code directly passes user input from the 'command' argument to system() or exec() without parameterization or sanitization
Verify if the fastly_cli component handles user input

Review the fastly_cli component code within fastly-mcp.mjs for any code paths where the 'command' parameter flows into shell command execution

Affected if User-supplied 'command' argument values reach shell execution functions without validation or escaping
Test for command injection vulnerability

If you have access to run FastlyMCP, attempt a safe test by providing a benign command argument like '; echo test' and observe if it executes

Affected if The injected string is executed as an OS command, indicating the vulnerability is present

You are affected if FastlyMCP is installed and the 'command' argument is passed to unsanitized system command execution in the fastly_cli component of fastly-mcp.mjs.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Until an official patch is released, avoid using FastlyMCP or restrict network access to it. The fix requires implementing strict input validation and using parameterized command execution instead of shell invocation.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA3.0 h

19.0 hours of engineering $3,380

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-7220?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 1.3%

Remediation

A high-priority fix

Have this fixed 19 hrs · Moderate

Typical engagement from $3,380

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-7220 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References