ctfer-io monitoring up to 0.2.1 pkg/extract/extract.go sanitizeArchivePath path traversal

Summaryinfo

A vulnerability, which was classified as critical, has been found in ctfer-io monitoring up to 0.2.1. Affected by this vulnerability is the function sanitizeArchivePath of the file pkg/extract/extract.go. This manipulation causes path traversal. This vulnerability is registered as CVE-2026-32771. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in ctfer-io monitoring up to 0.2.1. It has been declared as critical. Affected by this vulnerability is the function sanitizeArchivePath of the file pkg/extract/extract.go. The manipulation with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-32771 since 03/13/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

Upgrading to version 0.2.2 eliminates this vulnerability. Applying the patch 269dba165aa42210352628c0db6756f3b8fd3c8a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• ctfer-io

Name

• monitoring

Version

• 0.2.0
• 0.2.1

License

• open-source

Website

• Product: https://github.com/ctfer-io/monitoring/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion