# CVE-2026-32768: Chall-Manager's invalid NetworkPolicy enables a malicious actor to pivot into another namespace > A misconfigured NetworkPolicy in Chall-Manager allows attackers to pivot across namespaces, enabling lateral movement and unauthorized access to other pods. - **Severity:** High 7.9 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Mar 2026 - **Updated:** 20 Mar 2026 - **Also known as:** GHSA-mw24-f3xh-j3qv, GO-2026-4718 ## What is CVE-2026-32768? CVE-2026-32768 is a high-severity vulnerability in ctfer-io chall-manager, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2026-32768? 6 open source packages ship an affected version, including github.com/ctfer-io/chall-manager/deploy and github.com/ctfer-io/chall-manager/sdk. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/ctfer-io/chall-manager/deploy` | Go | All versions | 0.6.5 | | `github.com/ctfer-io/chall-manager/deploy` | Go | All versions | 0.6.5 | | `github.com/ctfer-io/chall-manager/deploy` | Go | All versions | 0.6.5 | | `github.com/ctfer-io/chall-manager/sdk` | Go | All versions | 0.6.5 | | `github.com/ctfer-io/chall-manager/sdk` | Go | All versions | 0.6.5 | | `github.com/ctfer-io/chall-manager/sdk` | Go | All versions | 0.6.5 | Products: Ctfer-Io Chall-Manager. ## How do I fix CVE-2026-32768? Upgrade github.com/ctfer-io/chall-manager/deploy to 0.6.5 or later. ## Is CVE-2026-32768 being exploited? There is no known exploitation of CVE-2026-32768 in the wild and no public exploit code. ## Other vulnerabilities in ctfer-io chall-manager - [CVE-2025-53632](https://insights.sbomify.com/CVE-2025-53632/): Chall-Manager's scenario decoding process does not check for zip slips (high 8.8) - [CVE-2025-53633](https://insights.sbomify.com/CVE-2025-53633/): Chall-Manager's scenario decoding process does not check for zip bombs (high 8.7) - [CVE-2025-53634](https://insights.sbomify.com/CVE-2025-53634/): Chall-Manager's HTTP Gateway have no header check timeout leading to potential slow loris attacks (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32768 and fix it if it is affected. What it is: CVE-2026-32768 is a high-severity vulnerability in ctfer-io chall-manager, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-32768 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/ctfer-io/chall-manager/deploy (Go): affected all versions; fixed in 0.6.5 - github.com/ctfer-io/chall-manager/deploy (Go): affected all versions; fixed in 0.6.5 - github.com/ctfer-io/chall-manager/deploy (Go): affected all versions; fixed in 0.6.5 - github.com/ctfer-io/chall-manager/sdk (Go): affected all versions; fixed in 0.6.5 - github.com/ctfer-io/chall-manager/sdk (Go): affected all versions; fixed in 0.6.5 - github.com/ctfer-io/chall-manager/sdk (Go): affected all versions; fixed in 0.6.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-32768/ (Markdown: https://insights.sbomify.com/CVE-2026-32768/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32768 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32768 - OSV: https://osv.dev/vulnerability/CVE-2026-32768 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32768/ Summaries are generated and may contain mistakes; the official description above is the record.