Uh oh!
There was an error while loading. Please reload this page.
[3.13] gh-146333: Fix quadratic regex backtracking in configparser option parsing (GH-146399) - #148559
Conversation
…ser option parsing (pythonGH-146399) Use negative lookahead in option regex to prevent backtracking, and to avoid changing logic outside the regexes (since people could use the regex directly). (cherry picked from commit 7e0a0be) Co-authored-by: Joshua Swanson <22283299+joshuaswanson@users.noreply.github.com>
Uh oh!
There was an error while loading. Please reload this page.
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11, 3.12. |
Sorry, @encukou, I could not cleanly backport this to |
Sorry, @encukou, I could not cleanly backport this to |
Sorry, @encukou, I could not cleanly backport this to |
serhiy-storchaka
commented
Jul 15, 2026
Please don't forget about backports. |
GH-154081 is a backport of this pull request to the 3.12 branch. |
GH-154877 is a backport of this pull request to the 3.11 branch. |
GH-154878 is a backport of this pull request to the 3.10 branch. |
…tion parsing (GH-146399) (GH-148559) (#154081) Use negative lookahead in option regex to prevent backtracking, and to avoid changing logic outside the regexes (since people could use the regex directly). (cherry picked from commit 7e0a0be) (cherry picked from commit a5969e8) Co-authored-by: Joshua Swanson <22283299+joshuaswanson@users.noreply.github.com>
Use negative lookahead in option regex to prevent backtracking, and to avoid changing logic outside the regexes (since people could use the regex directly).
(cherry picked from commit 7e0a0be)
configparser.RawConfigParser.{OPTCRE,OPTCRE_NV}regexes vulnerable to quadratic backtracking #146333