CVE-2026-6321: fast-uri vulnerable to path traversal via percent-encoded dot segments

Published May 4, 2026
·
Updated

Impact

fast-uri v3.1.0 and earlier decodes percent-encoded path separators (%2F) and dot segments (%2E) before applying dot-segment removal in normalize() and equal(). This makes encoded path data behave like real / and .., so distinct URIs collapse onto the same normalized path.

For example, http://example.com/public/%2e%2e/admin normalizes to http://example.com/admin, and equal() considers them the same URI.

Applications that normalize or compare attacker-controlled URLs to enforce path-based policy can be bypassed. A path that looks confined under an allowed prefix can normalize to a different location.

Patches

Upgrade to fast-uri >= 3.1.1.

Workarounds

None. Upgrade to the patched version.

Other sources

fast-uri decoded percent-encoded path separators and dot segments before applying dot-segment removal in its normalize() and equal() functions. Encoded path data was treated like real slashes and parent-directory references, so distinct URIs could collapse onto the same normalized path. Applications that normalize or compare attacker-controlled URLs to enforce path-based policy can be bypassed, with a path that appears confined under an allowed prefix normalizing to a different location. Versions <= 3.1.0 are affected. Update to 3.1.1 or later.

MITRE

Affected Software

3 affected componentsFixes available
crates/fast-uri<=3.1.0
npm/fast-uri<=3.1.0
3.1.1
Openjsf Fast-uri Node.js<3.1.1

Event History

May 4, 2026
CVE Published
via MITRE·07:31 PM
Data Sourced
via MITRE·07:31 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·08:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
Affected Software
May 8, 2026
Advisory Published
via GitHub·05:15 PM
Data Sourced
via GitHub·05:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-6321?

The severity of CVE-2026-6321 is considered high due to the potential for path traversal vulnerabilities.

2

How do I fix CVE-2026-6321?

To fix CVE-2026-6321, update the fast-uri library to version 3.1.1 or later.

3

What kind of attack does CVE-2026-6321 enable?

CVE-2026-6321 enables attackers to exploit a path traversal vulnerability to access unintended files or directories on the server.

4

Which versions of fast-uri are affected by CVE-2026-6321?

CVE-2026-6321 affects fast-uri versions up to and including 3.1.0.

5

What functions in fast-uri are related to CVE-2026-6321?

The normalize() and equal() functions in fast-uri are related to CVE-2026-6321 as they improperly handle percent-encoded path separators.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203