GHSA-mrwp-f3q8-3g9p

follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects

High highest severity reported · also known as CVE-2026-116689

5
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.3%
EPSS for CVE-2026-116689, percentile 19

Catalog tools matching GHSA-mrwp-f3q8-3g9p

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
infisical
Secret Management
v0.167.4follow-redirects@1.16.0
npm
1.16.2not analyzedsink/oidc-server/package-lock.jsonDispute
KubeStellar Console
Kubernetes Security
v0.3.42follow-redirects@1.16.0
npm
1.16.2not analyzedweb/package-lock.jsonDispute
gatekeeper
Policy as Code
v3.23.1follow-redirects@1.16.0
npm
1.16.2not analyzedwebsite/yarn.lockDispute
vet
Software Composition Analysis (SCA)
v1.20.0follow-redirects@1.16.0
npm
1.16.2not analyzedpnpm-lock.yamlDispute
cloudsplaining
Cloud Security
0.9.1follow-redirects@1.16.0
npm
1.16.2not analyzedpackage-lock.jsonDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-mrwp-f3q8-3g9p · NVD CVE-2026-116689 · OSV GHSA-mrwp-f3q8-3g9p

Grype data sources: https://github.com/advisories/GHSA-mrwp-f3q8-3g9p