Bug 2524980 (CVE-2026-81829) - CVE-2026-81829 smallrye-jwt: quarkus-smallrye-jwt: smallrye-jwt: Unauthenticated same-origin SSRF via unsanitized JWT kid header in AwsAlbKeyResolver
Summary: CVE-2026-81829 smallrye-jwt: quarkus-smallrye-jwt: smallrye-jwt: Unauthentica...
Keywords:
Status: NEW
Alias: CVE-2026-81829
Deadline: 2026-10-15
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-27 14:08 UTC by Abhishek Raj
Modified: 2026-09-17 13:55 UTC (History)
47 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Abhishek Raj 2026-08-27 14:08:16 UTC
A path traversal and same-origin Server-Side Request Forgery (SSRF) vulnerability was found in the AWS ALB key resolver of SmallRye JWT. When the AWS_ALB key provider is configured, AwsAlbKeyResolver constructs the verification-key URL by concatenating the configured key location with the attacker-controlled kid value from the inbound, unverified JWT header. The kid value is only checked for null and, optionally, against a configured expected value. Characters such as /, .., ?, and # are not rejected or encoded. An unauthenticated attacker can therefore cause the application server to issue GET requests to arbitrary paths and manipulate query parameters on the configured OIDC/JWKS origin before JWT signature verification. This can be exploited remotely without authentication or user interaction, allowing attackers to read non-public data on the same origin as the configured key endpoint.

Comment 2 Abhishek Raj 2026-09-17 13:47:04 UTC


Note You need to log in before you can comment on or make changes to this bug.