dbcve.org
MonitoringApplication · Ctfer

CVE-2026-32771

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 0.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The CTFer.io Monitoring component prior to 0.2.2 contains a path traversal vulnerability in the sanitizeArchivePath function in pkg/extract/extract.go. The missing trailing path separator in the strings.HasPrefix check allows attackers to craft archive paths that escape the intended extraction directory, enabling arbitrary file writes to sensitive locations like shell configs, SSH keys, kubeconfig, and crontabs, leading to RCE and persistent backdoors.

MitigationUpgrade to version 0.2.2 or implement proper path sanitization by adding a trailing slash to the strings.HasPrefix check to prevent directory traversal.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MonitoringApplication
Affected:< 0.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate ctfer monitoring binary
    Search for the ctfer binary in common paths: which ctfer, ls /usr/local/bin/ctfer, ls /opt/ctfer/bin/ctfer, or check your system's service manager for ctfer processes
    Affected if The ctfer binary is not found - the component is not installed
  2. Determine installed version
    Run 'ctfer version' or 'ctfer --version' to get the exact version number
    Affected if Version is present but less than 0.2.2 - the vulnerable version is installed
  3. Verify package or container version
    If installed via package manager: apt list --installed 2>/dev/null | grep ctfer, yum list installed ctfer, or check docker images for ctfer version tags
    Affected if Package or container version is listed as anything before 0.2.2
  4. Check if extraction feature is in use
    Review ctfer configuration files (usually in /etc/ctfer/, /opt/ctfer/config/, or ~/.ctfer/) for archive extraction or upload functionality enabled
    Affected if Archive extraction/upload module is enabled in config - the vulnerable code path can be triggered

User is affected if ctfer monitoring is installed with version less than 0.2.2 AND the archive extraction feature is in use or accessible

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.2.2 or later
Fixed in 0.2.2
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.2.2 or implement proper path sanitization by adding a trailing slash to the strings.HasPrefix check to prevent directory traversal.

Recommended fix High confidence

0.2.2

  1. Upgrade the CTFer.io Monitoring component from any version below 0.2.2 to version 0.2.2 or later
  2. Verify the upgrade was successful by checking the installed version
  3. Confirm the sanitizeArchivePath function in pkg/extract/extract.go now includes a trailing path separator in the strings.HasPrefix check (or review commit 269dba165aa42210352628c0db6756f3b8fd3c8a for the fix details)
  4. Test the archive extraction functionality to ensure legitimate use cases still work after the fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Monitoring Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32771 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32771 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data