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

Advisory record · `GHSA-vh7g-p26c-j2cw`

- **Identifiers:** `GHSA-vh7g-p26c-j2cw` · `CVE-2022-39222`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 3 Oct 2022
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/dexidp/dex` (Go): affected `<2.35.0`; fixed in `2.35.0`

## 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

- 9.3 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`, from 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

- 31 Oct 2026, 14:43 UTC: First seen by agentprime
- 31 Oct 2026, 14:43 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vh7g-p26c-j2cw)

## Sources

- [GitHub Advisory Database: GHSA-vh7g-p26c-j2cw](https://github.com/advisories/GHSA-vh7g-p26c-j2cw)
- [OSV: GHSA-vh7g-p26c-j2cw](https://osv.dev/vulnerability/GHSA-vh7g-p26c-j2cw)
- <https://github.com/dexidp/dex/security/advisories/GHSA-vh7g-p26c-j2cw>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-39222>
- <https://github.com/dexidp/dex/commit/49471b14c8080ddb034d4855841123d378b7a634>
- <https://github.com/dexidp/dex>
- <https://github.com/dexidp/dex/releases/tag/v2.35.0>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vh7g-p26c-j2cw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vh7g-p26c-j2cw/>. Everything for agents: <https://agentprime.io/llms.txt>.
