Medium 5.1Published Jul 2, 2026

CVE-2026-54430Server-Site Request Forgery in liboauth2

Updated under an hour ago (Oct 28, 2026, 1:00 PM ET)

Does this affect you?

It affects OpenIDC liboauth2. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for OpenIDC liboauth2

Exploited in the last 30 days

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

CVSS: 5.1 MEDIUM (v4.0, CNA)CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:N/SA:N
Weakness (CWE): CWE-918
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: CERT-PL
NVD analysis: Deferred
Record last updated: Jul 2, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

OpenIDC liboauth2 openidc:liboauth2 (from the name)	before 2.3.0	CNA record

References

References

https://cert.pl/en/posts/2026/07/CVE-2026-54430	third-party-advisory
https://github.com/OpenIDC/liboauth2	product
https://github.com/OpenIDC/liboauth2/commit/347507ac5b51f48c2933bbe49b2ee07c2af4712b	issue-tracking

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.