Insufficient Session Expiration in @cyyynthia/tokenize
Impact
A bug introduced in version 1.1.0 made Tokenize generate faulty tokens with NaN as a generation date. As a result, tokens would not properly expire and remain valid regardless of the lastTokenReset field.
Patches
Version 1.1.3 contains a patch that'll invalidate these faulty tokens and make new ones behave as expected.
Workarounds
None. Tokens do not hold the necessary information to perform invalidation anymore.
References
PR #1
For more information
If you have any questions or comments about this advisory:
- Open an issue in github.com/cyyynthia/tokenize
- Email us at cynthia@cynthia.dev
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | @cyyynthia/tokenize | >= 1.1.0, < 1.1.3 | 1.1.3 |
References
- Weakness (CWE)
CWE-613- Platform
- npm
- Package
@cyyynthia/tokenize- Disclosed
- 10.11.2021
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-jcjx-c3j3-44pr - CC BY 4.0
Vulnerability history: @cyyynthia/tokenize
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.