CVE-2021-41230

What it is

Pomerium is an open source identity-aware access proxy. In affected versions changes to the OIDC claims of a user after initial login are not reflected in policy evaluation when using `allowed_idp_claims` as part of policy. If using `allowed_idp_claims` and a user's claims are changed, Pomerium can make incorrect authorization decisions. This issue has been resolved in v0.15.6. For users unable to upgrade clear data on `databroker` service by clearing redis or restarting the in-memory databroker to force claims to be updated.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure.

Exploit odds

0.9% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2021-11-05 23:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:08 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.9% in the next 30 days (EPSS).
• Severity: 5.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2021-11-05 23:15 UTC

Last modified

2026-06-17 04:08 UTC

Exploit probability

0.9% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Modified

Affected

• Pomerium < 0.15.6

Attack profile CVSS 3.1 · 5.3

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2021-41230.md and follow it. Check whether this project is affected by CVE-2021-41230. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge