ZeroDay Findings
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-32720

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

Published Mar 16, 2026 · catalog updated Jun 17, 2026 · The CTFer.io Monitoring component

Check if you run it

No confirmed exploitation is on record for CVE-2026-32720. EPSS is 0.42%. Act only if a listed version of The CTFer.io Monitoring component is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The CTFer.io Monitoring component).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.42%
Remediation
Advisory link
Affected products
See sources for product scope

The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). Prior to 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. This vulnerability is fixed in 0.2.1.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-32720

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-32720. EPSS is 0.42%. Act only if a listed version of The CTFer.io Monitoring component is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-284: Improper Access Control. EPSS 0.42%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 16, 2026 · NIST NVD

    Detected

    The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). Prior to 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.

  2. Jun 17, 2026 · NIST NVD

    Updated

    The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). Prior to 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.

Sources

  • CVE.orgVulnerability recordCVE-2026-32720

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-32720

    30-day exploitation probability 0.4%

    first.org
  • NIST NVDVulnerability recordCVE-2026-32720

    The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). Prior to 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace. This brea

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.