CVE-2024-39315: Pomerium is an identity and context-aware access proxy

Q: How do I fix CVE-2024-39315?

pomerium: upgrade to 0.26.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-39315 being exploited?

CVE-2024-39315 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-39315 affect?

CVE-2024-39315 affects pomerium. Severity is medium (CVSS 5.7). Pomerium is an identity and context-aware access proxy. Prior to version 0.26.1, the Pomerium user info page (at `/.pomerium`) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens a

Q: How urgent is CVE-2024-39315?

Priority 29/100. No elevated risk signals yet.

Routine

MEDIUM 5.7UPGRADE

CVE-2024-39315 is a medium-severity flaw (CVSS 5.7) affecting pomerium. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Pomerium is an identity and context-aware access proxy. Prior to version 0.26.1, 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 a cross-site scripting vulnerability in an upstream application proxied through Pomerium. If an attacker could insert

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.7 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-201
Published	2024-07-02
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: pomerium

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-07-02 20:15 UTCPublished CVE record published
2026-06-17 07:41 UTCUpdated Record last modified

pomerium pomerium UPGRADE

Affected: < 0.26.1

Fixed in: 0.26.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pomerium || rpm -q pomerium || pomerium --version

2. UPGRADE to 0.26.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pomerium

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pomerium

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-39315?

pomerium: upgrade to 0.26.1. Exact commands for each OS are on this page.

Is CVE-2024-39315 being exploited?

CVE-2024-39315 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-39315 affect?

CVE-2024-39315 affects pomerium. Severity is medium (CVSS 5.7). Pomerium is an identity and context-aware access proxy. Prior to version 0.26.1, the Pomerium user info page (at `/.pomerium`) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens a

How urgent is CVE-2024-39315?

Priority 29/100. No elevated risk signals yet.

References

← Back to latest CVEs