GHSA-xhcr-cqfr-m3hv: atomic-agents-stack Remote Code Execution Vulnerability

HIGH
CWE-319 CWE-494
Published
Advisory Summary

GHSA-xhcr-cqfr-m3hv is a HIGH remote code execution vulnerability (CWE-319: Cleartext Transmission of Sensitive Information) affecting atomic-agents-stack libraries in the PyPI ecosystem. The issue involves http mcp catalog accepts cleartext http and spawns catalog-supplied commands (mitm to rce). Remediation is available by upgrading affected packages to version 1.1.0.

GHSA-xhcr-cqfr-m3hv at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-xhcr-cqfr-m3hv
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-319: Cleartext Transmission of Sensitive Information
Affected Product atomic-agents-stack
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-xhcr-cqfr-m3hv

To remediate this vulnerability, upgrade all affected atomic-agents-stack dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

atomic-agents-stack fixed: 1.1.0
pip install atomic-agents-stack>=1.1.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show atomic-agents-stack

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-xhcr-cqfr-m3hv, inspect your installed packages using pip:

pip show atomic-agents-stack

Analyze the terminal output to locate any version of atomic-agents-stack in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.1.0), your application is affected.

Note: The pip show atomic-agents-stack command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-319: Cleartext Transmission of Sensitive Information, where the product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. In atomic-agents-stack, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

The HTTP MCP server-registry backend factory (`atomic_agents/mcp_registry/http.py`, `make_http_mcp_server_registry_backend_from_url`) accepts both `http` and `https` schemes. Catalog entries carry `command`/`args` that are type-validated but content-unrestricted, and are later spawned as local stdio subprocesses by `MCPClientPool`. Over a cleartext `http://` catalog URL, a network man-in-the-middle can rewrite the catalog response to inject an arbitrary `command`/`args` and obtain code execution on the agent host, with no LLM involvement. The Policy MCP allowlist is not a default mitigation (`mcp_allow_fn` defaults to None), so absent an operator-authored allowlist every resolved spec connects. **Affected:** `mcp_registry/http.py`, all versions through 1.0.0. (The `https` path is sound: `httpx` defaults to `verify=True`, `follow_redirects=False`.) **Fix:** require `https` by default and gate `http://` behind a loud explicit opt-in. Defense-in-depth: allowlist the resolved command basename (or require confirmation) before any registry-sourced subprocess spawn. Document the consequence in spec/36.

GHSA-xhcr-cqfr-m3hv Affected atomic-agents-stack Versions

1 component(s)
Fixed Versions:
1.1.0
Product / Package Ecosystem Affected Versions Fixed Version
atomic-agents-stack
PyPI
< 1.1.0
1.1.0

References

Frequently Asked Questions

What is GHSA-xhcr-cqfr-m3hv?
GHSA-xhcr-cqfr-m3hv is a security vulnerability in atomic-agents-stack involving HTTP MCP catalog accepts cleartext http and spawns catalog-supplied commands (MITM to RCE) under CWE-319: Cleartext Transmission of Sensitive Information.
Which atomic-agents-stack versions are affected?
Affected versions include releases prior to 1.1.0 across affected packages: atomic-agents-stack.
What version fixes GHSA-xhcr-cqfr-m3hv?
Upgrading to 1.1.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is atomic-agents-stack affected?
Yes, atomic-agents-stack is affected in releases prior to 1.1.0. Upgrade your dependency to 1.1.0 or later.
What CWE is associated with GHSA-xhcr-cqfr-m3hv?
GHSA-xhcr-cqfr-m3hv is classified under CWE-319: Cleartext Transmission of Sensitive Information (The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.).
How can I check PyPI dependencies for GHSA-xhcr-cqfr-m3hv?
Run the dependency tree command: 'pip show atomic-agents-stack'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xhcr-cqfr-m3hv",
  "modified" : "2026-08-17T21:49:55Z",
  "published" : "2026-08-17T21:49:55Z",
  "aliases" : [ ],
  "summary" : "atomic-agents-stack: HTTP MCP catalog accepts cleartext http and spawns catalog-supplied commands (MITM to RCE)",
  "details" : "The HTTP MCP server-registry backend factory (`atomic_agents/mcp_registry/http.py`, `make_http_mcp_server_registry_backend_from_url`) accepts both `http` and `https` schemes. Catalog entries carry `command`/`args` that are type-validated but content-unrestricted, and are later spawned as local stdio subprocesses by `MCPClientPool`. Over a cleartext `http://` catalog URL, a network man-in-the-middle can rewrite the catalog response to inject an arbitrary `command`/`args` and obtain code execution on the agent host, with no LLM involvement. The Policy MCP allowlist is not a default mitigation (`mcp_allow_fn` defaults to None), so absent an operator-authored allowlist every resolved spec connects.\n\n**Affected:** `mcp_registry/http.py`, all versions through 1.0.0. (The `https` path is sound: `httpx` defaults to `verify=True`, `follow_redirects=False`.)\n\n**Fix:** require `https` by default and gate `http://` behind a loud explicit opt-in. Defense-in-depth: allowlist the resolved command basename (or require confirmation) before any registry-sourced subprocess spawn. Document the consequence in spec/36.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "atomic-agents-stack"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.1.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/dep0we/atomic-agents-stack/security/advisories/GHSA-xhcr-cqfr-m3hv"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/dep0we/atomic-agents-stack"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dep0we/atomic-agents-stack/releases#release-v1.1.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-319", "CWE-494" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-17T21:49:55Z",
    "nvd_published_at" : null
  }
}