WhatsApp bridge body-parser version pin security concern
Cluster 112382 · gateway. Data as of
1 open item. Fix merged in #113153 on 17 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113153. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113153. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These issues and PRs center on a specific npm dependency override in the WhatsApp bridge, where pinning body-parser to a particular version was flagged as leaving moderate security advisories unaddressed. The discussion involves adjusting the pinned version to move outside the affected advisory range.
Open issues0
Open PRs1
- PR#112398fix(sec): stop pinning WhatsApp body-parser to a stale advisory range
Fixes on record
-
#113153 fix(whatsapp-bridge): npm audit is clean — body-parser override moves off the advisory range (#112382, salvage #112383)
files:
scripts/whatsapp-bridge/package.json
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#112383 fix(whatsapp-bridge): bump body-parser override pin to 1.20.8 (fixes #112382) · superseded by another PR →
#113153,#112382
Closed issues · 1
- Closed#112382[Bug]: WhatsApp bridge `body-parser` override pins a vulnerable version (1.20.6) — 3 moderate npm advisories survive, including a transitive qs CVE
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #113153
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 17 Sep 2026