CVE-2026-32805
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
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ctfer-io | romeo | to 0.2.2 (exc) |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
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.