HighGHSA-cfc2-wjcm-c8fmBIT-envoy-2021-39206CVE-2021-39206

Incorrect Authorization with specially crafted requests

Published 10 Sept 2021 · Updated 4 Feb 2026

Is your project on an affected github.com/pomerium/pomerium?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=0.11.0 <0.14.8
Fixed in
0.14.8
Update to the fixed version for your release line, for example:go get github.com/pomerium/pomerium@v0.14.8
Affected
>=0.15.0 <0.15.1
Fixed in
0.15.1
Update to the fixed version for your release line, for example:go get github.com/pomerium/pomerium@v0.15.1

Details

Envoy, which Pomerium is based on, contains two authorization related vulnerabilities:

  • CVE-2021-32777: incorrectly transform a URL containing a #fragment element, causing a mismatch in path-prefix based authorization decisions.
  • CVE-2021-32779: incorrectly handle duplicate headers, dropping all but the last. This may lead to incorrect routing or authorization policy decisions.

Impact

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

Patches

Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched.

Workarounds

  • This issue can only be triggered when using path prefix based policy. Removing any such policies should provide mitigation.

References

envoy GSA CVE-2021-32777 envoy GSA CVE-2021-32779 envoy announcement

For more information

If you have any questions or comments about this advisory:

  • Open an issue in pomerium/pomerium
  • Email us at [security@pomerium.com](mailto:security@pomerium.com)

Is GHSA-cfc2-wjcm-c8fm in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/pomerium/pomerium, and gives you the command that fixes it.

More advisories for github.com/pomerium/pomerium

  • HighCVE-2026-50285Pomerium Pre-Auth Memory Exhaustion via Unbounded zstd Decompression in HPKE Callback · 15 Jul 2026
  • LowCVE-2024-47616Pomerium service account access token may grant unintended access to databroker API in github.com/pomerium/pomerium · 9 Oct 2024
  • HighCVE-2024-47616Pomerium service account access token may grant unintended access to databroker API · 2 Oct 2024
  • MediumCVE-2022-24797Exposure of debug and metrics endpoints in Pomerium · 6 Sept 2024
  • LowCVE-2021-39162Incorrect handling of H2 GOAWAY + SETTINGS frames in github.com/pomerium/pomerium · 21 Aug 2024
  • LowCVE-2021-29652pomerium_signature is not verified in middleware in github.com/pomerium/pomerium · 21 Aug 2024
All 20 advisories for github.com/pomerium/pomerium

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.