Advisory record · GHSA-pvrc-wvj2-f59p

Pomerium vulnerable to Incorrect Authorization with specially crafted requests

CVSS 10.0 CriticalCriticalEPSS 0.0092 · 61st percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 26 May 2023, 22:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/pomerium/pomeriumGo>=0.22.0, <0.22.2 || >=0.21.0, <0.21.4 || >=0.20.0, <0.20.1 || >=0.19.0, <0.19.2 || >=0.18.0, <0.18.1 || <0.17.40.22.2, 0.21.4, 0.20.1, 0.19.2, 0.18.1, 0.17.4
Identifiers
GHSA-pvrc-wvj2-f59p · CVE-2023-33189 · GO-2023-1800
Weakness (CWE)
CWE-285
Published
26 May 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Pomerium versions before 0.17.4, from 0.18.0 before 0.18.1, from 0.19.0 before 0.19.2, from 0.20.0 before 0.20.1, from 0.21.0 before 0.21.4, and from 0.22.0 before 0.22.2 are vulnerable to incorrect authorization decisions. The source gives few details on what attackers must do, but specially crafted requests can cause Pomerium to make wrong authorization decisions. Upgrade to 0.22.2, 0.21.4, 0.20.1, 0.19.2, 0.18.1, or 0.17.4, matching your release line.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
10.0 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0092, the 61st percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.