MediumGHSA-pf59-j7c2-rh6xCVE-2020-13597

Exposure of Sensitive Information to an Unauthorized Actor and Insertion of Sensitive Information Into Sent Data in Calico

Published 15 Feb 2022 · Updated 7 Aug 2026

Is your project on an affected github.com/projectcalico/calico?

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
>=3.14.0 <3.14.1
Fixed in
3.14.1
Update to the fixed version for your release line, for example:go get github.com/projectcalico/calico@v3.14.1
Affected
>=3.13.0 <3.13.4
Fixed in
3.13.4
Update to the fixed version for your release line, for example:go get github.com/projectcalico/calico@v3.13.4
Affected
>=3.12.0 <3.12.2
Fixed in
3.12.2
Update to the fixed version for your release line, for example:go get github.com/projectcalico/calico@v3.12.2
Affected
>=3.11.0 <3.11.3
Fixed in
3.11.3
Update to the fixed version for your release line, for example:go get github.com/projectcalico/calico@v3.11.3
Affected
>=3.10.0 <3.10.4
Fixed in
3.10.4
Update to the fixed version for your release line, for example:go get github.com/projectcalico/calico@v3.10.4
Affected
>=3.9.0 <3.9.6
Fixed in
3.9.6
Update to the fixed version for your release line, for example:go get github.com/projectcalico/calico@v3.9.6
Affected
<3.8.9
Fixed in
3.8.9
Update to the fixed version for your release line, for example:go get github.com/projectcalico/calico@v3.8.9

Details

Clusters using Calico (version 3.14.0 and below), Calico Enterprise (version 2.8.2 and below), may be vulnerable to information disclosure if IPv6 is enabled but unused. A compromised pod with sufficient privilege is able to reconfigure the node’s IPv6 interface due to the node accepting route advertisement by default, allowing the attacker to redirect full or partial network traffic from the node to the compromised pod.

Is GHSA-pf59-j7c2-rh6x 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/projectcalico/calico, and gives you the command that fixes it.

More advisories for github.com/projectcalico/calico

  • LowCVE-2026-41184Calico Inserts Sensitive Information into Log File in github.com/projectcalico/calico · 7 Jul 2026
  • LowCVE-2026-41185Calico Inserts Sensitive Information into Log File in github.com/projectcalico/calico · 7 Jul 2026
  • MediumCVE-2026-41184Calico Inserts Sensitive Information into Log File · 28 May 2026
  • MediumCVE-2026-41185Calico Inserts Sensitive Information into Log File · 28 May 2026
  • LowCVE-2024-33522Calico privilege escalation vulnerability in github.com/projectcalico/calico · 10 Jun 2024
  • HighCVE-2024-33522Calico privilege escalation vulnerability · 30 Apr 2024
All 9 advisories for github.com/projectcalico/calico

References

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