Is CVE-2026-119202 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-119202 being exploited in the wild.

How severe is CVE-2026-119202?

High severity, with a CVSS score of 7.5, published 29 October 2026.

Which products and versions are affected?

Hapi @Hapi/Content 3.0.6 to 6.0.2; @hapi/content (npm) = 3.0.6, <= 4.0.6, SEMVER:introduced=3.0.6,last_affected=4.0.6.

Is there a fix for CVE-2026-119202?

Yes. @hapi/content (npm): upgrade to 6.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-119202 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-119202?

Check whether you run Hapi @Hapi/Content, @hapi/content (npm) or content (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119202: @hapi/content ReDoS in Content-Disposition parsing

Q: Is there a fix for CVE-2026-119202?

Yes. @hapi/content (npm): upgrade to 6.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-119202 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-119202?

Check whether you run Hapi @Hapi/Content, @hapi/content (npm) or content (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119202 · Severity: high · CVSS 7.5 · Published 2026-10-29

@hapi/content is a library for parsing HTTP headers used by web servers and APIs. When processing multipart form data or Content-Disposition headers containing specially crafted tokens, the library can be forced to perform excessive pattern matching, blocking the application's event loop and denying service to legitimate requests.

Technologies: Hapi @Hapi/Content, @hapi/content (npm). Vendors: Hapi, npm.

Quick answers

Is CVE-2026-119202 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119202 being exploited in the wild.
How severe is CVE-2026-119202?: High severity, with a CVSS score of 7.5, published 29 October 2026.
Which products and versions are affected?: Hapi @Hapi/Content 3.0.6 to 6.0.2; @hapi/content (npm) <= 6.0.2, SEMVER:introduced=0,fixed=6.0.3; content (npm) >= 3.0.6, <= 4.0.6, SEMVER:introduced=3.0.6,last_affected=4.0.6.
Is there a fix for CVE-2026-119202?: Yes. @hapi/content (npm): upgrade to 6.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-119202 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-119202?: Check whether you run Hapi @Hapi/Content, @hapi/content (npm) or content (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@hapi/content (npm): upgrade to 6.0.3 or later
```
npm install @hapi/content@6.0.3
```

Technical details

A regular expression used by Content.disposition() lacks anchoring, causing quadratic processing time when matching Content-Disposition parameter names against input containing long tokens without equals signs. The vulnerability affects unauthenticated hapi web framework routes with payload.multipart enabled and any application passing untrusted headers directly to the Content.disposition() method.

Affected products

hapi @hapi/content 3.0.6 to 6.0.2

Identifiers

CVE-2026-119202
GHSA-8494-f6mr-cjpv

Timeline

2026-10-29: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.