CVE Intelligence
Low Denial of service

CVE-2026-111714 — tarteaucitron.js before 1.37.0 ReDoS via Unescaped Cookie Name in cookie.purge

tarteaucitron.js before 1.37.0 contains a regular expression denial of service vulnerability that allows attackers to block visitor pages by supplying unescaped cookie names to cookie.purge. Attackers can plant a cookie from a sibling subdomain or inject a purgeBtn element with a catastrophic-backtracking data-cookie pattern that freezes the page when the purge button is clicked.

Published Oct 16, 2026 · Updated Oct 16, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
AmauriC
Tarteaucitron.js
CVSS base
3.1
Low · 3 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (AmauriC Tarteaucitron.js).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
AmauriC Tarteaucitron.js < 1.37.0 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
2.3 CVSS 4.0 Low — — disclosure@vulncheck.com via NIST National Vulnerability Database
2.3 CVSS 4.0 Low — — VulnCheck via CVE Program (cve.org) e CISA ADP
3.1 CVSS 3.1 Low 1.6 1.4 disclosure@vulncheck.com via NIST National Vulnerability Database
3.1 CVSS 3.1 Low — — GitHub, Inc. via GitHub Security Advisories
3.1 CVSS 3.1 Low — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-1333 · Inefficient Regular Expression Complexity (ReDoS)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Track CPU/memory spikes and availability drops correlated with request patterns.
web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Published → Awaiting Analysis
    Oct 16, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 16, 2026
  • CVSS changed · 3.1
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 16, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 16, 2026 – Oct 16, 2026
  • 1× Official description updated · Oct 16, 2026 – Oct 16, 2026

References

6 on the record

Elsewhere on this site

AmauriC
every CVE for this vendor
CWE-1333
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-111713 tarteaucitron.js before 1.37.0 XSS via getElemAttr Attribute Validation Mismatch 7h
  • Medium CVE-2026-49977 tarteaucitron.js: data-cookie attribute can be used to delete arbitrary cookies Jul 17, 2026
  • Medium CVE-2026-22809 tarteaucitron.js has Regular Expression Denial of Service (ReDoS) vulnerability Jan 13, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-111714 is "tarteaucitron.js before 1.37.0 ReDoS via Unescaped Cookie Name in cookie.purge", rated Low. It affects Tarteaucitron.js (AmauriC); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.1 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.