Add warning about crafted regex filter inputs - #10023
Merged
Merged
Conversation
Thanks to @syrull for making the team aware.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the filtering documentation to explicitly warn API authors about denial-of-service risks when enabling regex-based search via the $ (iregex) prefix.
Changes:
- Adds a warning callout about maliciously crafted regular expressions (ReDoS/catastrophic backtracking) when using
$/iregexsearch. - Updates the
$lookup table row to reference the new warning.
馃挕 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
auvipy
approved these changes
Aug 18, 2026
browniebroke
changed the title
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thanks to @syrull for making the team aware.