How severe is GHSA-rm43-82j9-r4mj?

No CVSS score has been assigned to GHSA-rm43-82j9-r4mj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rm43-82j9-r4mj?

GHSA-rm43-82j9-r4mj affects the following packages: atomic-agents-stack (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-rm43-82j9-r4mj?

Update atomic-agents-stack to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rm43-82j9-r4mj is resolved across your whole dependency graph.

How do I detect GHSA-rm43-82j9-r4mj in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for atomic-agents-stack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rm43-82j9-r4mj if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-rm43-82j9-r4mj actively exploited in the wild?

No public exploit code has been indexed for GHSA-rm43-82j9-r4mj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rm43-82j9-r4mj?

GHSA-rm43-82j9-r4mj has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rm43-82j9-r4mj?

GHSA-rm43-82j9-r4mj is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rm43-82j9-r4mj published, and has it been updated?

GHSA-rm43-82j9-r4mj was published on August 13, 2026 and was last updated on September 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-rm43-82j9-r4mj — atomic-agents-stack

Fix: dep0we/atomic-agents-stack@ec474f4

GHSA-rm43-82j9-r4mj is a Path Traversal vulnerability in atomic-agents-stack. A fix is available for atomic-agents-stack — see the affected versions and patch details below.

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

Also known asCVE-2026-91989

Published

Aug 13, 2026

Updated

Sep 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rm43-82j9-r4mj.

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍atomic-agents-stack

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The optional dashboard HTTP server (atomic_agents/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.safe_resolve_under. Literal ../ segments survive urlparse and Path joining, so a request can read files outside the intended agents_root (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.do_GET / _serve_file), all versions through 1.0.0.

Fix: route every served path through _io.safe_resolve_under against the intended root and return 404 on PathTraversalError; reject ../separators early; optionally refuse a non-loopback --host unless an explicit auth/allow flag is set (matching serve/_app.py).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`atomic-agents-stack`	all versions	1.1.0`pip install --upgrade 'atomic-agents-stack==1.1.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for atomic-agents-stack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update atomic-agents-stack to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rm43-82j9-r4mj is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

The optional dashboard HTTP server (`atomic_agents/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.safe_resolve_under`. Literal `../` segments survive `urlparse` and `Path` joining, so a request can read files outside the intended `agents_root` (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

O3 Security · Impact-Aware SCA

Is GHSA-rm43-82j9-r4mj in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works