GHSA-q5pp-gvjg-h7v4: Microsoft APM: Symlinks under `.apm/prompts/` and `.apm/agents/` are dereferenced during `apm install`, copying host-local file contents into the project tree
SummaryTwo primitive integrators in `apm-cli` enumerate package files with bare `Path.glob()` / `Path.rglob()` calls and read each match with `Path.read_text()`, 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 `apm_modules/` on clone and then dereferenced during integration, with the resolved content written as a regular file into the project's deploy directories.The package `content_hash`, 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 codeSinks`src/apm_cli/integration/prompt_integrator.py`  
`PromptIntegrator.find_prompt_files`: `package_path.glob("*.prompt.md")` and `apm_prompts.glob("*.prompt.md")`  
No symlink filter.`src/apm_cli/integration/prompt_integrator.py`  
`PromptIntegrator.copy_prompt`: `source.read_text("utf-8")``src/apm_cli/integration/agent_integrator.py`  
`AgentIntegrator.find_agent_files`: `package_path.glob("*.agent.md")`, `apm_agents.rglob("*.agent.md")`, `apm_agents.rglob("*.md")`, `apm_chatmodes.glob("*.chatmode.md")`  
No symlink filter.`src/apm_cli/integration/agent_integrator.py`  
`AgentIntegrator.copy_agent`: `source.read_text("utf-8")``src/apm_cli/integration/agent_integrator.py`  
`_write_codex_agent`: `source.read_text("utf-8")`; resolved bytes are embedded into `developer_instructions` of the generated `.codex/agents/<name>.toml``src/apm_cli/integration/agent_integrator.py`  
`_write_windsurf_agent_skill`: same dereference pattern; resolved bytes land in `.windsurf/skills/<name>/SKILL.md`Safe pattern already present in the codebase`src/apm_cli/integration/base_integrator.py`  
`BaseIntegrator.find_files_by_glob()` rejects:symlinks via `f.is_symlink()`hardlinks via `f.stat().st_nlink > 1`resolved paths escaping the package rootThis helper is already used by `InstructionIntegrator.find_instruction_files`.Documented contract that the affected integrators violateIn `src/apm_cli/install/phases/local_content.py`, `_copy_local_package` documents the intent of preserving symlinks in `apm_modules/`:This is security-relevant and not intended behavior because the codebase already documents that symlinks preserved in `apm_modules/` are supposed to remain inert unless a consumer follows them safely. The affected integrators are exactly those consumer paths, and they dereference the symlink without sandboxing or symlink checks. That makes this an implementation gap, not expected design.The affected integrators are the consumer tools that follow the link without sandboxing.ReproducerThis proof of concept is localhost-only and uses a sentinel file, not a real secret.It uses a real bare git repository and `git config insteadOf` so the install path is the same one APM uses for real GitHub clones (`Repo.clone_from`). No network access is required.Observed resultDefault install output:The source under `apm_modules/` remains a symlink:The deploy roots receive plain regular files containing the sentinel:`.github/agents/notes.agent.md``.github/prompts/welcome.prompt.md``.claude/agents/notes.md``.cursor/agents/notes.md``.codex/agents/notes.toml``.windsurf/skills/notes/SKILL.md`Example:The deployed files persist after the original symlink target is removed:Defenses that did not flag the resultThe pre-deploy `SecurityGate.scan_files` walks with `followlinks=False` and continues past `is_symlink()` files. The symlinked source is not scanned.`apm audit` against the post-install tree reports no findings.The auto-written `.gitignore` contains only `apm_modules/`. The deploy roots are not excluded, and `git add -A` stages all deployed files alongside `apm.lock.yaml`.The package `content_hash` is computed before symlink resolution and remained stable across installs whose resolved deployed bytes differed.ImpactThe directly demonstrated impact is file-content disclosure.Any file readable by the user running `apm install` can be selected by the package author through an absolute symlink target committed inside the dependency, and its contents are then written into the project's deploy directories as regular files.Realistic downstream consequencesThese were not separately demonstrated with real secrets, but they follow from the validated behavior:The deploy directories (`.github/`, `.claude/`, `.cursor/`, `.codex/`, `.windsurf/`) are project-tracked by convention, and the auto-generated `.gitignore` does not exclude them.In automation that regenerates and commits agent context, the leaked files can be pushed without human review.A symlink target such as `/proc/self/environ` would resolve to the APM process environment at install time.Why this is security-relevant and not intended behaviorThis is not just "a malicious package being malicious."The codebase already contains the correct defense in `BaseIntegrator.find_files_by_glob()`, and that helper explicitly rejects symlinks, hardlinks, and containment escapes. `InstructionIntegrator` uses it. `PromptIntegrator` and `AgentIntegrator` do not.The codebase also documents that preserving symlinks inside `apm_modules/` is acceptable only because the links are supposed to remain inert unless a consumer tool follows them safely. Here, APM itself is the consumer tool that follows them unsafely.That architectural asymmetry makes this look like an implementation oversight, not intended behavior.Recommended fixRoute both affected finders through the existing safe helper.Optional defense in depthIn `copy_prompt`, `copy_agent`, `_write_codex_agent`, and `_write_windsurf_agent_skill`, explicitly raise on `source.is_symlink()` before reading.Treat any symlink under a dependency's `.apm/` tree as a security finding during scanning.Regression test ideaAdd unit tests that create a fixture package with symlinks under `.apm/prompts/`, `.apm/agents/`, and `.apm/chatmodes/`, then assert that the symlink entries are filtered out before any read occurs.Example shape:A second test should mirror the same pattern for `AgentIntegrator.find_agent_files()`.
CVSS v3.1: 7.4