# CVE-2026-32771: Monitoring is vulnerable to Archive Slip due to missing checks in sanitization

> Attackers can exploit path traversal in the monitoring component to write arbitrary files, leading to remote code execution and persistent backdoors.

- **Severity:** High 8.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-f7cq-gvh6-qr25, GO-2026-4712

## What is CVE-2026-32771?

CVE-2026-32771 is a high-severity path traversal vulnerability in ctfer-io monitoring, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). In versions prior to 0.2.2, the sanitizeArchivePath function in pkg/extract/extract.go (lines 248–254) is vulnerable to Path Traversal due to a missing trailing path separator in the strings.HasPrefix check. The extractor allows arbitrary file writes (e.g., overwriting shell configs, SSH keys, kubeconfig, or crontabs), enabling RCE and persistent backdoors. The attack surface is further amplified by the default ReadWriteMany PVC access mode, which lets any pod in the cluster inject a malicious payload. This issue has been fixed in version 0.2.2.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-32771?

3 open source packages ship an affected version, including github.com/ctfer-io/monitoring. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ctfer-io/monitoring` | Go | All versions | 0.2.2 |
| `github.com/ctfer-io/monitoring` | Go | All versions | 0.2.2 |
| `github.com/ctfer-io/monitoring` | Go | All versions | 0.2.2 |

Products: Ctfer Monitoring.

## How do I fix CVE-2026-32771?

Upgrade github.com/ctfer-io/monitoring to 0.2.2 or later.

## Is CVE-2026-32771 being exploited?

There is no known exploitation of CVE-2026-32771 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32771 and fix it if it is affected.

What it is: CVE-2026-32771 is a high-severity path traversal vulnerability in ctfer-io monitoring, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32771 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.2
- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.2
- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32771/ (Markdown: https://insights.sbomify.com/CVE-2026-32771/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32771
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32771
- OSV: https://osv.dev/vulnerability/CVE-2026-32771

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32771/
Summaries are generated and may contain mistakes; the official description above is the record.