Skip to main content
VulnerabilityPublished Updated

CVE-2026-46383: Windows absolute-path tar member overwrite during legacy-bundle probing in `apm install`

Affects apmSource GCVE Database

0
Compare
Authoritative record:CVE-2026-46383· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.28.0 when convenient.

Data as of 30 Oct 2026, 05:15 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.28.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade apm to 0.28.0.

Affected software

ProductAffectedFixed in
Homebrewapmpkg:brew/apmOther threatsAffected
  • <0.28.0
Fixed in
  • 0.28.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Microsoft APM is an open-source, community-driven dependency manager for AI agents. Prior to 0.13.0, Microsoft APM contains a Windows-specific archive extraction boundary failure in the legacy-bundle probe used by apm install <bundle> on supported Python 3.10 and 3.11 runtimes. When apm install is given a local .tar.gz that is not recognized as a plugin-format bundle, APM probes whether it is a legacy --format apm bundle. On Python versions earlier than 3.12, that probe extracts untrusted tar members with raw tar.extractall() without rejecting Windows absolute member names such as D:/.... This vulnerability is fixed in 0.13.0.

References

Community reviews

Loading reviews…