High severity · published Mar 18, 2026
CVE-2026-32805
Romeo is vulnerable to Archive Slip due to missing checks in sanitization
7.5
CVSS
0.5%
EPSS
No
On KEV
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.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 destination directory. Version 0.2.2 fixes the issue.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 39% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
RO
romeo · ctfer-io
< 0.2.2 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-32805
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-32805
Patch
https://github.com/ctfer-io/romeo/commit/c2ebcfb9f305fd5f6ef68858de82507dbac10263
Exploit
https://github.com/ctfer-io/romeo/security/advisories/GHSA-p799-g7vv-f279
More from romeo
10.0
CVE-2026-32737
Romeo's invalid NetworkPolicy enables a malicious actor to pivot into another namespace
