Advisory record · GHSA-vh7g-p26c-j2cw

Dex vulnerable to Man-in-the-Middle allowing ID token capture via intercepted authorization code

CVSS 9.3 CriticalCriticalEPSS 0.016 · 76th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 3 Oct 2022, 19:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/dexidp/dexGo<2.35.02.35.0
Identifiers
GHSA-vh7g-p26c-j2cw · CVE-2022-39222
Weakness (CWE)
CWE-200 · CWE-862
Published
3 Oct 2022
Updated
10 Sept 2026

Machine-written summary

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

Dex (github.com/dexidp/dex) versions before 2.35.0 are vulnerable. An attacker who can get a victim to visit a malicious website can run a poll against the Dex approval endpoint to capture the OAuth authorization code, then exchange it for an ID token and access applications that accept those tokens. Upgrade to Dex 2.35.0. Disabling public clients is the only listed way to defend against this issue without upgrading.

Written 6 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
9.3 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.016, the 76th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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