A flaw was found in librest. The PKCE implementation for OAuth authorization uses the GRand function from the GLib API, a cryptographically insecure… (CVE-2026-16615)
A vulnerability in librest's PKCE implementation for OAuth authorization arises from using the GLib API's GRand function, which is a cryptographically insecure pseudo-random number generator. This results in a code verifier with insufficient entropy, enabling attackers to predict or reconstruct it. Consequently, attackers can bypass PKCE protections and impersonate clients during the OAuth 2.0 authorization flow.
AI Analysis
Technical Summary
The librest library's implementation of PKCE for OAuth authorization relies on the GRand function from the GLib API to generate the code verifier. GRand is a cryptographically insecure pseudo-random number generator, leading to code verifiers that lack sufficient cryptographic entropy. An attacker can reverse-engineer the PRNG seed to predict or reconstruct the code verifier string, thereby bypassing PKCE protections and impersonating the client in the OAuth 2.0 authorization process. This vulnerability is identified as CVE-2026-16615 and is associated with CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator). The CVSS v3.1 vector indicates network attack vector, high attack complexity, no privileges required, user interaction required, unchanged scope, and high confidentiality and integrity impact.
Potential Impact
An attacker can bypass PKCE protections in OAuth 2.0 authorization by predicting or reconstructing the code verifier due to insufficient cryptographic entropy. This allows successful client impersonation during the OAuth authorization flow, potentially leading to unauthorized access to protected resources. The vulnerability impacts confidentiality and integrity but does not affect availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Users should monitor the Red Hat advisory and related vendor communications for updates on patches or mitigations. Until a fix is available, consider mitigating risk by avoiding reliance on the affected PKCE implementation or employing additional compensating controls in OAuth authorization flows.
A flaw was found in librest. The PKCE implementation for OAuth authorization uses the GRand function from the GLib API, a cryptographically insecure… (CVE-2026-16615)
Description
A vulnerability in librest's PKCE implementation for OAuth authorization arises from using the GLib API's GRand function, which is a cryptographically insecure pseudo-random number generator. This results in a code verifier with insufficient entropy, enabling attackers to predict or reconstruct it. Consequently, attackers can bypass PKCE protections and impersonate clients during the OAuth 2.0 authorization flow.
CVSS v3.1
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The librest library's implementation of PKCE for OAuth authorization relies on the GRand function from the GLib API to generate the code verifier. GRand is a cryptographically insecure pseudo-random number generator, leading to code verifiers that lack sufficient cryptographic entropy. An attacker can reverse-engineer the PRNG seed to predict or reconstruct the code verifier string, thereby bypassing PKCE protections and impersonating the client in the OAuth 2.0 authorization process. This vulnerability is identified as CVE-2026-16615 and is associated with CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator). The CVSS v3.1 vector indicates network attack vector, high attack complexity, no privileges required, user interaction required, unchanged scope, and high confidentiality and integrity impact.
Potential Impact
An attacker can bypass PKCE protections in OAuth 2.0 authorization by predicting or reconstructing the code verifier due to insufficient cryptographic entropy. This allows successful client impersonation during the OAuth authorization flow, potentially leading to unauthorized access to protected resources. The vulnerability impacts confidentiality and integrity but does not affect availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Users should monitor the Red Hat advisory and related vendor communications for updates on patches or mitigations. Until a fix is available, consider mitigating risk by avoiding reliance on the affected PKCE implementation or employing additional compensating controls in OAuth authorization flows.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-223h-642r-2f6v
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-16615"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a6151269c2644c7f8da6329
Added to database: 07/22/2026, 23:24:22 UTC
Last enriched: 07/22/2026, 23:57:59 UTC
Last updated: 07/23/2026, 02:51:54 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.