Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p799-g7vv-f279 | Romeo is vulnerable to Archive Slip due to missing checks in sanitization |
Tue, 24 Mar 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:ctfer-io:romeo:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
Thu, 19 Mar 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 19 Mar 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ctfer-io
Ctfer-io romeo |
|
| Vendors & Products |
Ctfer-io
Ctfer-io romeo |
Wed, 18 Mar 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Romeo is vulnerable to Archive Slip due to missing checks in sanitization | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-19T13:46:59.937Z
Reserved: 2026-03-16T17:35:36.695Z
Link: CVE-2026-32805
Updated: 2026-03-19T13:46:38.632Z
Status : Analyzed
Published: 2026-03-18T23:17:30.213
Modified: 2026-03-24T21:26:26.890
Link: CVE-2026-32805
No data.
OpenCVE Enrichment
Updated: 2026-03-25T11:51:51Z
Github GHSA