Skip to content

fix: refresh proxy-addr for GHSA-jqcg-44mw-7w3h - #25

Merged
SergioTCG merged 1 commit into
mainfrom
fix/proxy-addr-advisory
Oct 6, 2026
Merged

SergioTCG merged 1 commit into
mainfrom
fix/proxy-addr-advisory

Conversation

@SergioTCG

Copy link
Copy Markdown
Owner

Summary

npm audit --omit=dev fails CI on every run, main included, because of a newly published critical advisory: GHSA-jqcg-44mw-7w3h.

  • What: proxy-addr 2.0.7 is vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnets.
  • How SAB gets it: transitively, @modelcontextprotocol/sdk → express → proxy-addr.

This lockfile-only refresh moves proxy-addr to the patched 2.0.8, like #20.

Runtime exposure: none. SAB never imports express: the MCP channel uses the stdio transport. The fix is still needed to unblock CI for #23 and #24.

Validation

  • npm audit --omit=dev: 0 vulnerabilities.
  • npm test: 548 pass, 0 fail.
  • npm run check: pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_011Xs8AVBVrTGfpzUMiCQp2R

npm audit now reports a critical advisory for proxy-addr 2.0.7, reached
through @modelcontextprotocol/sdk > express. Because of it, CI's
production-dependency audit fails on every run, including main.

proxy-addr 2.0.8 is the patched release. This is a lockfile-only change.
SAB never imports express: its MCP channel uses the stdio transport, so
the vulnerable code path was not loaded at runtime.

Validated: npm audit reports 0 vulnerabilities, npm test passes (548),
and npm run check passes.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011Xs8AVBVrTGfpzUMiCQp2R
@SergioTCG
SergioTCG merged commit 84a6b09 into main Oct 6, 2026
3 checks passed
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.

2 participants