Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

Dagu MCP DAG specification read bypasses path containment and workspace isolation

CVE-2026-102943GHSA-5m6c-38r8-5w76

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/dagu-org/dagu/v2 2.11.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-102943: 0.41% estimated exploitation activity in the next 30 days; percentile 35.96 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The traversal fix for CVE-2026-33344 was implemented as HTTP middleware installed only in the chi handler chain, but the MCP service calls the same API method in process, so arbitrary YAML file read is reachable again through the MCP tool surface with a viewer-role key. Read-only, limited to .yaml/.yml targets. Confirmed at HEAD f6c039f (post v2.10.7).

The defect The fix for CVE-2026-33344 is a reflection-based HTTP middleware (internal/frontend/.../api.go, roughly lines 553-597) that inspects a request field named FileName and rejects anything that is not a plain name. It is installed in exactly one place: the chi strict-handler chain (api.go around line 419). The MCP service does not go through that chain. internal/service/mcp/server.go calls the API method directly as an in-process Go call: ```go func (svc *Service) getDAGSpec(ctx context.Context, name string) (map[string]any, error) { // line 307 resp, err := svc.api.GetDAGSpec(ctx, daguapi.GetDAGSpecRequestObject{…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-5m6c-38r8-5w76

  2. Revision 1 · created ·

    Published from ghsa record GHSA-5m6c-38r8-5w76

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102943

Advisory: Dagu MCP DAG specification read bypasses path containment and workspace isolation
IDs: CVE-2026-102943, GHSA-5m6c-38r8-5w76
Record: https://patchnext.com/advisories/cve-2026-102943 (revision 2, source checked 11 Nov 2026, 07:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/dagu-org/dagu/v2 2.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dagu-org/dagu/v2: affected < 2.11.0; fixed in 2.11.0

## Suggested inspection (read-only)
- Go github.com/dagu-org/dagu/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/dagu-org/dagu/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5m6c-38r8-5w76 (GitHub-reviewed advisory GHSA-5m6c-38r8-5w76 lists affected ranges: Go github.com/dagu-org/dagu/v2 >=0 <=2.10.7)
- Verified: https://osv.dev/vulnerability/GHSA-5m6c-38r8-5w76 (OSV record GHSA-5m6c-38r8-5w76 lists affected ranges: Go github.com/dagu-org/dagu/v2 >=0 <2.11.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…