Which versions of @cyyynthia/tokenize are affected by GHSA-JCJX-C3J3-44PR?

@cyyynthia/tokenize (npm) versions >= 1.1.0, < 1.1.3 is affected.

Is there a fix for GHSA-JCJX-C3J3-44PR?

Yes. GHSA-JCJX-C3J3-44PR is fixed in 1.1.3. Upgrade to this version or later.

Is GHSA-JCJX-C3J3-44PR exploitable, and should I be worried?

Whether GHSA-JCJX-C3J3-44PR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-JCJX-C3J3-44PR is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-JCJX-C3J3-44PR?

Upgrade @cyyynthia/tokenize to 1.1.3 or later.

GHSA-JCJX-C3J3-44PR in @cyyynthia/tokenize

Q: What is GHSA-JCJX-C3J3-44PR?

GHSA-JCJX-C3J3-44PR is a high-severity security vulnerability in @cyyynthia/tokenize (npm), affecting versions >= 1.1.0, < 1.1.3. It is fixed in 1.1.3.

Q: Is there a fix for GHSA-JCJX-C3J3-44PR?

Yes. GHSA-JCJX-C3J3-44PR is fixed in 1.1.3. Upgrade to this version or later.

Q: Is GHSA-JCJX-C3J3-44PR exploitable, and should I be worried?

Whether GHSA-JCJX-C3J3-44PR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-JCJX-C3J3-44PR is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-JCJX-C3J3-44PR?

Upgrade @cyyynthia/tokenize to 1.1.3 or later.

GHSA-JCJX-C3J3-44PR

GHSA-JCJX-C3J3-44PR is a high-severity security vulnerability in @cyyynthia/tokenize (npm), affecting versions >= 1.1.0, < 1.1.3. It is fixed in 1.1.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Insufficient Session Expiration in @cyyynthia/tokenize

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 [email protected]

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.

Affected versions

@cyyynthia/tokenize (>= 1.1.0, < 1.1.3)

Security releases

@cyyynthia/tokenize → 1.1.3 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Version 1.1.3 contains a patch that'll invalidate these faulty tokens and make new ones behave as expected.

Frequently Asked Questions

What is GHSA-JCJX-C3J3-44PR? GHSA-JCJX-C3J3-44PR is a high-severity security vulnerability in @cyyynthia/tokenize (npm), affecting versions >= 1.1.0, < 1.1.3. It is fixed in 1.1.3.
Which versions of @cyyynthia/tokenize are affected by GHSA-JCJX-C3J3-44PR? @cyyynthia/tokenize (npm) versions >= 1.1.0, < 1.1.3 is affected.
Is there a fix for GHSA-JCJX-C3J3-44PR? Yes. GHSA-JCJX-C3J3-44PR is fixed in 1.1.3. Upgrade to this version or later.
Is GHSA-JCJX-C3J3-44PR exploitable, and should I be worried? Whether GHSA-JCJX-C3J3-44PR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-JCJX-C3J3-44PR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-JCJX-C3J3-44PR? Upgrade @cyyynthia/tokenize to 1.1.3 or later.