Romeo is vulnerable to Archive Slip due to missing checks in sanitization

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-32805: 0.45% estimated exploitation activity in the next 30 days; percentile 39.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Vulnerable Code File: webserver/api/v1/decoder.go, lines 80-88 The function is called at line 48 inside [Decompressor].Unzip, which is invoked by Decode (line 80) during execution of the webserver CLI (command download). Root Cause strings.HasPrefix(v, filepath.Clean(d)) does not append a trailing / to the directory prefix, causing a directory name prefix collision. If the destination is /home/user/extract-output and a tar entry is named ../extract-outputevil/pwned, the joined path /home/user/extract-outputevil/pwned passes the prefix check — it starts with /home/user/extract-output — even though it is entirely outside the intended directory. Steps to Reproduce 1. Deploy Romeo. A measured app writes its…

Published by the source

16 Mar 2026, 20:47 UTC

Last modified by the source

19 Mar 2026, 21:15 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p799-g7vv-f279

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32805

Advisory: Romeo is vulnerable to Archive Slip due to missing checks in sanitization
IDs: CVE-2026-32805, GHSA-p799-g7vv-f279
Record: https://patchnext.com/advisories/cve-2026-32805 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ctfer-io/romeo/webserver 0.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ctfer-io/romeo/webserver: affected < 0.2.2; fixed in 0.2.2

## Suggested inspection (read-only)
- Go github.com/ctfer-io/romeo/webserver: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ctfer-io/romeo/webserver.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p799-g7vv-f279 (GitHub-reviewed advisory GHSA-p799-g7vv-f279 lists affected ranges: Go github.com/ctfer-io/romeo/webserver >=0 <0.2.2)

Commands are suggestions: review each one before running it.