CVE-2026-32768 — deploy
Fix: ctfer-io/chall-manager@dc5ef27CVE-2026-32768 is a CWE-284 vulnerability in github.com/ctfer-io/chall-manager/deploy. A fix is available for github.com/ctfer-io/chall-manager/deploy — see the affected versions and patch details below.
Chall-Manager's invalid NetworkPolicy enables a malicious actor to pivot into another namespace
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32768.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/ctfer-io/chall-manager/deploy🐹github.com/ctfer-io/chall-manager/sdkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/ctfer-io/chall-manager/deploy | all versions | 0.6.5go get github.com/ctfer-io/chall-manager/deploy@v0.6.5 |
| 🐹Go | github.com/ctfer-io/chall-manager/sdk | all versions | 0.6.5go get github.com/ctfer-io/chall-manager/sdk@v0.6.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ctfer-io/chall-manager/deploy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ctfer-io/chall-manager/deploy to 0.6.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32768 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-32768 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-32768. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-32768 in your dependencies?
O3 Security finds CVE-2026-32768 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.