# CVE-2026-32769: Fullchain's Invalid NetworkPolicy enables a malicious actor to pivot into another namespace

> A misconfigured NetworkPolicy in Fullchain allows attackers to pivot laterally across namespaces, bypassing intended isolation boundaries.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:P/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-hxm7-9q36-c77f, GO-2026-4715

## What is CVE-2026-32769?

CVE-2026-32769 is a high-severity vulnerability in ctfer-io fullchain, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Fullchain is an umbrella project for deploying a ready-to-use CTF platform. In versions prior to  0.1.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from a subverted application to any Pod out of the origin namespace. The flawed inter-ns NetworkPolicy breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. This issue has been fixed in version 0.1.1. To workaround, delete the failing network policy that should be prefixed by inter-ns- in the target namespace.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-32769?

3 open source packages ship an affected version, including github.com/ctfer-io/fullchain. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ctfer-io/fullchain` | Go | All versions | 0.1.1 |
| `github.com/ctfer-io/fullchain` | Go | All versions | 0.1.1 |
| `github.com/ctfer-io/fullchain` | Go | All versions | 0.1.1 |

Products: Ctfer Fullchain.

## How do I fix CVE-2026-32769?

Upgrade github.com/ctfer-io/fullchain to 0.1.1 or later.

## Is CVE-2026-32769 being exploited?

There is no known exploitation of CVE-2026-32769 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32769 and fix it if it is affected.

What it is: CVE-2026-32769 is a high-severity vulnerability in ctfer-io fullchain, 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-32769 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ctfer-io/fullchain (Go): affected all versions; fixed in 0.1.1
- github.com/ctfer-io/fullchain (Go): affected all versions; fixed in 0.1.1
- github.com/ctfer-io/fullchain (Go): affected all versions; fixed in 0.1.1

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-32769/ (Markdown: https://insights.sbomify.com/CVE-2026-32769/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32769
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32769
- OSV: https://osv.dev/vulnerability/CVE-2026-32769

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32769/
Summaries are generated and may contain mistakes; the official description above is the record.