CVE-2026-16615

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM 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

A fix is available — apply it.

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(medium)
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

September 1, 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(4)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrest-0:0.9.1-11.el10_0.12026-09-01redhat
redhatrest-0:0.9.1-11.el10_2.12026-07-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
librest0.10.2-1 ... 1.0.0-1 (9 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
librest0.10.2-1, 0.9.1-6, 1.0.0-1——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
librest0.10.2-1, 0.9.1-6, 1.0.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
librest0.10.2-1, 0.9.1-6, 1.0.0-1——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 88× 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.

Showing the most recent 100 of 186 total refreshes for this CVE.

  1. 2026-09-14 03:37 UTCEG score recompute
  2. 2026-09-14 03:37 UTCVendor advisory
  3. 2026-09-14 03:37 UTCGHSA enrichment
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-13 02:15 UTCEG score recompute
  6. 2026-09-13 02:15 UTCVendor advisory
  7. 2026-09-13 02:15 UTCGHSA enrichment
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-12 00:51 UTCEG score recompute
  10. 2026-09-12 00:51 UTCVendor advisory
  11. 2026-09-12 00:51 UTCGHSA enrichment
  12. 2026-09-11 14:52 UTCEPSS rescore
  13. 2026-09-11 09:36 UTCEPSS rescore
  14. 2026-09-10 21:33 UTCEG score recompute
  15. 2026-09-10 21:33 UTCVendor advisory
  16. 2026-09-10 21:33 UTCGHSA enrichment
  17. 2026-09-10 09:34 UTCEPSS rescore
  18. 2026-09-09 09:15 UTCEG score recompute
  19. 2026-09-09 09:15 UTCVendor advisory
  20. 2026-09-09 09:15 UTCGHSA enrichment
  21. 2026-09-08 22:00 UTCEPSS rescore
  22. 2026-09-07 21:41 UTCEG score recompute
  23. 2026-09-07 21:41 UTCVendor advisory
  24. 2026-09-07 21:41 UTCGHSA enrichment
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 13:47 UTCEPSS rescore
  2. 2026-09-05 19:34 UTCEG score recompute
  3. 2026-09-05 19:34 UTCVendor advisory
  4. 2026-09-05 19:34 UTCGHSA enrichment
  5. 2026-09-04 13:54 UTCEG score recompute
  6. 2026-09-04 13:54 UTCVendor advisory
  7. 2026-09-04 13:54 UTCGHSA enrichment
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:11 UTCEPSS rescore
  10. 2026-09-01 18:26 UTCEG score recompute
  11. 2026-09-01 18:26 UTCVendor advisory
  12. 2026-09-01 18:25 UTCGHSA enrichment
  13. 2026-09-01 17:37 UTCEG score recompute
  14. 2026-09-01 17:37 UTCVendor advisory
  15. 2026-09-01 17:37 UTCGHSA enrichment
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-31 02:17 UTCEG score recompute
  19. 2026-08-31 02:17 UTCVendor advisory
  20. 2026-08-31 02:17 UTCGHSA enrichment
  21. 2026-08-30 19:17 UTCEPSS rescore
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-30 00:53 UTCEG score recompute
  24. 2026-08-30 00:53 UTCVendor advisory
  25. 2026-08-30 00:53 UTCGHSA enrichment
  26. 2026-08-28 21:41 UTCEPSS rescore
  27. 2026-08-27 14:25 UTCEPSS rescore
  28. 2026-08-27 10:18 UTCEG score recompute
  29. 2026-08-27 10:18 UTCVendor advisory
  30. 2026-08-27 10:18 UTCGHSA enrichment
  31. 2026-08-26 14:46 UTCEPSS rescore
  32. 2026-08-26 06:54 UTCEG score recompute
  33. 2026-08-26 06:54 UTCVendor advisory
  34. 2026-08-26 06:54 UTCGHSA enrichment
  35. 2026-08-25 13:48 UTCEPSS rescore
  36. 2026-08-25 04:52 UTCEG score recompute
  37. 2026-08-25 04:52 UTCVendor advisory
  38. 2026-08-25 04:52 UTCGHSA enrichment
  39. 2026-08-24 03:30 UTCVendor advisory
  40. 2026-08-24 03:30 UTCGHSA enrichment
  41. 2026-08-23 00:56 UTCEG score recompute
  42. 2026-08-23 00:56 UTCVendor advisory
  43. 2026-08-23 00:56 UTCGHSA enrichment
  44. 2026-08-23 00:19 UTCEPSS rescore
  45. 2026-08-21 23:49 UTCEPSS rescore
  46. 2026-08-21 23:34 UTCEG score recompute
  47. 2026-08-21 23:34 UTCVendor advisory
  48. 2026-08-21 23:34 UTCGHSA enrichment
  49. 2026-08-20 22:55 UTCEPSS rescore
  50. 2026-08-20 22:11 UTCVendor advisory
  51. 2026-08-20 22:11 UTCGHSA enrichment
  52. 2026-08-19 20:44 UTCEG score recompute
  53. 2026-08-19 20:44 UTCVendor advisory
  54. 2026-08-19 20:44 UTCGHSA enrichment
  55. 2026-08-19 17:03 UTCEPSS rescore
  56. 2026-08-18 19:12 UTCEG score recompute
  57. 2026-08-18 19:12 UTCVendor advisory
  58. 2026-08-18 19:12 UTCGHSA enrichment
  59. 2026-08-18 13:48 UTCEPSS rescore
  60. 2026-08-17 13:47 UTCEPSS rescore
  61. 2026-08-17 12:41 UTCEG score recompute
  62. 2026-08-17 12:41 UTCVendor advisory
  63. 2026-08-17 12:41 UTCGHSA enrichment
  64. 2026-08-16 14:56 UTCEPSS rescore
  65. 2026-08-16 11:19 UTCEG score recompute
  66. 2026-08-16 11:19 UTCVendor advisory
  67. 2026-08-16 11:19 UTCGHSA enrichment
  68. 2026-08-16 02:14 UTCEPSS rescore
  69. 2026-08-15 09:57 UTCEG score recompute
  70. 2026-08-15 09:57 UTCVendor advisory
  71. 2026-08-15 09:57 UTCGHSA enrichment
  72. 2026-08-15 01:30 UTCEPSS rescore
  73. 2026-08-14 08:34 UTCEG score recompute
  74. 2026-08-14 08:34 UTCVendor advisory
  75. 2026-08-14 08:34 UTCGHSA enrichment

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 September 1, 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.0% 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

See which npm, PyPI, Go, and Maven packages are affected by 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