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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
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 | 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 include Ctfer Monitoring.
How do I fix CVE-2026-32771?
Upgrade github.com/ctfer-io/monitoring to 0.2.2 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-32771 being exploited?
There is no known exploitation of CVE-2026-32771 in the wild and no public exploit code.
Sources
Also known as GHSA-f7cq-gvh6-qr25, GO-2026-4712.