Advisory record · GHSA-rrqr-7w59-637v

Pomerium exposed OAuth2 access and ID tokens in user info endpoint response

CVSS 5.7 MediumEPSS 0.0042 · 36th percentile

Published by the GitHub Advisory Database at 5 Jul 2024, 19:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/pomerium/pomeriumGo<0.26.10.26.1
Identifiers
GHSA-rrqr-7w59-637v · CVE-2024-39315 · GO-2024-2965
Weakness (CWE)
CWE-201
Published
5 Jul 2024
Updated
10 Sept 2026

Machine-written summary

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

Pomerium versions before 0.26.1 expose serialized OAuth2 access and ID tokens from the logged-in user's session on the user info page at /.pomerium. An attacker who can run a script on a page proxied through Pomerium, such as through an XSS flaw in an upstream application, could read these tokens, and upstream applications that rely only on the ID token may be open to user impersonation. Upgrade to Pomerium 0.26.1; the source lists no workarounds.

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

Timeline

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