ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-32737

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.

Published Mar 18, 2026 · catalog updated Jun 17, 2026 · Romeo gives the capability

Check if you run it

No confirmed exploitation is on record for CVE-2026-32737. EPSS is 0.53%. Act only if a listed version of Romeo gives the capability is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Romeo gives the capability).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.53%
Remediation
Advisory link
Affected products
cpe ctfer-io/romeo

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 NetworkPolicy patches the vulnerability in version 0.2.1. If updates are not possible in production environments, manually delete and update as soon as possible. Given one's context, delete the failing network policy that should be prefixed by in the target namespace.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe ctfer-io/romeoversion unspecified

How to fix CVE-2026-32737

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-32737. EPSS is 0.53%. Act only if a listed version of Romeo gives the capability is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-284: Improper Access Control. EPSS 0.53%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 18, 2026 · NIST NVD

    Detected

    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, lea

  2. Jun 17, 2026 · NIST NVD

    Updated

    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, lea

Sources

  • CVE.orgVulnerability recordCVE-2026-32737

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-32737

    30-day exploitation probability 0.5%

    first.org
  • NIST NVDVulnerability recordCVE-2026-32737

    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" name

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.