Romeo's invalid NetworkPolicy enables a malicious actor to pivot into another namespace

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-32737: 0.40% estimated exploitation activity in the next 30 days; percentile 34.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Patch Removing the inter-ns NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible. Workaround Given your context, delete the failing network policy that should be prefixed by inter-ns- in the target namespace.

Published by the source

16 Mar 2026, 20:45 UTC

Last modified by the source

19 Mar 2026, 21:15 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fgm3-q9r5-43v9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32737

Advisory: Romeo's invalid NetworkPolicy enables a malicious actor to pivot into another namespace
IDs: CVE-2026-32737, GHSA-fgm3-q9r5-43v9
Record: https://patchnext.com/advisories/cve-2026-32737 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ctfer-io/romeo/environment/deploy 0.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ctfer-io/romeo/environment/deploy: affected < 0.2.1; fixed in 0.2.1

## Suggested inspection (read-only)
- Go github.com/ctfer-io/romeo/environment/deploy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ctfer-io/romeo/environment/deploy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fgm3-q9r5-43v9 (GitHub-reviewed advisory GHSA-fgm3-q9r5-43v9 lists affected ranges: Go github.com/ctfer-io/romeo/environment/deploy >=0 <0.2.1)

Commands are suggestions: review each one before running it.