dbcve.org
RomeoApplication · Ctfer Io

CVE-2026-32737

CRITICAL · 10.0 CVSS v3.1 Published 2026-03-18
Fix available
A fix is available. Upgrade to 0.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Kubernetes NetworkPolicy misconfiguration vulnerability in the Romeo tool (code coverage measurement for Go apps). Prior to version 0.2.1, a miswritten NetworkPolicy named 'inter-ns' allows lateral movement from the hardened namespace to any Pod outside of it, breaking the security-by-default isolation model.

MitigationUpgrade Romeo to version 0.2.1 or later which removes the vulnerable NetworkPolicy. As an immediate workaround, manually delete any NetworkPolicy prefixed with 'inter-ns-' from the target namespace.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RomeoApplication
Affected:< 0.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Romeo version
    Run 'romeo version' or check the container image tag deployed in your Kubernetes cluster to determine the installed version of Ctfer Io Romeo
    Affected if Version is below 0.2.1
  2. List NetworkPolicies in the Romeo namespace
    Run 'kubectl get networkpolicies -n <romeo-namespace>' to retrieve all NetworkPolicy objects deployed by Romeo
    Affected if Any NetworkPolicy with name starting with 'inter-ns-' exists in the namespace
  3. Inspect the inter-ns NetworkPolicy spec
    Run 'kubectl get networkpolicy <inter-ns-policy-name> -n <romeo-namespace> -o yaml' and examine the ingress rules, specifically looking for rules that allow traffic FROM the hardened namespace TO external pod IPs
    Affected if The policy contains an ingress rule with 'from' specifying the hardened namespace and 'to' allowing CIDR ranges that include pods outside that namespace

You are affected if Romeo version is below 0.2.1 AND a NetworkPolicy prefixed with 'inter-ns-' exists and permits ingress from your hardened namespace to pods outside of it.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.2.1 or later
Fixed in 0.2.1
Vendor patch github.com →
Interim mitigation

Upgrade Romeo to version 0.2.1 or later which removes the vulnerable NetworkPolicy. As an immediate workaround, manually delete any NetworkPolicy prefixed with 'inter-ns-' from the target namespace.

Recommended fix High confidence

Romeo version 0.2.1

  1. Upgrade Romeo to version 0.2.1 or later to receive the patched NetworkPolicy configuration
  2. If immediate upgrade is not feasible in production, manually delete the NetworkPolicy resources prefixed with 'inter-ns-' in the target namespace using: kubectl delete networkpolicy inter-ns-<resource> -n <namespace>
  3. After applying the upgrade or manual deletion, verify the NetworkPolicy has been removed or corrected by checking: kubectl get networkpolicy -n <namespace>
  4. Update to the latest Romeo release as soon as possible once the manual mitigation is in place

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Romeo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32737 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32737 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data