How severe is GHSA-jcjx-c3j3-44pr?

No CVSS score has been assigned to GHSA-jcjx-c3j3-44pr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jcjx-c3j3-44pr?

GHSA-jcjx-c3j3-44pr affects the following packages: @cyyynthia/tokenize (npm). Ecosystems affected: npm.

How do I fix GHSA-jcjx-c3j3-44pr?

Update @cyyynthia/tokenize to 1.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jcjx-c3j3-44pr is resolved across your whole dependency graph.

How do I detect GHSA-jcjx-c3j3-44pr in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @cyyynthia/tokenize, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jcjx-c3j3-44pr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-jcjx-c3j3-44pr actively exploited in the wild?

No public exploit code has been indexed for GHSA-jcjx-c3j3-44pr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-jcjx-c3j3-44pr published, and has it been updated?

GHSA-jcjx-c3j3-44pr was published on November 10, 2021 and was last updated on November 8, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Insufficient Session Expiration in @cyyynthia/tokenizeGHSA-jcjx-c3j3-44pr

GHSA-jcjx-c3j3-44pr is a security vulnerability in @cyyynthia/tokenize. A fix is available for @cyyynthia/tokenize — see the affected versions and patch details below.

Published

Nov 10, 2021

Updated

Nov 8, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@cyyynthia/tokenizenpm

58downloads / week

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@cyyynthia/tokenize`	≥ 1.1.0&&< 1.1.3	1.1.3`npm install @cyyynthia/tokenize@1.1.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @cyyynthia/tokenize, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @cyyynthia/tokenize to 1.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jcjx-c3j3-44pr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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](ht

O3 Security · Impact-Aware SCA

Is GHSA-jcjx-c3j3-44pr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

Insufficient Session Expiration in @cyyynthia/tokenizeGHSA-jcjx-c3j3-44pr

Real-World Exposure

Description

Impact

Patches

Workarounds

References

For more information

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-jcjx-c3j3-44pr in your dependencies?