CVE-2026-32805: Github.com/ctfer io/romeo/webserver Romeo Is Vulnerable To Archive Vulnerability

HIGH
Advisory Identifier: GHSA-p799-g7vv-f279
CWE-22
Published
Advisory Summary

CVE-2026-32805 is a HIGH romeo is vulnerable to archive vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Github.com/ctfer io/romeo/webserver libraries in the Go ecosystem. The issue involves romeo is vulnerable to archive slip due to missing checks in sanitization. Remediation is available by upgrading affected packages to version 0.2.2.

CVE-2026-32805 at a Glance

CVE Identifier CVE-2026-32805
GHSA Identifier GHSA-p799-g7vv-f279
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Github.com/ctfer io/romeo/webserver
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-32805

To remediate this vulnerability, upgrade all affected Github.com/ctfer io/romeo/webserver dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/ctfer-io/romeo/webserver fixed: 0.2.2
Upgrade github.com/ctfer-io/romeo/webserver to 0.2.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/ctfer-io/romeo/webserver

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-32805, inspect your project dependencies for Github.com/ctfer io/romeo/webserver:

inspect dependencies for github.com/ctfer-io/romeo/webserver

Analyze the terminal output to locate any version of Github.com/ctfer io/romeo/webserver in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.2.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where 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. In Github.com/ctfer io/romeo/webserver, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 ```go func sanitizeArchivePath(d, t string) (v string, err error) { v = filepath.Join(d, t) if strings.HasPrefix(v, filepath.Clean(d)) { return v, nil } return "", &ErrPathTainted{ Path: t, } } ``` 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 coverage data. 2. **Place the PoC zip on the PVC.** Any pod with write access to the `ReadWriteMany` PVC (or the webserver itself) copies a `poc-path-traversal.tar` into the `coverdir` mount path. The archive contains legitimate coverage files alongside two crafted entries with path-traversal names. 3. **Run the webserver CLI against the running webserver:** ``` webserver download \ --server http://localhost:8080 \ --directory /home/user/extract-output ``` 4. **Observe the bypass.** `unzip` processes the zip stream. For the malicious entries: ``` // entry name: ../extract-outputevil/poc-proof.txt filepath.Join("/home/user/extract-output", "../extract-outputevil/poc-proof.txt") => "/home/user/extract-outputevil/poc-proof.txt" strings.HasPrefix("/home/user/extract-outputevil/poc-proof.txt", "/home/user/extract-output") => true // BUG: prefix collision; file lands OUTSIDE target dir ``` Both malicious entries are written outside `/home/user/extract-output/`. The legitimate coverage files land correctly inside it. ## Impact Successful exploitation gives an attacker arbitrary file write on the machine running the webserver CLI. Real-world primitives include: - Overwriting `~/.bashrc` / `~/.zshrc` / `~/.profile` for RCE on next shell login - Appending to `~/.ssh/authorized_keys` for persistent SSH backdoor - Dropping a malicious entry into `~/.kube/config` to hijack cluster access - Writing crontab entries for persistent scheduled execution The attack surface is widened by the default `ReadWriteMany` PVC access mode, which means any pod in the cluster with the PVC mounted can inject the payload — not just the Romeo webserver itself.

CVE-2026-32805 Affected Github.com/ctfer io/romeo/webserver Versions

1 component(s)
Fixed Versions:
0.2.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/ctfer-io/romeo/webserver
Go
< 0.2.2
0.2.2

References

Frequently Asked Questions

What is CVE-2026-32805?
CVE-2026-32805 is a security vulnerability in Github.com/ctfer io/romeo/webserver involving Romeo is vulnerable to Archive Slip due to missing checks in sanitization under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Github.com/ctfer io/romeo/webserver versions are affected?
Affected versions include releases prior to 0.2.2 across affected packages: github.com/ctfer-io/romeo/webserver.
What version fixes CVE-2026-32805?
Upgrading to 0.2.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/ctfer-io/romeo/webserver affected?
Yes, github.com/ctfer-io/romeo/webserver is affected in releases prior to 0.2.2. Upgrade your dependency to 0.2.2 or later.
What CWE is associated with CVE-2026-32805?
CVE-2026-32805 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (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.).
How can I check Go dependencies for CVE-2026-32805?
Run the dependency tree command: 'inspect dependencies for github.com/ctfer-io/romeo/webserver'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p799-g7vv-f279",
  "modified" : "2026-03-19T21:15:42Z",
  "published" : "2026-03-16T20:47:02Z",
  "aliases" : [ "CVE-2026-32805" ],
  "summary" : " Romeo is vulnerable to Archive Slip due to missing checks in sanitization",
  "details" : "## Summary\n\nThe `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.\n\n## Vulnerable Code\n\nFile: `webserver/api/v1/decoder.go`, lines 80-88\n\n```go\nfunc sanitizeArchivePath(d, t string) (v string, err error) {\n\tv = filepath.Join(d, t)\n\tif strings.HasPrefix(v, filepath.Clean(d)) {\n\t\treturn v, nil\n\t}\n\treturn \"\", &ErrPathTainted{\n\t\tPath: t,\n\t}\n}\n```\n\nThe function is called at line 48 inside `[*Decompressor].Unzip`, which is invoked by `Decode` (line 80) during execution of the webserver CLI (command `download`).\n\n## Root Cause\n\n`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.\n\n## Steps to Reproduce\n\n1. **Deploy Romeo**. A measured app writes its coverage data.\n\n2. **Place the PoC zip on the PVC.** Any pod with write access to the `ReadWriteMany` PVC (or the webserver itself) copies a `poc-path-traversal.tar` into the `coverdir` mount path. The archive contains legitimate coverage files alongside two crafted entries with path-traversal names.\n\n3. **Run the webserver CLI against the running webserver:**\n   ```\n   webserver download \\\n     --server http://localhost:8080 \\\n     --directory /home/user/extract-output\n   ```\n\n4. **Observe the bypass.** `unzip` processes the zip stream. For the malicious entries:\n   ```\n   // entry name: ../extract-outputevil/poc-proof.txt\n   filepath.Join(\"/home/user/extract-output\", \"../extract-outputevil/poc-proof.txt\")\n     => \"/home/user/extract-outputevil/poc-proof.txt\"\n\n   strings.HasPrefix(\"/home/user/extract-outputevil/poc-proof.txt\",\n                     \"/home/user/extract-output\")\n     => true   // BUG: prefix collision; file lands OUTSIDE target dir\n   ```\n   Both malicious entries are written outside `/home/user/extract-output/`. The legitimate coverage files land correctly inside it.\n\n## Impact\n\nSuccessful exploitation gives an attacker arbitrary file write on the machine running the webserver CLI. Real-world primitives include:\n\n- Overwriting `~/.bashrc` / `~/.zshrc` / `~/.profile` for RCE on next shell login\n- Appending to `~/.ssh/authorized_keys` for persistent SSH backdoor\n- Dropping a malicious entry into `~/.kube/config` to hijack cluster access\n- Writing crontab entries for persistent scheduled execution\n\nThe attack surface is widened by the default `ReadWriteMany` PVC access mode, which means any pod in the cluster with the PVC mounted can inject the payload — not just the Romeo webserver itself.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/ctfer-io/romeo/webserver"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.2.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ctfer-io/romeo/security/advisories/GHSA-p799-g7vv-f279"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32805"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ctfer-io/romeo/commit/c2ebcfb9f305fd5f6ef68858de82507dbac10263"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ctfer-io/romeo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-16T20:47:02Z",
    "nvd_published_at" : "2026-03-18T23:17:30Z"
  }
}