CVE-2026-16615

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory published 2026-07-22. a secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw was found in librest. The PKCE implementation for OAuth authorization uses the GRand function from the GLib API, a cryptographically insecure pseudo-random number generator. Because the generated "code verifier" lacks sufficient cryptographic entropy, a malicious actor can reverse-engineer the pseudo-random number generator (PRNG) seed to predict or reconstruct the code verifier string, allowing an attacker to bypass PKCE protections and successfully impersonate the client during the OAuth 2.0 authorization flow.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 22, 2026
Patch available. Sources: redhat.
generic

Weak random number generation in PKCE implementation (#25) · Issues · GNOME / librest · GitLab

https://gitlab.gnome.org/GNOME/librest/-/issues/25
redhat

2504432 – (CVE-2026-16615) CVE-2026-16615 librest: weak random number generation in PKCE implementation

https://bugzilla.redhat.com/show_bug.cgi?id=2504432
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-16615

Vendor Advisories for CVE-2026-16615(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 04:51 UTCEG score recompute
  3. 2026-07-27 04:51 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 03:26 UTCEG score recompute
  7. 2026-07-26 03:26 UTCGHSA enrichment
  8. 2026-07-25 14:17 UTCEPSS rescore
  9. 2026-07-25 14:17 UTCEPSS rescore
  10. 2026-07-24 14:17 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:06 UTCEG score recompute
  14. 2026-07-22 21:58 UTCEG score recompute
  15. 2026-07-22 21:58 UTCGHSA enrichment
  16. 2026-07-22 18:34 UTCEG score recompute
  17. 2026-07-22 18:33 UTCGHSA enrichment
  18. 2026-07-22 16:31 UTCEG score recompute
  19. 2026-07-22 16:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16615?
CVE-2026-16615 is a medium vulnerability published on July 22, 2026. A flaw was found in librest. The PKCE implementation for OAuth authorization uses the GRand function from the GLib API, a cryptographically insecure pseudo-random number generator. Because the generated "code verifier" lacks sufficient cryptographic entropy, a malicious actor can reverse-engineer…
When was CVE-2026-16615 disclosed?
CVE-2026-16615 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16615 actively exploited?
CVE-2026-16615 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.3% of all scored CVEs.
What is the CVSS score of CVE-2026-16615?
CVE-2026-16615 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-16615?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16615, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16615

Explore →

Is Your Infrastructure Affected by CVE-2026-16615?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs