CVE-2026-32805
Received Received - Intake
Path Traversal in Romeo's sanitizeArchivePath Allows Arbitrary File Write

Publication date: 2026-03-18

Last updated on: 2026-03-24

Assigner: GitHub, Inc.

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-18
Last Modified
2026-03-24
Generated
2026-06-16
AI Q&A
2026-03-19
EPSS Evaluated
2026-06-14
NVD
CVE-2026-32805
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ctfer-io romeo to 0.2.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the Romeo tool, which helps measure code coverage for Go applications within GitHub Actions. Specifically, before version 0.2.2, the function sanitizeArchivePath in the file webserver/api/v1/decoder.go had a flaw. The function used a strings.HasPrefix check that missed a trailing path separator, allowing a crafted tar archive to bypass path traversal protections.

As a result, an attacker could create a tar archive that writes files outside the intended destination directory, potentially overwriting or adding files in unauthorized locations.

This issue was fixed in version 0.2.2 of Romeo.

Impact Analysis

This vulnerability can allow an attacker to write files outside the intended directory when processing a crafted tar archive. This could lead to unauthorized file creation or modification on the system where Romeo is used.

Such unauthorized file writes can compromise system integrity, potentially leading to code execution, data corruption, or disruption of normal operations.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

To mitigate this vulnerability, upgrade Romeo to version 0.2.2 or later, as this version fixes the path traversal bypass issue in the sanitizeArchivePath function.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-32805. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart