Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-91989 – Unauthenticated Arbitrary File Read (Path Traversal) – atomic-agents-stack before 1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-91989 is a high-severity path traversal vulnerability (CVSS 8.7) in the optional dashboard HTTP server of the atomic-agents-stack PyPI package. The flaw allows unauthenticated, remote attackers to read arbitrary files on the host filesystem by sending crafted ../ sequences to the dashboard’s DashboardHandler.do_GET endpoint. All versions of atomic-agents-stack prior to 1.1.0 are affected.

Technical details

  • Root cause: atomic_agents/dashboard/serve.py builds filesystem paths directly from the incoming HTTP request path and serves the resulting file without validating that it stays inside the intended agents_root directory. Unlike other file-access paths in the codebase, this handler does not route through the library’s _io.safe_resolve_under containment check.
  • Trigger conditions: The optional dashboard server must be enabled (it hosts static HTML assets and renders dynamic agent interaction logs). Literal ../ segments survive urlparse and Path joining, so a request path containing traversal sequences escapes the intended root, including through the static-file serving branch.
  • Attack vector: Network — the dashboard binds to loopback by default, but the --host flag is an operator-settable option; binding to 0.0.0.0 exposes the server to the LAN. Even a loopback-bound instance can potentially be reached via DNS-rebinding attacks from a browser or SSRF from a co-located service.
  • Impact: Unauthenticated disclosure of arbitrary files readable by the process running the dashboard (e.g., configuration files, credentials, source code, logs), with no impact to integrity or availability.

Affected software

  • atomic-agents-stack (PyPI package, vendor: dep0we) — all versions before 1.1.0
  • Fixed in version 1.1.0 and later

Severity

  • CVSS v4.0: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade atomic-agents-stack to version 1.1.0 or later, which routes all dashboard file access through the _io.safe_resolve_under containment check and returns a 404 on path traversal attempts.
  • If immediate patching is not possible:
    • Disable the optional dashboard HTTP server if it is not required.
    • Ensure the dashboard is not bound to 0.0.0.0 or any externally reachable interface; keep it restricted to loopback and avoid exposing it via reverse proxies.
    • Restrict network access to the dashboard port using firewall rules or network segmentation, and monitor for anomalous requests containing ../ traversal sequences.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge