How severe is CVE-2026-32737?

CVE-2026-32737 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-32737 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (32nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-32737?

CVE-2026-32737 affects Ctfer-io Romeo. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-32737?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-32737 have an EU (EUVD) identifier?

Yes. CVE-2026-32737 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-12999.

When was CVE-2026-32737 published?

CVE-2026-32737 was published on 2026-03-18 and last updated on 2026-06-17.

CVE-2026-32737

CVE-2026-32737 is a critical-severity vulnerability in Ctfer-io Romeo with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-284.

Key facts

Severity: Critical (CVSS 3.x base score 10.0)
CVSS v4: 7.9
EPSS exploit prediction: 0% (32nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-12999
Weakness: CWE-284
Affected product: Ctfer-io Romeo
Published: 2026-03-18
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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. 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.
How severe is CVE-2026-32737?: CVE-2026-32737 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-32737 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (32nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-32737?: CVE-2026-32737 affects Ctfer-io Romeo. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-32737?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-32737 have an EU (EUVD) identifier?: Yes. CVE-2026-32737 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-12999.
When was CVE-2026-32737 published?: CVE-2026-32737 was published on 2026-03-18 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:ctfer-io:romeo:*:*:*:*:*:*:*:*

More vulnerabilities in Ctfer-io Romeo

CVE-2026-32805 — High (CVSS 7.5): Romeo gives the capability to reach high code coverage of Go ≥1.20 apps by helping to measure code coverage for…

All CVEs affecting Ctfer-io Romeo →

Other CWE-284 (Improper Access Control) vulnerabilities

CVE-2026-76607 — Critical (CVSS 10.0): Joomla Extension - fabrikar.com - Missing ACL check in download element in Fabrik < 4.7.3 - ???.
CVE-2026-20315 — Critical (CVSS 10.0): As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Secure Workload engineering…
CVE-2026-70921 — Critical (CVSS 10.0): Vulnerability in the Oracle Hyperion Financial Management product of Oracle Hyperion (component: Security). The…
CVE-2026-66803 — Critical (CVSS 10.0): Improper access control in Azure Cosmos DB allows an unauthorized attacker to execute code over a network.
CVE-2026-58630 — Critical (CVSS 10.0): Improper access control in Azure App Service allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-60358 — Critical (CVSS 10.0): Vulnerability in the Oracle Access Manager product of Oracle Fusion Middleware (component: Authentication Engine).…

Browse all CWE-284 (Improper Access Control) vulnerabilities →