CVE-2026-54431
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
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.1
- CVSS vector
- CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- EPSS probability
- 0.18%
- CWE
- CWE-358
- Published
- 2026-07-02
- Last modified
- 2026-07-02
Affected products
- OpenIDC liboauth2
Weakness type
Related vulnerabilities
- CVE-2026-46582 — A wildcard replay, as another piece of data, triggers poisoning in the serve expired reply path
- CVE-2026-65058 — Trezor Safe improper security check in on-device display
- CVE-2026-49783 — Secure Boot Security Feature Bypass Vulnerability
- CVE-2026-12577 — DVP80ES3 Improperly Implemented Security Check for Standard vulnerability
- CVE-2026-48797 — Backpropagate: backprop ui --auth and backprop ui --share do not enforce authentication
- CVE-2026-42081 — free5GC: UE Security Capability bypass on NGAP PathSwitchRequest
- CVE-2026-42082 — free5GC: Missing Concurrent NAS SMC Validation During NGAP Handover
- CVE-2026-44473 — Ella Core: UE Downlink Redirection via Forged PDUSessionResourceSetupResponse