NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Incorrect Authorization with specially crafted requestsGHSA-cfc2-wjcm-c8fm

HIGH

GHSA-cfc2-wjcm-c8fm is a high-severity (CVSS 8.6) CWE-863 vulnerability in github.com/pomerium/pomerium. A fix is available for github.com/pomerium/pomerium — see the affected versions and patch details below.

Also known asBIT-envoy-2021-39206CVE-2021-39206
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.00%0.65%1.30%1.96%0.2%1.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹github.com/pomerium/pomerium🐹github.com/pomerium/pomerium

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/pomerium/pomerium≥ 0.11.0&&< 0.14.80.14.8go get github.com/pomerium/pomerium@v0.14.8
🐹Gogithub.com/pomerium/pomerium≥ 0.15.0&&< 0.15.10.15.1go get github.com/pomerium/pomerium@v0.15.1

Affected Products

2 products · 6 configurations
Application
envoyenvoyproxy
≥ 1.18.0 && < 1.18.4
1 version
1.19.0
Application
pomeriumpomerium
≥ 0.11.0 && < 0.14.8
1 version
0.15.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pomerium/pomerium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/pomerium/pomerium to 0.14.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cfc2-wjcm-c8fm is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Envoy, which Pomerium is based on, contains two authorization related vulnerabilities: - [CVE-2021-32777](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32779): incorrectly transform a URL containing a `#fragment` element, causing a mismatch in path-prefix based authorization decisions. - [CVE-2021-32779](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32777): 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 dec
O3 Security · Impact-Aware SCA

Is GHSA-cfc2-wjcm-c8fm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Incorrect Authorization with specially crafted requests