Uh oh!
There was an error while loading. Please reload this page.
fix: protect regex from redos - #38
Merged
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
gsoldevila added a commit
to elastic/kibana
that referenced
this pull request
Apr 21, 2026
…ent (#264077) ## Summary Fixes CVE-2026-35213 — a Regular Expression Denial of Service (ReDoS) vulnerability in `@hapi/content@6.0.0` which is a transitive dependency of `@hapi/hapi` (Kibana's HTTP server framework). Upgrades `@hapi/hapi` from `21.4.4` to `21.4.8`, which cascades into patching the full vulnerable dependency chain: | Package | Before | After | Role | |---|---|---|---| | `@hapi/hapi` | `21.4.4` | `21.4.8` | Direct dependency (HTTP server) | | `@hapi/subtext` | `8.1.1` | `8.1.2` | Request body parsing (requires `@hapi/content ^6.0.1`) | | `@hapi/pez` | `6.1.0` | `6.1.1` | Multipart form parsing (requires `@hapi/content ^6.0.1`) | | `@hapi/content` | `6.0.0` | `6.0.1` | **Vulnerable package — contains the fix** | ### Vulnerability Details `@hapi/content@6.0.0` has a ReDoS vulnerability in its `Content-Type` header parsing regex. A maliciously crafted `Content-Type` header sent to any Kibana HTTP endpoint could cause catastrophic backtracking, exhausting CPU and causing a denial of service. No authentication is required to exploit this. - **CVE:** CVE-2026-35213 - **Severity:** High - **Fix:** Upgrade `@hapi/content` to `6.0.1` ([upstream commit](hapijs/content@ac9a2de), [upstream PR](hapijs/content#38)) - **Tracking issue:** elastic/security#9673 ### Impact Assessment All network-accessible Kibana deployments running `@hapi/content@6.0.0` are potentially affected. The exploit requires no privileges and targets the HTTP layer. ## Test plan - [ ] CI passes — confirms the hapi version bump has no regressions in Kibana's HTTP layer, routing, and request handling - [ ] Confirm `yarn.lock` no longer contains `@hapi/content@6.0.0` after bootstrap Made with [Cursor](https://cursor.com)
patrykkopycinski pushed a commit
to patrykkopycinski/kibana
that referenced
this pull request
Aug 5, 2026
…ent (elastic#264077) ## Summary Fixes CVE-2026-35213 — a Regular Expression Denial of Service (ReDoS) vulnerability in `@hapi/content@6.0.0` which is a transitive dependency of `@hapi/hapi` (Kibana's HTTP server framework). Upgrades `@hapi/hapi` from `21.4.4` to `21.4.8`, which cascades into patching the full vulnerable dependency chain: | Package | Before | After | Role | |---|---|---|---| | `@hapi/hapi` | `21.4.4` | `21.4.8` | Direct dependency (HTTP server) | | `@hapi/subtext` | `8.1.1` | `8.1.2` | Request body parsing (requires `@hapi/content ^6.0.1`) | | `@hapi/pez` | `6.1.0` | `6.1.1` | Multipart form parsing (requires `@hapi/content ^6.0.1`) | | `@hapi/content` | `6.0.0` | `6.0.1` | **Vulnerable package — contains the fix** | ### Vulnerability Details `@hapi/content@6.0.0` has a ReDoS vulnerability in its `Content-Type` header parsing regex. A maliciously crafted `Content-Type` header sent to any Kibana HTTP endpoint could cause catastrophic backtracking, exhausting CPU and causing a denial of service. No authentication is required to exploit this. - **CVE:** CVE-2026-35213 - **Severity:** High - **Fix:** Upgrade `@hapi/content` to `6.0.1` ([upstream commit](hapijs/content@ac9a2de), [upstream PR](hapijs/content#38)) - **Tracking issue:** elastic/security#9673 ### Impact Assessment All network-accessible Kibana deployments running `@hapi/content@6.0.0` are potentially affected. The exploit requires no privileges and targets the HTTP layer. ## Test plan - [ ] CI passes — confirms the hapi version bump has no regressions in Kibana's HTTP layer, routing, and request handling - [ ] Confirm `yarn.lock` no longer contains `@hapi/content@6.0.0` after bootstrap Made with [Cursor](https://cursor.com)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.