Skip to main content
VulnerabilityPublished

CVE-2026-32768: ctfer-io chall-manager · Improper Access Control

Affects ctfer-io chall-managerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.9 High : upgrade to 0.6.5 soon.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 4.0 base score
7.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.6.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade chall-manager and ctfer-io/chall-manager to 0.6.5.

Affected software

ProductAffectedFixed in
ctfer-iochall-managerAffected
  • <0.6.5
Fixed in
  • 0.6.5
GitHubctfer-io/chall-managerpkg:github/ctfer-io/chall-managerOther threatsAffected
  • <0.6.5
Fixed in
  • 0.6.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade chall-manager to version 0.6.5 or later, where the NetworkPolicy misconfiguration is corrected. In addition, review and harden Kubernetes NetworkPolicies to ensure strict namespace isolation and restrict Pod-to-Pod communication according to the principle of least privilege. Implement network segmentation and monitoring to detect unusual lateral movement within clusters. Employ Kubernetes Role-Based Access Control (RBAC) to limit permissions and reduce the blast radius of compromised Pods. Regularly audit cluster configurations and use security tools to validate NetworkPolicy enforcement. For deployments using sdk/kubernetes.Kompose, verify that instance isolation is properly configured or consider alternative deployment methods that enforce stronger isolation. Finally, maintain up-to-date vulnerability management and incident response plans to quickly address any exploitation attempts.

Description

Chall-Manager is a platform-agnostic system able to start Challenges on Demand of a player. In versions prior to 0.6.5, due to a miswritten NetworkPolicy, a malicious actor can pivot from an instance to any Pod out of the origin namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. In the specific case of sdk/kubernetes.Kompose it does not isolate the instances. This issue has been fixed in version 0.6.5.

References

Community reviews

Loading reviews…