# CVE-2026-32805: Romeo is vulnerable to Archive Slip due to missing checks in sanitization

> Attackers can exploit a path traversal flaw in Romeo to write files outside the intended directory via crafted tar archives, potentially leading to code execution.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-p799-g7vv-f279, GO-2026-4719

## What is CVE-2026-32805?

CVE-2026-32805 is a high-severity path traversal vulnerability in ctfer-io romeo, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-32805?

3 open source packages ship an affected version, including github.com/ctfer-io/romeo/webserver. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ctfer-io/romeo/webserver` | Go | All versions | 0.2.2 |
| `github.com/ctfer-io/romeo/webserver` | Go | All versions | 0.2.2 |
| `github.com/ctfer-io/romeo/webserver` | Go | All versions | 0.2.2 |

Products: Ctfer-Io Romeo.

## How do I fix CVE-2026-32805?

Upgrade github.com/ctfer-io/romeo/webserver to 0.2.2 or later.

## Is CVE-2026-32805 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32805 exists.

## Other vulnerabilities in ctfer-io romeo

- [CVE-2026-32737](https://insights.sbomify.com/CVE-2026-32737/): Romeo's invalid NetworkPolicy enables a malicious actor to pivot into another namespace (high 7.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32805 and fix it if it is affected.

What it is: CVE-2026-32805 is a high-severity path traversal vulnerability in ctfer-io romeo, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32805 exists.

Affected packages and fixed versions:
- github.com/ctfer-io/romeo/webserver (Go): affected all versions; fixed in 0.2.2
- github.com/ctfer-io/romeo/webserver (Go): affected all versions; fixed in 0.2.2
- github.com/ctfer-io/romeo/webserver (Go): affected all versions; fixed in 0.2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32805/ (Markdown: https://insights.sbomify.com/CVE-2026-32805/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32805
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32805
- OSV: https://osv.dev/vulnerability/CVE-2026-32805

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32805/
Summaries are generated and may contain mistakes; the official description above is the record.