Vulnerability Database · npm · Package report

solc: vulnerability history, versions and safety

solc is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on solc 0.8.38 i

Updated on 23 Oct 2026

Good news: 0.8.38, the version you would install today, has no known vulnerabilities.

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 0.8.38 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.8.38 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.8.38 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,509 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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.

01 Versions

Which versions are affected

Every version Vulert tracks for solc, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.8.38 22 Oct 2026 none MIT — Details →
0.8.37 10 Sep 2026 none MIT — Details →
0.8.36 09 Jul 2026 none MIT — Details →
0.8.35 29 Apr 2026 none MIT — Details →
0.8.34 18 Feb 2026 none MIT — Details →
0.8.33 18 Dec 2025 none MIT — Details →
0.8.32 18 Dec 2025 none MIT — Details →
0.8.31 03 Dec 2025 none MIT — Details →
0.8.30 07 May 2025 none MIT — Details →
0.8.29 12 Mar 2025 none MIT — Details →
0.8.28 09 Oct 2024 none MIT — Details →
0.8.27 04 Sep 2024 none MIT — Details →
0.8.26 21 May 2024 none MIT — Details →
0.8.25 14 Mar 2024 none MIT — Details →
0.8.24 25 Jan 2024 none MIT — Details →
0.8.23-fixed 09 Nov 2023 none MIT — Details →
0.8.23 08 Nov 2023 none MIT — Details →
0.8.22 25 Oct 2023 none MIT — Details →
0.8.21 19 Jul 2023 none MIT — Details →
0.8.20 10 May 2023 none MIT — Details →
0.8.19 22 Feb 2023 none MIT — Details →
0.8.18 01 Feb 2023 none MIT — Details →
0.8.17 08 Sep 2022 none MIT — Details →
0.8.16 08 Aug 2022 none MIT — Details →
0.8.15 15 Jun 2022 none MIT — Details →
0.8.14-fixed 18 May 2022 none MIT — Details →
0.8.14 17 May 2022 none MIT — Details →
0.8.13 16 Mar 2022 none MIT — Details →
0.8.12 16 Feb 2022 none MIT — Details →
0.8.11 20 Dec 2021 none MIT — Details →
0.8.10 09 Nov 2021 none MIT — Details →
0.8.9 29 Sep 2021 none MIT — Details →
0.8.8 27 Sep 2021 none MIT — Details →
0.8.7-fixed 11 Aug 2021 none MIT — Details →
0.8.7 11 Aug 2021 none MIT — Details →
0.8.6 22 Jun 2021 none MIT — Details →
0.8.5 10 Jun 2021 none MIT — Details →
0.8.4 21 Apr 2021 none MIT — Details →
0.8.3 23 Mar 2021 none MIT — Details →
0.8.2 03 Mar 2021 none MIT — Details →
0.8.1 27 Jan 2021 none MIT — Details →
0.8.0 16 Dec 2020 none MIT — Details →
0.7.6 16 Dec 2020 none MIT — Details →
0.7.5 18 Nov 2020 none MIT — Details →
0.7.4 19 Oct 2020 none MIT — Details →
0.7.3 07 Oct 2020 none MIT — Details →
0.7.2 28 Sep 2020 none MIT — Details →
0.7.1 02 Sep 2020 none MIT — Details →
0.7.0 28 Jul 2020 none MIT — Details →
0.6.12 22 Jul 2020 none MIT — Details →
0.6.11 07 Jul 2020 none MIT — Details →
0.6.10 11 Jun 2020 none MIT — Details →
0.6.9 04 Jun 2020 none MIT — Details →
0.6.8 14 May 2020 none MIT — Details →
0.6.7 04 May 2020 none MIT — Details →
0.6.6 09 Apr 2020 none MIT — Details →
0.6.5 06 Apr 2020 none MIT — Details →
0.5.17 17 Mar 2020 none MIT — Details →
0.6.4 10 Mar 2020 none MIT — Details →
0.6.3 18 Feb 2020 none MIT — Details →
0.6.2 27 Jan 2020 none MIT — Details →
0.6.1 03 Jan 2020 none MIT — Details →
0.5.16 02 Jan 2020 none MIT — Details →
0.6.0 17 Dec 2019 none MIT — Details →
0.5.15 17 Dec 2019 none MIT — Details →
0.5.14 09 Dec 2019 none MIT — Details →
0.5.13 14 Nov 2019 none MIT — Details →
0.5.12 01 Oct 2019 none MIT — Details →
0.5.11 12 Aug 2019 none MIT — Details →
0.5.10 25 Jun 2019 none MIT — Details →
0.5.9 28 May 2019 none MIT — Details →
0.4.26 23 May 2019 none MIT — Details →
0.5.8 30 Apr 2019 none MIT — Details →
0.5.7 26 Mar 2019 none MIT — Details →
0.5.6 13 Mar 2019 none MIT — Details →
0.5.5 05 Mar 2019 none MIT — Details →
0.5.4 12 Feb 2019 none MIT — Details →
0.5.3 22 Jan 2019 none MIT — Details →
0.5.2 20 Dec 2018 none MIT — Details →
0.5.1 03 Dec 2018 none MIT — Details →
0.5.0 13 Nov 2018 none MIT — Details →
0.4.25 13 Sep 2018 none MIT — Details →
0.4.24 16 May 2018 none MIT — Details →
0.4.23 19 Apr 2018 none MIT — Details →
0.4.22 17 Apr 2018 none MIT — Details →
0.4.21 08 Mar 2018 none MIT — Details →
0.4.20 14 Feb 2018 none MIT — Details →
0.4.19 01 Dec 2017 none MIT — Details →
0.4.18 18 Oct 2017 none MIT — Details →
0.4.17 22 Sep 2017 none MIT — Details →
0.4.16 25 Aug 2017 none MIT — Details →
0.4.15 09 Aug 2017 none MIT — Details →
0.4.14 31 Jul 2017 none MIT — Details →
0.4.13 06 Jul 2017 none MIT — Details →
0.4.11 03 May 2017 none MIT — Details →
0.4.10 15 Mar 2017 none MIT — Details →
0.4.9 02 Feb 2017 none MIT — Details →
0.4.8 13 Jan 2017 none MIT — Details →
0.4.7 16 Dec 2016 none MIT — Details →
0.4.6 29 Nov 2016 none MIT — Details →
0.4.5 29 Nov 2016 none — — Details →
0.4.4 01 Nov 2016 none — — Details →
0.4.3 25 Oct 2016 none — — Details →
0.4.2 17 Sep 2016 none — — Details →
0.4.1 09 Sep 2016 none — — Details →
0.4.0 08 Sep 2016 none — — Details →
0.3.6 11 Aug 2016 none — — Details →
0.3.5 10 Jun 2016 none — — Details →
0.3.4 31 May 2016 none — — Details →
0.3.3 31 May 2016 none — — Details →
0.3.2-1 06 May 2016 none — — Details →
0.3.1-1 01 Apr 2016 none — — Details →
0.3.0-1 13 Mar 2016 none — — Details →
0.2.2-2 20 Feb 2016 none — — Details →
0.2.1-1 31 Jan 2016 none — — Details →
0.2.0-1 03 Dec 2015 none — — Details →
0.1.7-1 17 Nov 2015 none — — Details →
0.1.6-2 20 Oct 2015 none — — Details →
0.1.6-1 19 Oct 2015 none — — Details →
0.1.6 16 Oct 2015 none — — Details →

The newest 120 of 127 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for solc

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About solc

Is solc safe to use?

Vulert has no vulnerabilities on record for solc in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is solc's Vulert package health score?

Vulert scores solc 82/100, which reads as in good shape. 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).

Is the latest version of solc affected?

No. 0.8.38, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does solc have?

0 vulnerabilities are recorded for solc in the npm ecosystem: 0 critical, 0 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 solc vulnerabilities disclosed?

0 vulnerabilities were recorded for solc in the last 12 months. 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 solc 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 solc for upcoming vulnerabilities?

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