Answer in brief
CVE-2026-81829 records a Medium severity (CVSS 5.3) vulnerability in Smallrye-jwt: quarkus-smallrye-jwt: smallrye-jwt: unauthenticated same-origin ssrf via unsanitized jwt kid header in awsalbkeyresolver. The current sources do not mark it as known exploited. The current feed maps Red Hat/exploit-intelligence/agent-client-rhel9 (generic), Red Hat/quarkus-smallrye-jwt (generic), Red Hat/smallrye-jwt (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/exploit-intelligence/agent-client-rhel9 (generic), Red Hat/quarkus-smallrye-jwt (generic), Red Hat/smallrye-jwt (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/exploit-intelligence/agent-client-rhel9generic | * | Not reported |
| Red Hat/quarkus-smallrye-jwtgeneric | * | Not reported |
| Red Hat/smallrye-jwtgeneric | * | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
A flaw was found in SmallRye JWT's AwsAlbKeyResolver, which is used by applications to verify JSON Web Tokens signed by AWS Application Load Balancers. When the AWS_ALB key provider is configured, the resolver constructs the key-fetch URL by directly concatenating the attacker-controlled kid header value from an inbound JWT without sanitizing path traversal characters or query-string separators. This allows an unauthenticated remote attacker to force the application server to issue GET requests to arbitrary paths on the same origin as the configured key endpoint. As a result, non-public endpoints or internal data reachable on that origin may be read by the attacker before JWT signature verification takes place.
Quoted source text, attributed separately from HOL analysis.