tarteaucitron.js has Regular Expression Denial of Service (ReDoS) vulnerability
CVE-2026-22809GHSA-q5f6-qxm2-mcqm
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (tarteaucitronjs 1.29.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm tarteaucitronjs
- Affected
- < 1.29.0
- Fixed in
- 1.29.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-q5f6-qxm2-mcqm lists affected ranges: npm tarteaucitronjs >=0 <1.29.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-q5f6-qxm2-mcqm lists affected ranges: npm tarteaucitronjs >=0 <1.29.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.4 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2026-22809: 0.13% estimated exploitation activity in the next 30 days; percentile 2.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary A potential Regular Expression Denial of Service (ReDoS) vulnerability was identified in tarteaucitron.js in the handling of the issuuid parameter. Details The issue was caused by the use of insufficiently constrained regular expressions applied to attacker-controlled input: if (issuuid.match(/\d+\/\d+/)) { issuuembed = '#' + issuuid; } else if (issuuid.match(/d=(.)&u=(.)/)) { issuuembed = '?' + issuuid; } These expressions are not anchored and rely on greedy patterns (.). When evaluated against specially crafted input, they may cause excessive backtracking, leading to high CPU consumption and potential denial of service. Impact An attacker able to control the issuuid parameter could exploit this vulnerability to degrade performance or cause temporary service unavailability through CPU exhaustion. No confidentiality or integrity impact was identified. Fix https://github.com/AmauriC/tarteaucitron.js/commit/f0bbdac2fdf3cd24a325fc0928c0d34abf1b7b52 The logic was simplified and…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-q5f6-qxm2-mcqm
- Revision 1 · created ·
Published from osv record GHSA-q5f6-qxm2-mcqm
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-22809 Advisory: tarteaucitron.js has Regular Expression Denial of Service (ReDoS) vulnerability IDs: CVE-2026-22809, GHSA-q5f6-qxm2-mcqm Record: https://patchnext.com/advisories/cve-2026-22809 (revision 2, source checked 26 Oct 2026, 12:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: tarteaucitronjs 1.29.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm tarteaucitronjs: affected < 1.29.0; fixed in 1.29.0 ## Suggested inspection (read-only) - `npm ls tarteaucitronjs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on tarteaucitronjs. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-q5f6-qxm2-mcqm (OSV record GHSA-q5f6-qxm2-mcqm lists affected ranges: npm tarteaucitronjs >=0 <1.29.0 (fixed)) - Verified: https://github.com/advisories/GHSA-q5f6-qxm2-mcqm (GitHub-reviewed advisory GHSA-q5f6-qxm2-mcqm lists affected ranges: npm tarteaucitronjs >=0 <1.29.0) Commands are suggestions: review each one before running it.
Loading voting…