CVE-2026-32737: Romeo gives the capability to reach high code coverage of Go ≥1.20 apps by helping to measure code coverage fo

Q: How do I fix CVE-2026-32737?

romeo: upgrade to 0.2.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-32737 being exploited?

CVE-2026-32737 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-32737 affect?

CVE-2026-32737 affects romeo. Severity is critical (CVSS 10.0). 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

Q: How urgent is CVE-2026-32737?

Priority 49/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 10.0REMOTEUPGRADE

CVE-2026-32737 is a critical-severity flaw (CVSS 10.0) affecting romeo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	10.0 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-284
Published	2026-03-18
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: ctfer-io

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-18 23:17 UTCPublished CVE record published
2026-06-17 10:36 UTCUpdated Record last modified

ctfer-io romeo UPGRADE

Affected: < 0.2.1

Fixed in: 0.2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy romeo || rpm -q romeo || romeo --version

2. UPGRADE to 0.2.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade romeo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade romeo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-32737?

romeo: upgrade to 0.2.1. Exact commands for each OS are on this page.

Is CVE-2026-32737 being exploited?

CVE-2026-32737 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-32737 affect?

CVE-2026-32737 affects romeo. Severity is critical (CVSS 10.0). 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

How urgent is CVE-2026-32737?

Priority 49/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2026-32805 HIGH 7.5 UPGRADE Romeo gives the capability to reach high code coverage of Go ≥1.20 apps by helping to measure code coverage fo

References

← Back to latest CVEs