CVE-2026-32805: 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-32805?

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

Q: Is CVE-2026-32805 being exploited?

CVE-2026-32805 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-32805 affect?

CVE-2026-32805 affects romeo. Severity is 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 functional and integration tests within GitHub Actions. Prior to version 0.2.2, the `sanitizeArchivePath` function in `webserver

Q: How urgent is CVE-2026-32805?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2026-32805 is a high-severity flaw (CVSS 7.5) 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.2, the `sanitizeArchivePath` function in `webserver/api/v1/decoder.go` (lines 80-88) is vulnerable to a path traversal bypass due to a missing trailing path separator in the `strings.HasPrefix` check. A crafted tar archive can write files outside the intended d

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Weakness	CWE-22
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.2

Fixed in: 0.2.2

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.2 (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-32805?

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

Is CVE-2026-32805 being exploited?

CVE-2026-32805 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-32805 affect?

CVE-2026-32805 affects romeo. Severity is 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 functional and integration tests within GitHub Actions. Prior to version 0.2.2, the `sanitizeArchivePath` function in `webserver

How urgent is CVE-2026-32805?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2026-32737 CRITICAL 10.0 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