Skip to content
Fencer Intel
high 8.6

CVE-2021-39206 json

Incorrect Authorization with specially crafted requests

published 5y ago modified 2mo ago also BIT-envoy-2021-39206 , EUVD-2021-2038 , GHSA-cfc2-wjcm-c8fm

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

Pomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, contains two authorization related vulnerabilities CVE-2021-32777 and CVE-2021-32779. This may lead to incorrect routing or authorization policy decisions. With specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium. Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched. This issue can only be triggered when using path prefix based policy. Removing any such policies should provide mitigation.

Patch / fix

  • go github.com/pomerium/pomerium 0.14.8, 0.15.1
  • bitnami envoy 1.16.5, 1.17.4, 1.18.4, 1.19.1
  • envoyproxy envoy 1.16.5, 1.17.4, 1.18.4
  • pomerium pomerium 0.14.8

Is CVE-2021-39206 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.46% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
OSV 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/pomerium/pomerium
>=0.11.0, <0.14.8
>=0.15.0, <0.15.1
0.14.8
0.15.1
bitnami envoy
<1.16.5
>=1.17.0, <1.17.4
>=1.18.0, <1.18.4
>=1.19.0, <1.19.1
1.16.5
1.17.4
1.18.4
1.19.1

Affected products

  • pomerium pomerium

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.