CVE-2020-26149 json
Sensitive data exposure in NATS
published 6y ago modified 4mo ago also GHSA-82rf-q3pr-4f6p , EUVD-2020-1419
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
NATS nats.js before 2.0.0-209, nats.ws before 1.0.0-111, and nats.deno before 1.0.0-9 allow credential disclosure from a client to a server.
Patch / fix
- npm nats 2.0.0-209
- npm nats.ws 1.0.0-111
- linuxfoundation nats.deno 1.0.0-9
- linuxfoundation nats.js 2.0.0-209
- linuxfoundation nats.ws 1.0.0-111
Is CVE-2020-26149 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | nats | >=2.0.0-201, <2.0.0-209 |
2.0.0-209 |
| npm | nats.ws | >=1.0.0-85, <1.0.0-111 |
1.0.0-111 |
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
github.com
/nats-io/nats.ws/commit/0a37ac2a411ff63f0707cda69a268c5fc4079eb7
web, patch, third-party-advisory
-
github.com
/nats-io/nats.deno/compare/v1.0.0-8...v1.0.0-9
web, patch, third-party-advisory
-
openwall.com
/lists/oss-security/2020/09/30/3
web, mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-26149
advisory
-
github.com
/nats-io/nats.ws
package
Sources
- CVE List CVE-2020-26149
- GitHub Advisory GHSA-82rf-q3pr-4f6p
- NVD CVE-2020-26149
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.