dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-5619

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-06
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 flaw has been found in Braffolk mcp-summarization-functions up to 0.1.5. This impacts an unknown function of the file src/server/mcp-server.ts of the component summarize_command. Executing a manipulation of the argument command can lead to os command injection. The attack requires local access. The exploit has been published and may be used. 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 Braffolk mcp-summarization-functions (up to 0.1.5) within the summarize_command component in src/server/mcp-server.ts. An attacker with local access can manipulate the command argument to execute arbitrary OS commands.

MitigationUpdate to a version beyond 0.1.5 once available, and implement strict input validation or use parameterized/safe APIs instead of shell execution for the summarize_command component.

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. Check if Braffolk mcp-summarization-functions is installed
    Run 'npm list mcp-summarization-functions' or check package.json dependencies
    Affected if The package appears in installed dependencies or package.json
  2. Verify the installed version
    Run 'npm list mcp-summarization-functions' to get the version number
    Affected if Version is 0.1.5 or lower
  3. Locate the vulnerable component
    Search for src/server/mcp-server.ts in the project directory
    Affected if The file exists and contains the summarize_command component
  4. Confirm summarize_command is exposed
    Inspect the MCP server configuration and exposed methods in mcp-server.ts for the 'command' parameter handling
    Affected if The 'command' argument is accepted and passed to shell execution functions such as exec() or spawn() without sanitization
  5. Determine if untrusted input can reach the command parameter
    Review how the summarize_command is invoked and whether external/local untrusted input is passed to the 'command' argument
    Affected if The 'command' parameter accepts user-supplied or network-provided input without validation

You are affected if Braffolk mcp-summarization-functions version 0.1.5 or lower is installed and the summarize_command component with its 'command' parameter is exposed to untrusted input.

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

Update to a version beyond 0.1.5 once available, and implement strict input validation or use parameterized/safe APIs instead of shell execution for the summarize_command component.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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