🛡️ CVE-2024-39315 — pomerium

🟡 CVSS 5.7 — Medium ✅ No Known Exploit CWE-201 NVD
5.7
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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. 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](https://www.pomerium.com/docs/capabilities/getting-users-identity) 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](https://github.com/pomerium/pomerium/issues)
  • Email us at [security@pomerium.com](mailto:[email protected])

Credit to Vadim Sheydaev, aka Enr1g for reporting this issue.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.

Affected software

CVE-2024-39315 is recorded against 2 packages.

  • github.com/pomerium/pomerium
  • pomerium (fixed in 0.26.1)

Timeline and source

Published on 5 July 2024 and last revised on 3 March 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)

Details

Severity Medium
CVSS Score 5.7
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
CWE CWE-201
Public Exploit ✅ No
Source NVD
Published 2024-07-05
Updated 2026-08-12
Modified 2026-03-03

Affected Packages

Software From version Fixed in
github.com/pomerium/pomerium — —
pomerium — 0.26.1

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in pomerium

CVE-2024-39315 is rated CVSS 5.7 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.