Vulnerability · Published Mar 18, 2026 · Assigned by GitHub_M

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

High 7.9

In plain English

A high-severity improper access control in romeo from ctfer-io. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 35% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)7.9High
Exploit odds (30 days)0.4%top 64.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/ctfer-io/romeo/environment/deploy0.2.1GHSA-fgm3-q9r5-43v9
Gogithub.com/ctfer-io/romeo/environment/deployno fix listedGO-2026-4714

Affected products (as reported)

VendorProductVersions
ctfer-io romeo < 0.2.1

Weakness: CWE-284 · Vector: 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

References