CVE-2026-32771: Ctfer Monitoring path traversal (CVSS 9.8)

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Ctfer Monitoring< 0.2.2

Remediation

Fixed in

Ctfer Monitoring≥ 0.2.2

Patch & vendor advisories

References

https://github.com/ctfer-io/monitoring/commit/269dba165aa42210352628c0db6756f3b8fd3c8aPatch
https://github.com/ctfer-io/monitoring/security/advisories/GHSA-f7cq-gvh6-qr25ExploitVendor Advisory
https://security.snyk.io/research/zip-slip-vulnerability#expandable-socPI9fFAJ-titleExploitThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-32771 being actively exploited?

CVE-2026-32771 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.71%.

How severe is CVE-2026-32771?

CVE-2026-32771 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.71% probability of exploitation.

Which products are affected by CVE-2026-32771?

Affected products include Ctfer Monitoring.

How do I fix CVE-2026-32771?

Upgrade affected software to a fixed version, for example Ctfer Monitoring 0.2.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-32771 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo