CVE-2026-32768

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-03-20 06:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:36 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 7.9 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-03-20 06:16 UTC

Last modified

2026-06-17 10:36 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-284 · Improper access control

Record status

Analyzed

Affected

• ctfer-io chall-manager < 0.6.5

Attack profile CVSS 4.0 · 7.9

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

None

Confidentiality

None

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-32768.md and follow it. Check whether this project is affected by CVE-2026-32768. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge