Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Salvo has a Path Traversal in salvo-proxy::encode_url_path allows API Gateway Bypass

CVE-2026-33242GHSA-f842-phm9-p4v4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (salvo 0.89.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io salvo

    Affected
    >= 0.39.0, <= 0.89.2
    Fixed in
    0.89.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-33242: 0.57% estimated exploitation activity in the next 30 days; percentile 47.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Details A Path Traversal and Access Control Bypass vulnerability was discovered in the salvo-proxy component of the Salvo Rust framework (v0.89.2). The vulnerability allows an unauthenticated external attacker to bypass proxy routing constraints and access unintended backend paths (e.g., protected endpoints or administrative dashboards). This issue stems from the encodeurlpath function, which fails to normalize "../" sequences and inadvertently forwards them verbatim to the upstream server by not re-encoding the "." character. --- Technical Details If someone tries to attack by sending a special code like %2e%2e, Salvo changes it back to ../ when it first checks the path. The proxy then gets this plain ../ value. When making the new URL to send forward, the encodeurlpath function tries to change the path again, but its normal settings do not include the . (dot) character. Because of this, the proxy puts ../ straight into the new URL and sends a request like GET /api/../admin HTTP/1.1…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-f842-phm9-p4v4

Agent brief

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

# Patch Next advisory brief: CVE-2026-33242

Advisory: Salvo has a Path Traversal in salvo-proxy::encode_url_path allows API Gateway Bypass
IDs: CVE-2026-33242, GHSA-f842-phm9-p4v4
Record: https://patchnext.com/advisories/cve-2026-33242 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: salvo 0.89.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io salvo: affected >= 0.39.0, <= 0.89.2; fixed in 0.89.3

## 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-f842-phm9-p4v4 (GitHub-reviewed advisory GHSA-f842-phm9-p4v4 lists affected ranges: crates.io salvo >=0.39.0 <=0.89.2)

Commands are suggestions: review each one before running it.

Loading voting…