Is salvo affected by CVE-2026-33242?

crates.io salvo is affected in >=0.39.0 <0.89.3.

Is CVE-2026-33242 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.6%.

high

CVE-2026-33242

Q: Is CVE-2026-33242 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.6%.

crates.io · salvo

Summary

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

Severity: high
EPSS: 0.6% (p42)
Also known as: GHSA-f842-phm9-p4v4
Published: 2026-03-19

References

https://github.com/salvo-rs/salvo/security/advisories/GHSA-f842-phm9-p4v4
https://nvd.nist.gov/vuln/detail/CVE-2026-33242
https://github.com/salvo-rs/salvo/commit/7bac30e6960355c58e358e402072d4a3e5c4e1bb#diff-e319bf7afcb577f7e9f4fb767005072f6335d23f306dd52e8c94f3d222610d02R20

Related advisories

CVE-2026-33241 — high · crates.io/salvo
CVE-2026-22256 — high · crates.io/salvo
CVE-2026-22257 — high · crates.io/salvo

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.