Vulert records 1 vulnerabilities for sjcl in npm: 0 critical, 1 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is sjcl's Vulert package health score?

Vulert scores sjcl 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of sjcl affected?

Yes. 1.0.9, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of sjcl should I use?

1.0.9 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does sjcl have?

1 vulnerability is recorded for sjcl in the npm ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sjcl vulnerabilities disclosed?

1 vulnerability was recorded for sjcl in the last 12 months, and the oldest entry in this database dates to 17 Mar 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sjcl are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor sjcl for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the sjcl version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.

Vulnerability Database · npm · Package report

sjcl: vulnerability history, versions and safety

sjcl is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 9 releases, first recorded in Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

1 vulnerabilities recorded H1

1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →

1 in the last 12 months

Most recent disclosure 17 Mar 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sjcl vulnerabilities

Vulert verdict on sjcl 1.0.9 i

Updated on 23 Oct 2026

Careful: 1.0.9 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100

Security Some issues to review
Maintenance Sustainable
Popularity Key ecosystem project
Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

Current release 1.0.9 — affected i
Vulnerabilities on record 1 over 1 year · 1 in the last year i
Latest disclosure 17 Mar 2026 i
Highest CVSS 7.5 i
With no published fix 1 i
Depended on by 1,230 packages i
Stars 7,195 i
OpenSSF scorecard 1/10 i
Last release 7 months ago i
Licence BSD-2-Clause OR GPL-2.0-only i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for sjcl, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
1.0.9	18 Mar 2026	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →
1.0.8	10 Nov 2018	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →
1.0.7	04 Jul 2017	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →
1.0.6	10 Sep 2016	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →
1.0.5	09 Sep 2016	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →
1.0.3	20 May 2015	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →
1.0.2	25 Jan 2015	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →
1.0.1	30 Apr 2014	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →
1.0.0	10 Sep 2013	H1	BSD-2-Clause OR GPL-2.0-only	No	Details →

All 9 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for sjcl

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2026-4258: sjcl Package Lacks Point-on-Curve Validation Leading to ECDH Key Recovery	7.5 high	No fix published	17 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315