LiveActive security incident?Get immediate response
CVE Record

CVE-2023-26136: Versions of the package tough-cookie before 4.1.3 are vulnerable to Prototype Pollution due to improper han...

Versions of the package tough-cookie before 4.1.3 are vulnerable to Prototype Pollution due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode. This issue arises from the manner in which the objects are initialized.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-26136 affects the Node.js tough-cookie package before 4.1.3. In a specific CookieJar mode, malicious cookie handling can pollute JavaScript object prototypes, potentially changing application behavior or exposing limited data. Treat this as moderate priority unless the vulnerable mode is used in exposed request-processing paths.

Executive priority

Prioritize remediation in internet-facing Node.js services and products that process untrusted cookies. For internal systems without the risky CookieJar setting, handle through normal dependency patching cycles.

Technical view

The issue is prototype pollution in tough-cookie CookieJar when rejectPublicSuffixes=false. The CVSS vector indicates network reachability, low attack complexity, no privileges, and no user interaction, with low confidentiality and integrity impact. The fixed upstream version is 4.1.3.

Likely exposure

Most likely exposure is Node.js applications or transitive dependencies using tough-cookie versions before 4.1.3, especially where CookieJar is configured with rejectPublicSuffixes=false. Distribution and vendor advisories suggest downstream packaged exposure should also be checked.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The supplied CVSS vector includes E:P, suggesting proof-of-concept maturity, but no source here supports real-world exploitation claims.

Researcher notes

Focus review on object initialization and cookie parsing flows involving CookieJar with public suffix rejection disabled. Evidence is sufficient for affected version and fix direction, but incomplete for active exploitation or product-specific blast radius.

Mitigation direction

  • Upgrade tough-cookie to version 4.1.3 or later.
  • Review package-lock, yarn.lock, pnpm-lock, and SBOMs for transitive vulnerable versions.
  • Avoid rejectPublicSuffixes=false unless business logic requires it.
  • Apply Debian, Fedora, NetApp, or other vendor updates where tough-cookie is bundled.
  • Monitor upstream tough-cookie and vendor advisories for additional guidance.

Validation and detection

  • Confirm runtime dependency resolution loads tough-cookie 4.1.3 or later.
  • Search code for CookieJar configurations using rejectPublicSuffixes=false.
  • Run software composition analysis against production dependency manifests.
  • Check container images and OS packages for bundled vulnerable tough-cookie versions.
  • Verify remediation in deployed artifacts, not only source repositories.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-26136 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2023-26136Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/atough-cookie0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1321 · source CWE mapping

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.