Salvo is vulnerable to reflected XSS in the list_html function

Exploitation

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

CVSS

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

EPSS

• CVE-2026-22256: 0.33% estimated exploitation activity in the next 30 days; percentile 26.85 (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 function listhtml generates an file view of a folder which includes a render of the current path, in which its inserted in the HTML without proper sanitation, leading to reflected XSS. The request path is decoded and normalized in the matching stage but is not inserted raw in the HTML view (current.path). The only constraint here is for the root path (e.g., /files in the PoC example) to have a subdirectory (e. g., common ones like styles/scripts/etc.) so that the matching returns the list HTML page instead of the Not Found page. Details The vulnerable snippet of code is the following: dir.rs As seen here <title{}</title it is inserted unsafely. PoC https://github.com/user-attachments/assets/92a29a67-547b-40a5-af26-f1b0dd332702 Here is the example app, note this doesn’t need an upload feature (e.g to the other reported vulnerability), only the sub-folder is required. main.rs Cargo.toml Setup commands: Impact JavaScript execution, most likely leading to an account takeover,…

Published by the source

8 Jan 2026, 21:22 UTC

Last modified by the source

8 Jan 2026, 21:37 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rjf8-2wcw-f6mp

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

# Patch Next advisory brief: CVE-2026-22256

Advisory: Salvo is vulnerable to reflected XSS in the list_html function
IDs: CVE-2026-22256, GHSA-rjf8-2wcw-f6mp
Record: https://patchnext.com/advisories/cve-2026-22256 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: salvo 0.88.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io salvo: affected < 0.88.1; fixed in 0.88.1

## Suggested inspection (read-only)
- crates.io salvo: 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 salvo.
- 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-rjf8-2wcw-f6mp (GitHub-reviewed advisory GHSA-rjf8-2wcw-f6mp lists affected ranges: crates.io salvo >=0 <0.88.1)

Commands are suggestions: review each one before running it.