i18next is vulnerable to Regular Expression Denial of Service (ReDoS)
75
CVE Score
High
Regular Expression Denial of Service (ReDoS)
i18next's nesting regular expression backtracks exponentially when interpolated text contains the nesting prefix $t( without a matching closing ). With the default skipOnVariables and escapeValue settings, any value passed to t() as a variable reaches this regexp before the nest option is checked. A short untrusted value blocks the event loop for seconds to hours, leading to a remote denial of service through an ordinary translation call on a Node.js or server rendering process. The fix rewrites the regexp so every alternative starts with a distinct character, removing the overlapping backtracking paths.
Upgrade the i18next library to the patch version.
You are affected if you are using a version that falls within the vulnerable range.
25.3.3 - 26.4.3
Fixed in 26.4.4i18next is vulnerable to Regular Expression Denial of Service (ReDoS) in versions 25.3.3 - 26.4.3.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.