# Monitoring is vulnerable to Archive Slip due to missing checks in sanitization

Advisory record · `GHSA-f7cq-gvh6-qr25`

- **Identifiers:** `GHSA-f7cq-gvh6-qr25` · `CVE-2026-32771` · `GO-2026-4712`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 16 Mar 2026
- **Updated:** 5 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Mar 2026, 20:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/ctfer-io/monitoring` (Go): affected `<0.2.2`; fixed in `0.2.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Monitoring (Go module github.com/ctfer-io/monitoring) versions before 0.2.2 are affected. A crafted tar archive can write files outside the intended extraction directory because a path prefix check lacks a trailing separator, which allows a directory-name collision. An attacker who can place a tar archive on the shared volume used by the Cold Extract workflow could then write arbitrary files on the machine running the extractor. Upgrade to version 0.2.2.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:L/SA:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0072, the 54th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:08 UTC: First seen by agentprime
- 31 Oct 2026, 15:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f7cq-gvh6-qr25)

## Sources

- [GitHub Advisory Database: GHSA-f7cq-gvh6-qr25](https://github.com/advisories/GHSA-f7cq-gvh6-qr25)
- [OSV: GHSA-f7cq-gvh6-qr25](https://osv.dev/vulnerability/GHSA-f7cq-gvh6-qr25)
- <https://github.com/ctfer-io/monitoring/security/advisories/GHSA-f7cq-gvh6-qr25>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-32771>
- <https://github.com/ctfer-io/monitoring/commit/269dba165aa42210352628c0db6756f3b8fd3c8a>
- <https://github.com/ctfer-io/monitoring>
- <https://security.snyk.io/research/zip-slip-vulnerability#expandable-socPI9fFAJ-title>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f7cq-gvh6-qr25>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f7cq-gvh6-qr25/>. Everything for agents: <https://agentprime.io/llms.txt>.
