On this page (7 sections)

Ubuntu published USN-9080-1 on 12 November 2026. It covers node-tough-cookie, the Ubuntu package of the tough-cookie library, which implements RFC 6265 cookies and a cookie jar for Node.js. The notice describes a prototype pollution weakness that can be triggered by specially crafted cookies when a specific option is turned off.

If you run Node.js applications that handle cookies on Ubuntu 18.04, 20.04 or 22.04, or you ship tough-cookie as an npm dependency, this is worth a quick check. The fixed Ubuntu packages are only available through Ubuntu Pro, so the first question is whether your systems have access to ESM Apps.

What Ubuntu says happened

According to the notice, tough-cookie incorrectly handled cookies when the rejectPublicSuffixes option was disabled, leading to prototype pollution. Ubuntu says an attacker could possibly use this to change the behavior of applications that use the library, resulting in a denial of service or another unspecified impact. The overview summarizes it as the library being made to modify application data if it receives specially crafted cookies.

The notice references CVE-2023-26136. The research for this story does not include the CVE record itself, a CVSS score or any statement about exploitation in the wild, so this article does not assign a severity. Only one publisher, Ubuntu, is covered so far, and anything beyond its wording should be treated as unconfirmed.

Prototype pollution in plain terms

In JavaScript, most objects inherit properties from a shared prototype. Prototype pollution happens when attacker-controlled input is able to write into that shared prototype instead of into a normal object. Every object in the application can then appear to have a property the attacker chose.

The effect depends entirely on how the application reads its objects afterwards. Typical outcomes are crashes (denial of service), changed defaults or skipped checks. Ubuntu describes the impact here as a possible denial of service or another unspecified impact, and does not go further.

The only condition Ubuntu names is that the rejectPublicSuffixes option is disabled. The notice does not explain the option's default value or any other conditions that must be met, so do not assume your application is unaffected. Check how your own code and configuration set it.

Who is realistically exposed

  • Servers running Ubuntu 18.04, 20.04 or 22.04 with the node-tough-cookie package installed.
  • Node.js applications that use tough-cookie to parse or store cookies, for example HTTP clients, scrapers, test tooling or proxies that keep a cookie jar.
  • Code that explicitly sets rejectPublicSuffixes to false, since the notice ties the problem to that option being disabled.
  • Teams that get tough-cookie through npm. The Ubuntu update changes the system package, not copies inside your application's node_modules folder.
The Ubuntu notice covers the distribution package. It does not list fixed upstream npm versions, and the research does not either. Check the upstream project's advisory for the CVE before assuming a specific npm version is safe.

How to check your exposure

Start by finding out whether the Ubuntu package is installed and which version you have. These read-only commands show the package status on Ubuntu; compare the version to the fixed versions in the table below.

Check the installed node-tough-cookie package version (Ubuntu)Shell
apt list --installed 2>/dev/null | grep node-tough-cookie
dpkg -s node-tough-cookie | grep -i '^Version'
Fixed package versions from USN-9080-1 (ESM Apps)
Ubuntu releasePackageFixed version
22.04 LTS (jammy)node-tough-cookie4.0.0-2ubuntu0.1~esm1
20.04 LTS (focal)node-tough-cookie3.0.0-1ubuntu0.1~esm1
18.04 LTS (bionic)node-tough-cookie2.3.2+dfsg-1ubuntu0.1~esm1

Next, look for copies installed through npm in your own projects. This command, run from an application directory, lists every installed tough-cookie version in the dependency tree so you can see which packages pull it in.

List tough-cookie in a Node.js project's dependency tree (run in the project directory)Shell
npm ls tough-cookie

Finally, search your own code and configuration for the option named in the notice. This read-only search prints each file and line that mentions it, excluding installed dependencies.

Find places where rejectPublicSuffixes is set (run from your source directory)Shell
grep -rn "rejectPublicSuffixes" --include=*.js --include=*.json --include=*.ts . --exclude-dir=node_modules

What to do now

  1. Run the version check above on every Ubuntu 18.04, 20.04 and 22.04 host and note where node-tough-cookie is installed.
  2. If you have Ubuntu Pro with ESM Apps enabled, apply a standard system update to receive the fixed package version for your release.
  3. If you do not have Ubuntu Pro, note that Ubuntu says a community fix might become publicly available in the future. Ubuntu also says Pro is free for up to five machines, which may cover small setups.
  4. Run npm ls tough-cookie in each Node.js application and review the versions found, checking the upstream advisory for CVE-2023-26136 for the fixed npm release.
  5. Search your code for rejectPublicSuffixes set to false and decide whether that setting is really needed.
  6. Restart the services that use the library after updating so running processes load the fixed code.
  7. Review how your applications handle cookies from untrusted servers, since that is where crafted cookies would come from.

This command updates only the node-tough-cookie package on a system where Ubuntu Pro ESM Apps is enabled. Afterwards, re-run the version check and confirm it matches the table above.

Apply the standard update for the package (Ubuntu with Ubuntu Pro ESM Apps enabled)Shell
sudo apt update
sudo apt install --only-upgrade node-tough-cookie
Caution. Restarting a Node.js service interrupts requests in flight. Schedule the restart in a maintenance window and restart only the services that actually load tough-cookie.

Detection and monitoring afterwards

The notice gives no indicators of compromise, so there is no known log pattern to hunt for. The practical signals are indirect: unexpected crashes or restarts of Node.js processes that handle cookies, and odd application behavior after requests to or from untrusted hosts.

  • Watch process restart counts and error logs for services that use a cookie jar.
  • Track dependency versions in your build pipeline so an outdated tough-cookie is flagged before deployment.
  • Subscribe to Ubuntu security notices for the packages you rely on, so ESM Apps updates do not go unnoticed.

For the public-facing side of your sites, a regular outside-in check of headers and certificates helps you catch drift, though it cannot see inside a Node.js dependency tree. The free security headers checker is a quick start, and our guide to WordPress plugin vulnerabilities explains the same dependency-tracking habit for another ecosystem.

What is still unknown

  • No CVSS score or severity rating appears in the research.
  • Whether the issue is being exploited is not stated.
  • The notice says the impact is possible denial of service or another unspecified impact, so the worst realistic outcome depends on your application.
  • The notice does not explain the default value of rejectPublicSuffixes or any other conditions for the issue.
  • The fixed upstream npm version is not given in the research.

For more practical guidance on keeping software current, see the Webforta security guides and the security blog.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9080-1: tough-cookie vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • Node.js
  • tough-cookie
  • prototype pollution
  • USN