| Name | CVE-2026-54431 |
| Description | In liboauth2 the Demonstrating Proof-of-Possession (DPoP) verifier accepts a proof whose JSON Web Key (jwk) header contains private key material. RFC 9449 section 4.3 step 7 requires the verifier to reject such a proof but oauth2_token_verify() function returns success for a malformed DPoP proof that embeds the private Elliptic Curve (EC) key in the header. This issue was fixed in version 2.3.0 |
| Source | CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| liboauth2 (PTS) | bullseye | 1.4.0.1-1 | vulnerable |
| bookworm | 1.4.5.4-1 | vulnerable |
| trixie | 2.1.0-2 | vulnerable |
| forky, sid | 2.3.0-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| liboauth2 | source | (unstable) | 2.3.0-1 | | | |
Notes
[trixie] - liboauth2 <no-dsa> (Minor issue)
[bookworm] - liboauth2 <postponed> (Minor issue)
[bullseye] - liboauth2 <postponed> (Minor issue)
Fixed by: https://github.com/OpenIDC/liboauth2/commit/c0b57152ed6a0af33aeb04a60bd7f5bff5ab8800 (v2.3.0)