Skip to content

fix(deps): bump proxy-addr to 2.0.8 (CVE-2026-90711) - #1250

Closed
Brad-Edwards wants to merge 1 commit into
devfrom
fix/proxy-addr-cve-2026-90711
Closed

Brad-Edwards wants to merge 1 commit into
devfrom
fix/proxy-addr-cve-2026-90711

Conversation

@Brad-Edwards

Copy link
Copy Markdown
Collaborator

Summary

proxy-addr 2.0.7 has CVE-2026-90711 (CRITICAL) — IP spoofing via an IPv4-mapped IPv6 trust subnet (GHSA-jqcg-44mw-7w3h). It is pulled transitively through express in all nine MCP packages. The advisory is newly published, so it fails every CI run today, including the latest push on dev. The required Dependency vulnerability scan, Trivy filesystem scan, and Trivy image scan all report this one finding.

Fix

Bump the resolved proxy-addr to 2.0.8 in each MCP package lockfile (the ^2.0.7 range express declares already admits it; only the locked version moves). No application code changes.

Verification

npm audit --omit=dev --audit-level=high reports found 0 vulnerabilities in the MCP packages after the bump (checked mcp-casemgmt and mcp-red).

Note

This unblocks the security gates for every open PR, not just this one. dev is currently red on the same finding.

proxy-addr 2.0.7 has CRITICAL CVE-2026-90711 (IP spoofing via IPv4-mapped IPv6 trust subnet), pulled transitively through express in all nine MCP packages. Bump the resolved version to 2.0.8 in each package lockfile. npm audit (high+) is clean afterward. This clears the dependency-audit and Trivy critical that currently fails every CI run, including on dev.
@Brad-Edwards

Copy link
Copy Markdown
Collaborator Author

Folded into #1248. The proxy-addr 2.0.8 fix and the node22-base yarn/corepack strip are part of the consolidated PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant