Advisory record · GHSA-wj7q-gjg8-3cpm

league/oauth2-server key exposed in exception message when passing as a string and providing an invalid pass phrase

CVSS 8.2 HighEPSS 0.0095 · 62nd percentile

Published by the GitHub Advisory Database at 6 Jul 2023, 21:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
league/oauth2-serverPackagist>=8.3.2, <8.4.2 || >=8.5.0, <8.5.38.4.2, 8.5.3
Identifiers
GHSA-wj7q-gjg8-3cpm · CVE-2023-37260 · PKSA-pc52-dbxt-c1w6
Weakness (CWE)
CWE-200 · CWE-209
Published
6 Jul 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The league/oauth2-server PHP package, versions from 8.3.2 to before 8.4.2 and from 8.5.0 to before 8.5.3, can leak a key in an exception message. Servers that passed their key as a string to the CryptKey constructor, rather than as a file path, had the key included in a LogicException message when no valid pass phrase was supplied where one was required. The source does not describe how an attacker would read that message. Upgrade to 8.4.2 or 8.5.3, which are the fixed versions; if upgrading is not possible, the source suggests passing the key as a file instead of a string.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0095, the 62nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:04 UTC First seen by agentprime
  2. 31 Oct 2026, 14:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.