VulertSecurity VulertSecurity

Vulnerability Database · Pub · Package report

pointycastle: vulnerability history, versions and safety

pointycastle is a package in the Pub ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Pub 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.

See all pointycastle vulnerabilities

Vulert verdict on pointycastle 4.0.0 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 4.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 20 months ago i

Version list, release dates, licence and dependants published by pub.dev, 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 pointycastle, 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
4.0.0 19 Feb 2025 none — — Details →
3.9.1 07 May 2024 none — — Details →
3.9.0 19 Apr 2024 none — — Details →
3.8.0 05 Apr 2024 none — — Details →
3.7.4 15 Jan 2024 none — — Details →
3.7.3 14 Apr 2023 none — — Details →
3.7.2 23 Mar 2023 none — — Details →
3.7.1 21 Mar 2023 none — — Details →
3.7.0 16 Mar 2023 none — — Details →
3.6.2 09 Sep 2022 none — — Details →
3.6.1 19 Jul 2022 none — — Details →
3.6.0 27 Apr 2022 none — — Details →
3.5.2 07 Mar 2022 none — — Details →
3.5.1 08 Feb 2022 none — — Details →
3.5.0 30 Dec 2021 none — — Details →
3.4.0 09 Nov 2021 none — — Details →
3.4.0-rc2 04 Nov 2021 none — — Details →
3.4.0-rc1 03 Nov 2021 none — — Details →
3.3.5 27 Oct 2021 none — — Details →
3.3.4 07 Sep 2021 none — — Details →
3.3.3 03 Sep 2021 none — — Details →
3.3.2 27 Aug 2021 none — — Details →
3.3.1 18 Aug 2021 none — — Details →
3.3.0 12 Aug 2021 none — — Details →
3.2.0 29 Jul 2021 none — — Details →
3.2.0-rc0 05 Jul 2021 none — — Details →
3.1.3 29 Jun 2021 none — — Details →
3.1.2 17 Jun 2021 none — — Details →
3.1.1 04 Jun 2021 none — — Details →
3.0.1 24 Mar 2021 none — — Details →
3.0.0-nullsafety.2 05 Feb 2021 none — — Details →
2.0.1 16 Jan 2021 none — — Details →
2.0.0 02 Oct 2020 none — — Details →
2.0.0-rc2 25 Sep 2020 none — — Details →
2.0.0-rc1 12 Sep 2020 none — — Details →
1.0.2 15 Nov 2019 none — — Details →
1.0.1 20 Feb 2019 none — — Details →
1.0.0 17 Dec 2018 none — — Details →
1.0.0-rc4 04 Oct 2018 none — — Details →
1.0.0-rc3 14 Sep 2018 none — — Details →
1.0.0-rc2 21 Jun 2018 none — — Details →
1.0.0-rc1 28 May 2018 none — — Details →
0.11.1 28 Jan 2018 none — — Details →
0.11.0 28 Jan 2018 none — — Details →
0.10.0+5 08 Dec 2016 none — — Details →
0.10.0+4 08 Dec 2016 none — — Details →
0.10.0+3 08 Dec 2016 none — — Details →
0.10.0+2 07 Dec 2016 none — — Details →
0.10.0+1 12 Feb 2016 none — — Details →
0.10.0 03 Feb 2016 none — — Details →
0.10.0-dev 26 Jan 2016 none — — Details →

All 51 versions Vulert tracks for this package. 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 pointycastle

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 pointycastle

Is pointycastle safe to use?

Vulert has no vulnerabilities on record for pointycastle in Pub 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 pointycastle's Vulert package health score?

Vulert scores pointycastle 87/100, which reads as healthy. 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 pointycastle affected?

No. 4.0.0, 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 pointycastle have?

0 vulnerabilities are recorded for pointycastle in the Pub 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 pointycastle vulnerabilities disclosed?

0 vulnerabilities were recorded for pointycastle 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 pointycastle 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 pointycastle for upcoming vulnerabilities?

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