CVE-2024-39315: Pomerium exposed OAuth2 access and ID tokens in user info endpoint response
Impact The Pomerium user info page (at /.pomerium) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens are not intended to be exposed to end users. This issue may be more severe in the presence of an XSS vulnerability in an upstream application proxied through Pomerium.
Published Jul 5, 2024 · Updated Aug 8, 2024
Affected packages
github.com/pomerium/pomerium
- Ecosystem
- Go
- Affected
- < 0.26.1
- Fixed in
- 0.26.1
- Check
go list -m github.com/pomerium/pomerium
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The Pomerium user info page (at /.pomerium) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens are not intended to be exposed to end users.
This issue may be more severe in the presence of an XSS vulnerability in an upstream application proxied through Pomerium. If an attacker could insert a malicious script onto a web page proxied through Pomerium, that script could access these tokens by making a request to the /.pomerium endpoint.
Upstream applications that authenticate only the ID token may be vulnerable to user impersonation using a token obtained in this manner.
Note that an OAuth2 access token or ID token by itself is not sufficient to hijack a user's Pomerium session. Upstream applications should not be vulnerable to user impersonation via these tokens provided:
- the application verifies the Pomerium JWT for each request,
- the connection between Pomerium and the application is secured by mTLS,
- or the connection between Pomerium and the application is otherwise secured at the network layer.
Patches
Patched in Pomerium v0.26.1.
Workarounds
None
For more information
If you have any questions or comments about this advisory:
- Open an issue in pomerium/pomerium
- Email us at [[email protected]](mailto:[email protected])
Credit to Vadim Sheydaev, aka Enr1g for reporting this issue.
Credited to Enr1g.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-50285
Pomerium Pre-Auth Memory Exhaustion via Unbounded zstd Decompression in HPKE Callback
high7.5Jul 15, 2026CVE-2024-47616
Pomerium service account access token may grant unintended access to databroker API
high6.8Oct 2, 2024CVE-2022-24797
Exposure of debug and metrics endpoints in Pomerium
medium6.5Sep 6, 2024
