CVE-2026-35213 hapijs CVE debrief

Who should care

Developers and administrators using @hapi/content versions prior to 6.0.1 should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and validating HTTP header values, implementing additional monitoring and logging, and updating to version 6.0.1 or later. Security teams and operators should also be aware of the potential impact on their systems and take steps to protect them.

Technical summary

The @hapi/content library through version 6.0.0 is vulnerable to a Regular Expression Denial of Service (ReDoS) attack due to three regular expressions used for parsing Content-Type and Content-Disposition headers being susceptible to catastrophic backtracking. This can be exploited by providing crafted HTTP header values. The issue has been addressed in version 6.0.1. Developers should review and validate HTTP header values to prevent crafted inputs and implement additional monitoring and logging to detect potential ReDoS attacks.

Defensive priority

High

Recommended defensive actions

• Update @hapi/content to version 6.0.1 or later
• Review and validate HTTP header values to prevent crafted inputs
• Implement additional monitoring and logging to detect potential ReDoS attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-04-06T21:16:20.433Z and was last modified on 2026-07-24T21:10:00.143Z. The NVD entry is currently Analyzed. The @hapi/content library through version 6.0.0 is vulnerable to a Regular Expression Denial of Service (ReDoS) attack due to three regular expressions used for parsing Content-Type and Content-Disposition headers being susceptible to catastrophic backtracking. This can be exploited by providing crafted HTTP header values. The issue has been addressed in version 6.0.1. Evidence limits suggest verifying HTTP header validation and Content-Type parsing.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.