Skip to content

chore: Bump proxy-addr and @fastify/proxy-addr - #8800

Merged
hardillb merged 1 commit into
mainfrom
chore/bump-proxy-addr
Oct 6, 2026
Merged

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

Conversation

@Steve-Mcl

Copy link
Copy Markdown
Contributor

Description

Bumps two lockfile entries to fix CVE-2026-90711 / GHSA-jqcg-44mw-7w3h (critical): an IPv4-mapped IPv6 address could match a trusted subnet it shouldn't, letting a client spoof a trusted proxy.

Package From To Via
proxy-addr 2.0.7 2.0.8 express 4 (mqtt-schema-agent) and express 5 (MCP SDK under nr-assistant)
@fastify/proxy-addr 5.1.0 5.1.1 fastify

The advisory only names proxy-addr, but fastify's fork had the same code and was fixed the same day (fastify/proxy-addr#117), so it is included here.

Both parents ranges already allow the fixed versions, so this is a lockfile-only change. No other package versions move.

Exposure is likely low. Forge uses trustProxy: true, which trusts all proxies and doesn't reach the vulnerable subnet matching. Express only uses it when trust proxy is configured with subnets.

Both releases were published on 2026-09-15, well past the 12 hour minimum. The release notes list the security fix plus CI and housekeeping changes.

Clears https://github.com/FlowFuse/flowfuse/security/code-scanning/295

Related Issue(s)

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
  • Link to Changelog Entry PR, or note why one is not needed.

Labels

  • Includes a DB migration? -> add the area:migration label

proxy-addr 2.0.8 fixes IP spoofing via IPv4-mapped IPv6 trust subnets
(GHSA-jqcg-44mw-7w3h). @fastify/proxy-addr, the fork fastify uses, had
the same bug and was fixed in 5.1.1, but the advisory doesn't list it.
Both parents' ranges already allow the fixed versions, so only the
lockfile changes.

Clears https://github.com/FlowFuse/flowfuse/security/code-scanning/295
@Steve-Mcl Steve-Mcl changed the title chore: Bump proxy-addr and @fastify/proxy-addr for CVE-2026-90711 chore: Bump proxy-addr and @fastify/proxy-addr Oct 6, 2026
@Steve-Mcl
Steve-Mcl requested a review from hardillb October 6, 2026 09:43
@hardillb
hardillb enabled auto-merge (squash) October 6, 2026 09:46
@codecov

codecov Bot commented Oct 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.37%. Comparing base (fe8786f) to head (4d0865d).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8800      +/-   ##
==========================================
- Coverage   78.40%   78.37%   -0.04%     
==========================================
  Files         474      474              
  Lines       25639    25639              
  Branches     6827     6827              
==========================================
- Hits        20103    20095       -8     
- Misses       5536     5544       +8     
Flag Coverage Δ
backend 78.37% <ø> (-0.04%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@hardillb
hardillb merged commit ca183c1 into main Oct 6, 2026
28 of 29 checks passed
@hardillb
hardillb deleted the chore/bump-proxy-addr branch October 6, 2026 10:05

This branch was successfully deployed

1 active deployment
staging — 4d0865d6 Deployed Oct 6, 2026 by hardillb via Remove application #12180
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