Advisory record · GHSA-7qjx-gp9h-65qj

Dex: Token-exchange endpoint is missing AllowedConnectors enforcement

CVSS 8.7 High

Published by the GitHub Advisory Database at 9 Jun 2026, 21:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/dexidp/dexGo<0.0.0-20260303131938-204dbb2e3ff70.0.0-20260303131938-204dbb2e3ff7
Identifiers
GHSA-7qjx-gp9h-65qj · GO-2026-5231
Weakness (CWE)
CWE-285
Published
9 Jun 2026
Updated
25 Jun 2026

Machine-written summary

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

Dex (github.com/dexidp/dex) on master builds before 0.0.0-20260303131938-204dbb2e3ff7 is affected; the token-exchange endpoint does not check the client's AllowedConnectors list before issuing tokens. An attacker holding a leaked client secret plus a subject token from a connector the client should not use can obtain Dex-signed tokens reflecting that forbidden connector. Upgrade to 0.0.0-20260303131938-204dbb2e3ff7 or later.

Written 7 Nov 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.7 High 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 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.