CVE Catalog

CVE-2026-100351

HighCVSS 7.4
Published: Updated: Translated: NVD NIST

Summary

In kin-openapi from 0.144.0 until 0.147.0, openapi3filter.ValidationHandler validates an operation selected from decoded URL.Path while a downstream gorilla/mux router configured with UseEncodedPath can dispatch a different operation selected from URL.RawPath. When a public exact route and a protected parameterized route use the same method and overlap after decoding, an unauthenticated remote request containing an encoded path separator can be validated as public and then dispatched to the protected handler without invoking the configured AuthenticationFunc.

Risk Assessment

Possible authentication bypass and access to protected endpoints by an unauthenticated remote attacker. Proxies that canonicalize the URI before forwarding may prevent this specific mismatch.

Recommendation

Update kin-openapi to version 0.147.0 or later. Consider URI canonicalization at the proxy level and verify consistency between public and protected routes.

Other vulnerabilities in kin-openapi

See all
Original NVD description (English source)

kin-openapi is a Go project for handling OpenAPI files. From 0.144.0 until 0.147.0, openapi3filter.ValidationHandler validates an operation selected from decoded URL.Path while a downstream gorilla/mux router configured with UseEncodedPath can dispatch a different operation selected from URL.RawPath. When a public exact route and a protected parameterized route use the same method and overlap after decoding, an unauthenticated remote request containing an encoded path separator can be validated as public and then dispatched to the protected handler without invoking the configured AuthenticationFunc. The reachable path parameter is constrained to an encoded representation that decodes to the public literal route, and proxies that canonicalize the URI before forwarding prevent this specific mismatch. This issue is fixed in version 0.147.0.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS