CVE-2026-54430 Details
Description
liboauth2 is vulnerable to Server-Side Request Forgery in oauth2_jose_jwks_aws_alb_resolve() function. The AWS ALB verifier reads both signer and kid from the unverified JWT header. If signer matches the configured ARN, kid is appended to alb_base_url without URL encoding or path sanitization, and the HTTP GET is issued before signature verification. This allows an attacker to force the server to send a GET request to an attacker-chosen internal path. This issue was fixed in version 2.3.0
A server-side request forgery (SSRF) vulnerability has been identified in the liboauth2 library, specifically within the oauth2_jose_jwks_aws_alb_resolve() function. This vulnerability arises because the AWS Application Load Balancer (ALB) verifier processes the 'signer' and 'kid' headers from an unverified JWT header before the signature is validated. If the 'signer' matches the configured ARN, the 'kid' is added to the ALB base URL without proper URL encoding or path sanitization, allowing an attacker to manipulate the server into sending a GET request to a chosen internal path.
Users can upgrade to liboauth2 version 2.3.0 or later, where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jul 2, 2026CISA-ADP
Assessed Jul 2, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-918 | Server-Side Request Forgery (SSRF) | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| OpenIDC liboauth2 | < 2.3.0 (semver) |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 2, 2026 | CVE Modified | CISA-ADP |
| Jul 2, 2026 | CVE Modified | [email protected] |
| Jul 2, 2026 | New CVE Received | [email protected] |
Volerion