Skip to content

Update proxy-addr to 2.0.8 to resolve security advisory - #25

Merged
cdbartholomew merged 1 commit into
mainfrom
chore/bump-proxy-addr
Oct 19, 2026
Merged

cdbartholomew merged 1 commit into
mainfrom
chore/bump-proxy-addr

Conversation

@cdbartholomew

Copy link
Copy Markdown
Contributor

Summary

Bumps the transitive proxy-addr dependency from 2.0.7 to 2.0.8 to pick up the fix for CVE-2026-90711. proxy-addr is pulled in transitively via express, so this adds an npm overrides entry and regenerates the lockfile.

Changes

  • Added "proxy-addr": "^2.0.8" to the existing overrides block in package.json.
  • Regenerated package-lock.json (node_modules/proxy-addr now resolves to 2.0.8).

Verification

  • npm ls proxy-addr confirms proxy-addr@2.0.8 overridden resolves everywhere (via express@5.2.1).
  • npm ci installs cleanly from the lockfile.
  • npm run build passes.
  • npm audit --audit-level=critical reports 0 critical vulnerabilities.

Diff is limited to package.json and package-lock.json.

https://claude.ai/code/session_014J7s5yzoVEqoZ8LmnD8bQd

Bump the transitive proxy-addr dependency (pulled in via express) from
2.0.7 to 2.0.8 to pick up the fix for CVE-2026-90711. Added an npm
overrides entry since proxy-addr is not a direct dependency, and
regenerated the lockfile.

npm ls confirms proxy-addr@2.0.8 resolves everywhere, the build passes,
and npm audit reports 0 critical vulnerabilities.

Claude-Session: https://claude.ai/code/session_014J7s5yzoVEqoZ8LmnD8bQd
@cdbartholomew
cdbartholomew merged commit 272e7e5 into main Oct 19, 2026
2 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