rama has Stored XSS in ServeDir HTML directory listing via unescaped file names and URI path

Exploitation

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

CVSS

3.7 · CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Resolved: https://github.com/plabayo/rama/commit/89ddff578fd78bbebec99482d7030f28c07757a3 Summary plabayo/rama contains a stored/reflected cross-site scripting issue in the ServeDir HTML directory listing feature. When ServeDir is configured with DirectoryServeMode::HtmlFileList, file names and URI path components are inserted directly into generated HTML without HTML escaping. If an attacker can create or influence a file or directory name inside a served directory, they may inject HTML or JavaScript into the directory listing page. This can execute script in the browser of any user who visits the affected directory listing. Affected Repository plabayo/rama Affected Component rama-http/src/service/fs/servedir/openfile.rs Root Cause The HTML directory listing is constructed using string formatting and inserts untrusted values directly into HTML. The directory listing row includes the file or directory name in both the link text and the href attribute: rows.push(format!( "<tr<td{5} <a…

Published by the source

7 Jul 2026, 23:41 UTC

Last modified by the source

7 Jul 2026, 23:41 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cwv4-h3j5-w3cf

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

# Patch Next advisory brief: GHSA-cwv4-h3j5-w3cf

Advisory: rama has Stored XSS in ServeDir HTML directory listing via unescaped file names and URI path
IDs: GHSA-cwv4-h3j5-w3cf
Record: https://patchnext.com/advisories/ghsa-cwv4-h3j5-w3cf (revision 1, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rama 0.3.0-rc.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io rama: affected < 0.3.0-rc.1; fixed in 0.3.0-rc.1

## Suggested inspection (read-only)
- crates.io rama: 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 rama.
- 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-cwv4-h3j5-w3cf (GitHub-reviewed advisory GHSA-cwv4-h3j5-w3cf lists affected ranges: crates.io rama >=0 <0.3.0-rc.1)

Commands are suggestions: review each one before running it.