Skip to content

← Public intelligence

PyPI package

apm

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.4PyPIAmendedPublished

    Microsoft APM: Symlinks under .apm/prompts/ and .apm/agents/ are dereferenced during apm install, copying host-local file contents into the project tree

    CVE-2026-45539 · GHSA-q5pp-gvjg-h7v4

    Affected
    • PyPI apm >= 0.5.4, <= 0.12.4
    Fixed in
    0.13.0· Vendor fix available
    Issue
    Two primitive integrators in apm-cli enumerate package files with bare Path.glob() / Path.rglob() calls and read each match with Path.readtext(), transparently following symbolic links. A symlink committed inside a remote APM dependency under .apm/prompts/<x.prompt.md or .apm/agents/<x.agent.md is preserved verbatim into apmmodules/ on clone and then dereferenced during integration, with the resolved content written as a regular file into the project's deploy directories. The package contenthash, the pre-deploy SecurityGate scan, and apm audit do not flag this. The deploy roots are not added to the auto-generated .gitignore, so the resulting files are staged by git add by default. This was reproduced via the standard owner/repo#tag install flow against a real bare git repository. No --force or special flags were used. Affected code Sinks - src/apmcli/integration/promptintegrator.py PromptIntegrator.findpromptfiles: packagepath.glob(".prompt.md") and…

    Recommended action: Upgrade to 0.13.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →