TaskWeaver has Protection Mechanism Failure and Server-Side Request Forgery (SSRF)

Exploitation

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

CVSS

6.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary This vulnerability allows a user to escape the container network isolation and access the host’s local services (127.0.0.1 bound on the host). The vulnerability is applicable only on the MacOS and Windows environments while using Docker Desktop, Containerd on Lima VM, or Podman. Details TaskWeaver is a code-first agent framework for seamlessly planning and executing data analytics tasks. This innovative framework interprets user requests through code snippets and efficiently coordinates a variety of plugins in the form of functions to execute data analytics tasks in a stateful manner. TaskWeaver agents execute code as part of their tasks in a secure manner inside the code interpreter that implements Docker containers under the hood for security reasons. The current Docker client’s configuration can produce insecure outcomes when running on Windows or MacOS host machines while using Docker Desktop, Containerd on Lima, or Podman. Podman, Containerd, and Docker Desktop, while…

Published by the source

28 Jan 2026, 15:49 UTC

Last modified by the source

3 Feb 2026, 03:06 UTC

Source last checked

26 Oct 2026, 13:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gpx9-96j6-pp87

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gpx9-96j6-pp87

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

# Patch Next advisory brief: GHSA-gpx9-96j6-pp87

Advisory: TaskWeaver has Protection Mechanism Failure and Server-Side Request Forgery (SSRF)
IDs: GHSA-gpx9-96j6-pp87
Record: https://patchnext.com/advisories/ghsa-gpx9-96j6-pp87 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI agentos-taskweaver: affected <= 0.1.0

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on agentos-taskweaver.
- 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://osv.dev/vulnerability/GHSA-gpx9-96j6-pp87 (OSV record GHSA-gpx9-96j6-pp87 lists affected ranges: PyPI agentos-taskweaver >=0 <=0.1.0)
- Verified: https://github.com/advisories/GHSA-gpx9-96j6-pp87 (GitHub-reviewed advisory GHSA-gpx9-96j6-pp87 lists affected ranges: PyPI agentos-taskweaver >=0 <=0.1.0)

Commands are suggestions: review each one before running it.