CVE-2026-54431Disclosure

LOWCVSS 5.1 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-358

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

1 mentions across 1 observed day

What's happening

Technical details provided in 1 signal
Disclosure: 1 classified signal
1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Signal classification1 categories

Disclosure

1100.0%

Referenced assets1 URL

By indicator

https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-54431

Full discourse1 post

Vulmon Vulnerability Feed@VulmonFeeds92d
Disclosure
CVE-2026-54431 Private Key Exposure in liboauth2 DPoP Verifier Before Version 2.3.0 https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-54431
Post summary
A new CVE (CVE-2026-54431) for liboauth2 DPoP verifier has been disclosed, highlighting a private key exposure issue in versions before 2.3.0.
00000100
4.1K followersView on X

Explore more

Back to dashboard