atomic-agents-stack: Dashboard HTTP server path traversal allows arbitrary file read

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

The optional dashboard HTTP server (atomicagents/dashboard/serve.py) builds filesystem paths directly from the request path and serves them without a containment check. It is the only per-request untrusted-path site in the codebase that does not route through io.saferesolveunder. Literal ../ segments survive urlparse and Path joining, so a request can read files outside the intended agentsroot (including via the static branch). Impact: arbitrary file read. The default bind is loopback, but --host is an operator-settable documented flag; binding 0.0.0.0 exposes this to the LAN. Even on loopback it is reachable via DNS-rebinding from a browser or SSRF from a co-located service. Affected: dashboard/serve.py (DashboardHandler.doGET / servefile), all versions through 1.0.0. Fix: route every served path through io.saferesolveunder against the intended root and return 404 on PathTraversalError; reject ../separators early; optionally refuse a non-loopback --host unless an explicit auth/allow…

Published by the source

13 Aug 2026, 14:17 UTC

Last modified by the source

13 Aug 2026, 14:17 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rm43-82j9-r4mj

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

# Patch Next advisory brief: GHSA-rm43-82j9-r4mj

Advisory: atomic-agents-stack: Dashboard HTTP server path traversal allows arbitrary file read
IDs: GHSA-rm43-82j9-r4mj
Record: https://patchnext.com/advisories/ghsa-rm43-82j9-r4mj (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: atomic-agents-stack 1.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI atomic-agents-stack: affected <= 1.0.0; fixed in 1.1.0

## Suggested inspection (read-only)
- `python -m pip show atomic-agents-stack`: prints the installed version. Run with the environment that serves production active.

## 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 atomic-agents-stack.
- 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-rm43-82j9-r4mj (GitHub-reviewed advisory GHSA-rm43-82j9-r4mj lists affected ranges: PyPI atomic-agents-stack >=0 <=1.0.0)

Commands are suggestions: review each one before running it.