# CVE-2026-32737: Romeo's invalid NetworkPolicy enables a malicious actor to pivot into another namespace

> A misconfigured NetworkPolicy in Romeo allows attackers to pivot from a hardened namespace to other pods, enabling lateral movement.

- **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:** 18 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-fgm3-q9r5-43v9, GO-2026-4714

## What is CVE-2026-32737?

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

### Official description

Romeo gives the capability to reach high code coverage of Go ≥1.20 apps by helping to measure code coverage for functional and integration tests within GitHub Actions. Prior to version 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from the "hardened" namespace to any Pod out of it. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. Removing the `inter-ns` NetworkPolicy patches the vulnerability in version 0.2.1. If updates are not possible in production environments, manually delete `inter-ns` and update as soon as possible. Given one's context, 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-32737?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ctfer-io/romeo/environment/deploy` | Go | All versions | None |
| `github.com/ctfer-io/romeo/environment/deploy` | Go | All versions | 0.2.1 |
| `github.com/ctfer-io/romeo/environment/deploy` | Go | All versions | 0.2.1 |

Products: Ctfer-Io Romeo.

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

Upgrade github.com/ctfer-io/romeo/environment/deploy to 0.2.1 or later.

## Is CVE-2026-32737 being exploited?

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

## Other vulnerabilities in ctfer-io romeo

- [CVE-2026-32805](https://insights.sbomify.com/CVE-2026-32805/): Romeo is vulnerable to Archive Slip due to missing checks in sanitization (high 8.3)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- github.com/ctfer-io/romeo/environment/deploy (Go): affected all versions; no fix listed
- github.com/ctfer-io/romeo/environment/deploy (Go): affected all versions; fixed in 0.2.1
- github.com/ctfer-io/romeo/environment/deploy (Go): affected all versions; fixed in 0.2.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-32737/ (Markdown: https://insights.sbomify.com/CVE-2026-32737/index.md)
```

## Sources

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

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