# CVE-2026-22809: tarteaucitron.js has Regular Expression Denial of Service (ReDoS) vulnerability

> An attacker can cause a denial of service in tarteaucitron.js by exploiting a Regular Expression Denial of Service vulnerability in the issuu_id parameter.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-q5f6-qxm2-mcqm

## What is CVE-2026-22809?

CVE-2026-22809 is a medium-severity denial of service vulnerability in AmauriC tarteaucitron.js, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

tarteaucitron.js is a compliant and accessible cookie banner. Prior to 1.29.0, a Regular Expression Denial of Service (ReDoS) vulnerability was identified in tarteaucitron.js in the handling of the issuu_id parameter. This vulnerability is fixed in 1.29.0.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-22809?

2 open source packages ship an affected version, including tarteaucitronjs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tarteaucitronjs` | npm | All versions | 1.29.0 |
| `tarteaucitronjs` | npm | All versions | 1.29.0 |

Products: Amauri Tarteaucitronjs.

## How do I fix CVE-2026-22809?

Upgrade tarteaucitronjs to 1.29.0 or later.

## Is CVE-2026-22809 being exploited?

There is no known exploitation of CVE-2026-22809 in the wild and no public exploit code.

## Other vulnerabilities in AmauriC tarteaucitron.js

- [CVE-2025-31138](https://insights.sbomify.com/CVE-2025-31138/): tarteaucitron.js allows UI manipulation via unrestricted CSS injection (medium 5.5)
- [CVE-2025-31475](https://insights.sbomify.com/CVE-2025-31475/): tarteaucitron.js allows prototype pollution via custom text injection (medium 5.5)
- [CVE-2025-31476](https://insights.sbomify.com/CVE-2025-31476/): tarteaucitron.js allows url scheme injection via unfiltered inputs (medium 4.8)
- [CVE-2025-48939](https://insights.sbomify.com/CVE-2025-48939/): tarteaucitron.js vulnerable to DOM Clobbering via document.currentScript (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22809 and fix it if it is affected.

What it is: CVE-2026-22809 is a medium-severity denial of service vulnerability in AmauriC tarteaucitron.js, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22809 in the wild and no public exploit code.

Affected packages and fixed versions:
- tarteaucitronjs (npm): affected all versions; fixed in 1.29.0
- tarteaucitronjs (npm): affected all versions; fixed in 1.29.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22809/ (Markdown: https://insights.sbomify.com/CVE-2026-22809/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22809
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22809
- OSV: https://osv.dev/vulnerability/CVE-2026-22809

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22809/
Summaries are generated and may contain mistakes; the official description above is the record.