Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1

Dagu has an incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAG

CVE-2026-33344GHSA-ph8x-4jfv-v9v8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/dagu-org/dagu 1.30.4-0.20260319093346-7d07fda8f9de), 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

  • Go github.com/dagu-org/dagu

    Affected
    >= 1.30.4-0.20260221021317-e2ed589105d7, < 1.30.4-0.20260319093346-7d07fda8f9de
    Fixed in
    1.30.4-0.20260319093346-7d07fda8f9de

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-ph8x-4jfv-v9v8 lists affected ranges: Go github.com/dagu-org/dagu >=1.30.4-0.20260221021317-e2ed589105d7 <1.30.4-0.20260319093346-7d07fda8f9de

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

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

As published by the source; long descriptions are shortened.

The fix for CVE-2026-27598 (commit e2ed589, PR #1691) added ValidateDAGName to CreateNewDAG and rewrote generateFilePath to use filepath.Base. This patched the CREATE path. The remaining API endpoints - GET, DELETE, RENAME, EXECUTE - all pass the {fileName} URL path parameter to locateDAG without calling ValidateDAGName. %2F-encoded forward slashes in the {fileName} segment traverse outside the DAGs directory. Vulnerable code internal/persis/filedag/store.go, lines 508-513: findDAGFile resolves the path with filepath.Abs and checks only that the file exists with a YAML extension. No containment check against baseDir. Chi v5 routes using r.URL.RawPath when set. The pattern /dags/{fileName}/spec captures ..%2F..%2Fetc%2Ftarget.yaml as a single path segment. The oapi-codegen runtime calls url.PathUnescape, producing ../../etc/target.yaml. This decoded string reaches locateDAG with the / separator intact. Go's net/http.ServeMux would normally redirect paths containing .., but dagu binds…

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

    Published from ghsa record GHSA-ph8x-4jfv-v9v8

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-33344

Advisory: Dagu has an incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAG
IDs: CVE-2026-33344, GHSA-ph8x-4jfv-v9v8
Record: https://patchnext.com/advisories/cve-2026-33344 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
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 1.30.4-0.20260319093346-7d07fda8f9de. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dagu-org/dagu: affected >= 1.30.4-0.20260221021317-e2ed589105d7, < 1.30.4-0.20260319093346-7d07fda8f9de; fixed in 1.30.4-0.20260319093346-7d07fda8f9de

## Suggested inspection (read-only)
- Go github.com/dagu-org/dagu: 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.
- 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-ph8x-4jfv-v9v8 (GitHub-reviewed advisory GHSA-ph8x-4jfv-v9v8 lists affected ranges: Go github.com/dagu-org/dagu >=1.30.4-0.20260221021317-e2ed589105d7 <1.30.4-0.20260319093346-7d07fda8f9de)

Commands are suggestions: review each one before running it.

Loading voting…