How severe is GHSA-hpwf-8g29-85qm?

GHSA-hpwf-8g29-85qm has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-hpwf-8g29-85qm?

GHSA-hpwf-8g29-85qm affects the following packages: @nestjs/microservices (npm). Ecosystems affected: npm.

How do I fix GHSA-hpwf-8g29-85qm?

Update @nestjs/microservices to 11.1.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hpwf-8g29-85qm is resolved across your whole dependency graph.

How do I detect GHSA-hpwf-8g29-85qm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nestjs/microservices. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hpwf-8g29-85qm if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-hpwf-8g29-85qm?

O3 pinpoints whether GHSA-hpwf-8g29-85qm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hpwf-8g29-85qm actively exploited in the wild?

No public exploit code has been indexed for GHSA-hpwf-8g29-85qm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-hpwf-8g29-85qm?

GHSA-hpwf-8g29-85qm is classified as CWE-674 (CWE-674). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hpwf-8g29-85qm published, and has it been updated?

GHSA-hpwf-8g29-85qm was published on April 14, 2026 and was last updated on May 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-hpwf-8g29-85qm

HIGH

GHSA-hpwf-8g29-85qm is a high-severity (CVSS 7.5) CWE-674 vulnerability in @nestjs/microservices. O3 Security confirms whether GHSA-hpwf-8g29-85qm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Nest Affected by DoS via Recursive handleData in JsonSocket (TCP Transport)

Also known asCVE-2026-40879

Published

Apr 14, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@nestjs/microservicesnpm

2.3Mdownloads / week

Description

Impact

Attacker sends many small, valid JSON messages in one TCP frame → handleData() recurses once per message; buffer shrinks each call → maxBufferSize is never reached; call stack overflows instead → A ~47 KB payload is sufficient to trigger RangeError

Patches

Fixed in @nestjs/[email protected]

References

Discovered by https://github.com/hwpark6804-gif

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@nestjs/microservices`	all versions	11.1.19

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nestjs/microservices. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @nestjs/microservices to 11.1.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hpwf-8g29-85qm is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-hpwf-8g29-85qm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hpwf-8g29-85qm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Attacker sends many small, valid JSON messages in one TCP frame → handleData() recurses once per message; buffer shrinks each call → maxBufferSize is never reached; call stack overflows instead → A ~47 KB payload is sufficient to trigger RangeError ### Patches Fixed in `@nestjs/[email protected]` ### References Discovered by https://github.com/hwpark6804-gif

O3 Security · Impact-Aware SCA

Is GHSA-hpwf-8g29-85qm in your dependencies?

O3 detects GHSA-hpwf-8g29-85qm across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works