NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2023-37899 — @feathersjs/socketio

HIGHFix: feathersjs/feathers#3241

CVE-2023-37899 is a high-severity (CVSS 7.5) CWE-754 vulnerability in @feathersjs/socketio. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @feathersjs/socketio — see the affected versions and patch details below.

feathersjs socket handler allows abusing implicit toString

Also known asGHSA-hhr9-rh25-hvf9
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known
Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-37899.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.00%0.56%1.13%1.69%0.2%1.2%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

105other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@feathersjs/socketionpm
23Kdownloads / week
@feathersjs/transport-commonsnpm
44Kdownloads / week

Description

Impact

Feathers socket handler did not catch invalid string conversion errors like:

const message = `${{ toString: '' }}`

Causing the NodeJS process to crash when sending an unexpected Socket.io message like

socket.emit('find', { toString: '' })

Patches

A fix has been released in

  • v5.0.8 via #3241
  • v4.5.18 via #3242

Workarounds

Since it is in the core Socket handling code upgrading to the latest version is necessary.

References

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npm@feathersjs/socketioall versions4.5.18npm install @feathersjs/socketio@4.5.18
📦npm@feathersjs/socketio≥ 5.0.0&&< 5.0.85.0.8npm install @feathersjs/socketio@5.0.8
📦npm@feathersjs/transport-commonsall versions4.5.18npm install @feathersjs/transport-commons@4.5.18
📦npm@feathersjs/transport-commons≥ 5.0.0&&< 5.0.85.0.8npm install @feathersjs/transport-commons@5.0.8

Affected Products

1 product · 2 configurations
Application
feathersfeathersjs
≥ 5.0.0 && < 5.0.8
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @feathersjs/socketio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @feathersjs/socketio to 4.5.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-37899 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Feathers socket handler did not catch invalid string conversion errors like: ```ts const message = `${{ toString: '' }}` ``` Causing the NodeJS process to crash when sending an unexpected Socket.io message like ```ts socket.emit('find', { toString: '' }) ``` ### Patches A fix has been released in - `v5.0.8` via #3241 - `v4.5.18` via #3242 ### Workarounds Since it is in the core Socket handling code upgrading to the latest version is necessary. ### References - [v5.0.8 Changelog](https://github.com/feathersjs/feathers/blob/dove/CHANGELOG.md#508-2023-07-19) - [v4.5.18 Change
O3 Security · Impact-Aware SCA

Is CVE-2023-37899 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2023-37899: @feathersjs/socketio — Fixed in 4.5.18