chore(deps): update dependency http-proxy-middleware to v3.0.6 [security] - #454
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency http-proxy-middleware to v3.0.6 [security]#454renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-http-proxy-middleware-vulnerability
branch
from
August 10, 2025 14:02
cee7373 to
d408aaa
Compare
renovate
Bot
force-pushed
the
renovate/npm-http-proxy-middleware-vulnerability
branch
from
September 25, 2025 15:11
d408aaa to
be32386
Compare
renovate
Bot
force-pushed
the
renovate/npm-http-proxy-middleware-vulnerability
branch
from
November 10, 2025 19:02
be32386 to
530757f
Compare
renovate
Bot
force-pushed
the
renovate/npm-http-proxy-middleware-vulnerability
branch
2 times, most recently
from
December 31, 2025 19:37
e4b6d53 to
292c219
Compare
renovate
Bot
deleted the
renovate/npm-http-proxy-middleware-vulnerability
branch
March 27, 2026 01:40
renovate
Bot
force-pushed
the
renovate/npm-http-proxy-middleware-vulnerability
branch
from
March 30, 2026 18:33
292c219 to
40e5d1f
Compare
renovate
Bot
force-pushed
the
renovate/npm-http-proxy-middleware-vulnerability
branch
2 times, most recently
from
April 27, 2026 21:41
40e5d1f to
a4ef608
Compare
renovate
Bot
force-pushed
the
renovate/npm-http-proxy-middleware-vulnerability
branch
from
August 26, 2026 20:15
a4ef608 to
4865ea5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.0.0→3.0.6Warning
Some dependencies could not be looked up. Check the warning logs for more information.
@coderabbitai: ignore
http-proxy-middleware can call writeBody twice because "else if" is not used
CVE-2025-32996 / GHSA-4www-5p9h-95mh
More information
Details
In http-proxy-middleware before 2.0.8 and 3.x before 3.0.4, writeBody can be called twice because "else if" is not used.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
http-proxy-middleware
routerhost+path substring matching allows Host-header-driven backend routing bypassCVE-2026-55602 / GHSA-64mm-vxmg-q3vj
More information
Details
Summary
http-proxy-middlewaredocumentsrouterproxy-table entries as host, path, or host+path selectors, but the host+path implementation uses unanchored substring matching on attacker-controlled request metadata. As a result, a craftedHostheader that is only a superstring match for a configured host+path key can still route a request to an unintended backend.Details
Tested code state:
v4.0.0-beta.5339f09ede860197807d4fd99ed9020fa5d0bd358Relevant code locations:
src/router.tssrc/http-proxy-middleware.tsAffected public API:
createProxyMiddleware({ router: { 'host/path': 'http://target' } })Code explanation:
When a proxy-table router key contains
/,getTargetFromProxyTable()concatenates attacker-controlledreq.headers.hostandreq.urlinto a singlehostAndPathstring, then accepts the route if:That is a substring test, not an exact host match plus intended path match. In the validated PoC, the configured router key is:
but the attacker-controlled host is:
and the request path is:
The concatenated attacker-controlled string:
still contains the configured router key as a substring, so the middleware selects the alternate backend even though the host is not equal to the configured host.
Exploit path:
routerfeature with at least one host+path ruleHostheaderHttpProxyMiddleware.prepareProxyRequest()applies router selection before proxyinggetTargetFromProxyTable()accepts the craftedHost + pathstring through substring matchingPoC
Create these files in the same working directory and run:
File:
run.shFile:
DockerfileFile:
verify.mjsThis PoC starts:
DEFAULTSECRETIt then sends:
/apiwithHost: safe.example:3000/apiwithHost: evillocalhost:3000Observed result from the validated PoC:
STEP baseline-route body=DEFAULTSTEP crafted-route body=SECRETRESULT reproduced host_header_injection router substring match bypassThe PoC is considered successful only if:
Impact
This is a backend-selection integrity issue in a documented library feature. Applications that use host+path router-table rules for backend segmentation, tenant routing, or separation of public and more sensitive upstreams can have that routing boundary bypassed by an unauthenticated external client using an ordinary crafted
Hostheader.Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
chimurai/http-proxy-middleware (http-proxy-middleware)
v3.0.6Compare Source
What's Changed
node:protocol imports by @chimurai in #1127New Contributors
Full Changelog: chimurai/http-proxy-middleware@v3.0.5...v3.0.6
v3.0.5Compare Source
v3.0.4Compare Source
v3.0.3Compare Source
v3.0.2Compare Source
v3.0.1Compare Source
Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.