Advisory record · GHSA-4w5x-x539-ppf5

Incorrect handling of credential expiry by /nats-io/nats-server

CVSS 9.8 CriticalCriticalEPSS 0.023 · 83rd percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 11 Feb 2022, 23:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/nats-io/jwtGo<1.1.01.1.0
Identifiers
GHSA-4w5x-x539-ppf5 · CVE-2020-26892 · GHSA-2c64-vj8g-vwrq · GO-2022-0380
Weakness (CWE)
CWE-798
Published
11 Feb 2022
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The github.com/nats-io/jwt Go package versions before 1.1.0 mishandle credential expiry, so time-based expiration of credentials does not work. The source does not describe what an attacker must do beyond using expired credentials, and it gives few details on the exact access-control impact. Upgrade github.com/nats-io/jwt to 1.1.0 or later, and upgrade nats-server to 2.1.9 or later if it uses NATS Accounts.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.023, the 83rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:45 UTC First seen by agentprime
  2. 31 Oct 2026, 14:45 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.