Advisories
For your digest

nats, nats.ws: Sensitive data exposure in NATS

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • nats (npm): from 2.0.0-201, before 2.0.0-209
  • nats.ws (npm): from 1.0.0-85, before 1.0.0-111

The fix

  • nats (npm) fixed in 2.0.0-209

    npm
    npm install nats@2.0.0-209
    pnpm
    pnpm add nats@2.0.0-209
    yarn
    yarn add nats@2.0.0-209
    bun
    bun add nats@2.0.0-209
    Check what is installed
    npm ls nats
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency nats to 2.0.0-209 or the nearest later release, to fix CVE-2020-26149. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • nats.ws (npm) fixed in 1.0.0-111

    npm
    npm install nats.ws@1.0.0-111
    pnpm
    pnpm add nats.ws@1.0.0-111
    yarn
    yarn add nats.ws@1.0.0-111
    bun
    bun add nats.ws@1.0.0-111
    Check what is installed
    npm ls nats.ws
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency nats.ws to 1.0.0-111 or the nearest later release, to fix CVE-2020-26149. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

No evidence that it is being used, or can be. It is listed because of what it affects.

Timeline

  1. First published here, as "For your digest".