Vulnerability · Published Mar 20, 2026 · Assigned by GitHub_M

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

High 8.8

In plain English

A high-severity path traversal in monitoring from ctfer-io. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.7% (higher than 53% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)8.8High
Exploit odds (30 days)0.7%top 47.4% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/ctfer-io/monitoring0.2.2GHSA-f7cq-gvh6-qr25
Gogithub.com/ctfer-io/monitoring0.2.2GO-2026-4712

Affected products (as reported)

VendorProductVersions
ctfer-io monitoring < 0.2.2

Weakness: CWE-22 · Vector: 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

References