CVE-2026-32771: The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e

Q: How do I fix CVE-2026-32771?

monitoring: upgrade to 0.2.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-32771 being exploited?

CVE-2026-32771 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-32771 affect?

CVE-2026-32771 affects monitoring. Severity is critical (CVSS 9.8). 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 (li

Q: How urgent is CVE-2026-32771?

Priority 57/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2026-32771 is a critical-severity flaw (CVSS 9.8) affecting monitoring. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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, kubec

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 48%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-03-20
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: ctfer

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-20 01:15 UTCPublished CVE record published
2026-06-17 10:36 UTCUpdated Record last modified

ctfer monitoring UPGRADE

Affected: < 0.2.2

Fixed in: 0.2.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy monitoring || rpm -q monitoring || monitoring --version

2. UPGRADE to 0.2.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade monitoring

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade monitoring

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

Go · github.com/ctfer-io/monitoring · FIXED · 0.2.2 · vulnerable: < 0.2.2 · source

go get github.com/ctfer-io/monitoring@v0.2.2 go list -m github.com/ctfer-io/monitoring

Fedora ELN · intel-ipsec-mb · FIXED · 3.0.1-1.eln159 · FEDORA-2026-ca01077210 · source

sudo dnf upgrade --advisory=FEDORA-2026-ca01077210

Fedora 46 · complytime-providers · FIXED · 0.3.0-2.fc46 · FEDORA-2026-7c372be466 · source

sudo dnf upgrade --advisory=FEDORA-2026-7c372be466

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Write-up: github.com/ctfer-io/monitoring/security/advisories/GHSA-f7cq-gvh6-qr25

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-32771?

monitoring: upgrade to 0.2.2. Exact commands for each OS are on this page.

Is CVE-2026-32771 being exploited?

CVE-2026-32771 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-32771 affect?

CVE-2026-32771 affects monitoring. Severity is critical (CVSS 9.8). 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 (li

How urgent is CVE-2026-32771?

Priority 57/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs