What is CVE-2023-33189?

CVE-2023-33189 is a critical-severity security vulnerability in github.com/pomerium/pomerium (go), affecting versions >= 0.22.0, < 0.22.2. It is fixed in 0.22.2, 0.21.4, 0.20.1, 0.19.2, 0.18.1, 0.17.4.

How severe is CVE-2023-33189?

CVE-2023-33189 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/pomerium/pomerium are affected by CVE-2023-33189?

github.com/pomerium/pomerium (go) versions >= 0.22.0, < 0.22.2 is affected.

Is there a fix for CVE-2023-33189?

Yes. CVE-2023-33189 is fixed in 0.22.2, 0.21.4, 0.20.1, 0.19.2, 0.18.1, 0.17.4. Upgrade to this version or later.

Is CVE-2023-33189 exploitable, and should I be worried?

Whether CVE-2023-33189 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-33189 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-33189?

Upgrade: github.com/pomerium/pomerium to 0.22.2 or later, github.com/pomerium/pomerium to 0.21.4 or later, github.com/pomerium/pomerium to 0.20.1 or later, github.com/pomerium/pomerium to 0.19.2 or later, github.com/pomerium/pomerium to 0.18.1 or later, github.com/pomerium/pomerium to 0.17.4 or later.

CVE-2023-33189 in github.com/pomerium/pomerium

Q: How severe is CVE-2023-33189?

CVE-2023-33189 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/pomerium/pomerium are affected by CVE-2023-33189?

github.com/pomerium/pomerium (go) versions >= 0.22.0, < 0.22.2 is affected.

Q: Is there a fix for CVE-2023-33189?

Yes. CVE-2023-33189 is fixed in 0.22.2, 0.21.4, 0.20.1, 0.19.2, 0.18.1, 0.17.4. Upgrade to this version or later.

Q: Is CVE-2023-33189 exploitable, and should I be worried?

Whether CVE-2023-33189 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-33189 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-33189?

Upgrade: github.com/pomerium/pomerium to 0.22.2 or later, github.com/pomerium/pomerium to 0.21.4 or later, github.com/pomerium/pomerium to 0.20.1 or later, github.com/pomerium/pomerium to 0.19.2 or later, github.com/pomerium/pomerium to 0.18.1 or later, github.com/pomerium/pomerium to 0.17.4 or later.

Summary

Pomerium vulnerable to Incorrect Authorization with specially crafted requests

For more information

If you have any questions or comments about this advisory:

Open an issue in pomerium/pomerium
Email us at [email protected]

Impact

With specially crafted requests, incorrect authorization decisions may be made by Pomerium.

CVE-2023-33189 has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.22.2, 0.21.4, 0.20.1, 0.19.2, 0.18.1, 0.17.4); upgrading removes the vulnerable code path.

Affected versions

github.com/pomerium/pomerium (>= 0.22.0, < 0.22.2) github.com/pomerium/pomerium (>= 0.21.0, < 0.21.4) github.com/pomerium/pomerium (>= 0.20.0, < 0.20.1) github.com/pomerium/pomerium (>= 0.19.0, < 0.19.2) github.com/pomerium/pomerium (>= 0.18.0, < 0.18.1) github.com/pomerium/pomerium (< 0.17.4)

Security releases

github.com/pomerium/pomerium → 0.22.2 (go) github.com/pomerium/pomerium → 0.21.4 (go) github.com/pomerium/pomerium → 0.20.1 (go) github.com/pomerium/pomerium → 0.19.2 (go) github.com/pomerium/pomerium → 0.18.1 (go) github.com/pomerium/pomerium → 0.17.4 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

We are releasing patch fixes to address this vulnerability going back to v0.17.X. Please upgrade to:

v0.22.2
v0.21.4
v0.20.1
v0.19.2
v0.18.1
v0.17.4

Frequently Asked Questions

What is CVE-2023-33189? CVE-2023-33189 is a critical-severity security vulnerability in github.com/pomerium/pomerium (go), affecting versions >= 0.22.0, < 0.22.2. It is fixed in 0.22.2, 0.21.4, 0.20.1, 0.19.2, 0.18.1, 0.17.4.
How severe is CVE-2023-33189? CVE-2023-33189 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/pomerium/pomerium are affected by CVE-2023-33189? github.com/pomerium/pomerium (go) versions >= 0.22.0, < 0.22.2 is affected.
Is there a fix for CVE-2023-33189? Yes. CVE-2023-33189 is fixed in 0.22.2, 0.21.4, 0.20.1, 0.19.2, 0.18.1, 0.17.4. Upgrade to this version or later.
Is CVE-2023-33189 exploitable, and should I be worried? Whether CVE-2023-33189 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-33189 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-33189?
- Upgrade github.com/pomerium/pomerium to 0.22.2 or later
- Upgrade github.com/pomerium/pomerium to 0.21.4 or later
- Upgrade github.com/pomerium/pomerium to 0.20.1 or later
- Upgrade github.com/pomerium/pomerium to 0.19.2 or later
- Upgrade github.com/pomerium/pomerium to 0.18.1 or later
- Upgrade github.com/pomerium/pomerium to 0.17.4 or later

Other vulnerabilities in github.com/pomerium/pomerium

CVE-IDSeverityPackage summary

CVE-2024-47616Highgithub.com/pomerium/pomerium: Pomerium service account access token may grant unintended access to databroker API CVE-2022-24797Mediumgithub.com/pomerium/pomerium: Exposure of debug and metrics endpoints in Pomerium CVE-2024-39315Mediumgithub.com/pomerium/pomerium: Pomerium exposed OAuth2 access and ID tokens in user info endpoint response GHSA-J34V-3552-5R7JMediumgithub.com/pomerium/pomerium: Multiple security issues in Pomerium's embedded envoy CVE-2021-41230Mediumgithub.com/pomerium/pomerium: OIDC claims not updated from Identity Provider in Pomerium