https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 14:19:38 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-323052 EUVD-2026-323052 https://cve.radiocsirt.org/vuln/euvd-2026-323052 https://cve.radiocsirt.org/vuln/fkie_cve-2026-47673 <p>Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the jwt and jwk middlewares do not verify that the Authorization header value uses theBearer scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-Bearer scheme identifier (such as Basic or Token) is authenticated identically to a correctly formed Bearer request. This vulnerability is fixed in 4.12.21.</p> <p>Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the jwt and jwk middlewares do not verify that the Authorization header value uses theBearer scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-Bearer scheme identifier (such as Basic or Token) is authenticated identically to a correctly formed Bearer request. This vulnerability is fixed in 4.12.21.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-47673 https://cve.radiocsirt.org/vuln/ghsa-f577-qrjj-4474 <p><strong>Affected:</strong> npm: hono</p> <p>### Summary</p> <p>The `jwt` and `jwk` middlewares do not verify that the `Authorization` header value uses the`Bearer` scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-`Bearer` scheme identifier (such as `Basic` or `Token`) is authenticated identically to a correctly formed `Bearer` request.</p> <p>### Details</p> <p>When processing an `Authorization` (or custom) header, the middleware splits the value on whitespace and uses the second token as the JWT to verify. It does not check that the first token is `bearer` (case-insensitively). RFC 6750 specifies that JWT bearer tokens must be presented using the `Bearer` scheme; other scheme identifiers carry distinct semantics and may be subject to different policies in network-layer security controls.</p> <p>This discrepancy means that scheme-aware external controls — such as WAF rules, API gateways, or reverse proxies that apply policies specific to the `Bearer` scheme identifier — can be bypassed by presenting a valid JWT under a different scheme name.</p> <p>This issue affects `hono/jwt` and `hono/jwk` middleware.</p> <p>### Impact</p> <p>An attacker who possesses a valid JWT may present it under a non-`Bearer` scheme identifier and still pass middleware authentication.</p> <p>This may lead to:</p> <p>- Bypass of network-layer security controls that inspect or filter requests based on the authorization scheme identifier - Token reuse across authentication schemes in…</p> <p><strong>Affected:</strong> npm: hono</p> <p>### Summary</p> <p>The `jwt` and `jwk` middlewares do not verify that the `Authorization` header value uses the`Bearer` scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-`Bearer` scheme identifier (such as `Basic` or `Token`) is authenticated identically to a correctly formed `Bearer` request.</p> <p>### Details</p> <p>When processing an `Authorization` (or custom) header, the middleware splits the value on whitespace and uses the second token as the JWT to verify. It does not check that the first token is `bearer` (case-insensitively). RFC 6750 specifies that JWT bearer tokens must be presented using the `Bearer` scheme; other scheme identifiers carry distinct semantics and may be subject to different policies in network-layer security controls.</p> <p>This discrepancy means that scheme-aware external controls — such as WAF rules, API gateways, or reverse proxies that apply policies specific to the `Bearer` scheme identifier — can be bypassed by presenting a valid JWT under a different scheme name.</p> <p>This issue affects `hono/jwt` and `hono/jwk` middleware.</p> <p>### Impact</p> <p>An attacker who possesses a valid JWT may present it under a non-`Bearer` scheme identifier and still pass middleware authentication.</p> <p>This may lead to:</p> <p>- Bypass of network-layer security controls that inspect or filter requests based on the authorization scheme identifier - Token reuse across authentication schemes in…</p> https://cve.radiocsirt.org/vuln/ghsa-f577-qrjj-4474