Vulnerability Database · Go · Package report

software.sslmate.com/src/go-pkcs12: vulnerability history, versions and safety

software.sslmate.com/src/go-pkcs12 is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 0 release, from Jun 2026 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 17 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on software.sslmate.com/src/go-pkcs12 v0.7.4 i

Updated on 23 Oct 2026

Good news: v0.7.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 93/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release v0.7.4 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 17 Aug 2026 i
  • Highest CVSS 6.3 i
  • With no published fix 0 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the Go module proxy, 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 software.sslmate.com/src/go-pkcs12, 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
v0.7.4 10 Oct 2026 none BSD-3-Clause — Details →
v0.7.3 24 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260609232049-03c441f6b026 09 Jun 2026 none BSD-3-Clause — Details →
v0.7.2 09 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260409222156-09ae172c24ac 09 Apr 2026 none BSD-3-Clause — Details →
v0.7.1 09 Apr 2026 none BSD-3-Clause — Details →
v0.0.0-20251222193521-783a42d0116e 22 Dec 2025 none BSD-3-Clause — Details →
v0.7.0 22 Dec 2025 none BSD-3-Clause — Details →
v0.0.0-20250718163450-6566e2ea1fad 18 Jul 2025 none BSD-3-Clause — Details →
v0.6.0 18 Jul 2025 none BSD-3-Clause — Details →
v0.0.0-20250716131502-3ac7bcc8013d 16 Jul 2025 none BSD-3-Clause — Details →
v0.5.0 31 Aug 2024 none BSD-3-Clause — Details →
v0.4.1-0.20240830171742-063edb9a38cf 30 Aug 2024 none BSD-3-Clause — Details →
v0.4.1-0.20240404164616-b59d8ebcab6d 04 Apr 2024 none BSD-3-Clause — Details →
v0.4.0 05 Nov 2023 none BSD-3-Clause — Details →
v0.3.0 26 Oct 2023 none BSD-3-Clause — Details →
v0.2.2-0.20230718180300-98b1ddcc99e2 18 Jul 2023 none BSD-3-Clause — Details →
v0.2.2-0.20230714000120-73963f6d7e25 14 Jul 2023 none BSD-3-Clause — Details →
v0.0.0-20230713191905-01f6600bb386 13 Jul 2023 none BSD-3-Clause — Details →
v0.2.1 13 Jul 2023 none BSD-3-Clause — Details →
v0.0.0-20220610195639-426fe5a3b19a 10 Jun 2022 none BSD-3-Clause — Details →
v0.2.1-0.20220610195639-426fe5a3b19a 10 Jun 2022 none BSD-3-Clause — Details →
v0.1.1-0.20220416145337-18dc7b9430c9 16 Apr 2022 none BSD-3-Clause — Details →
v0.2.0 16 Apr 2022 none BSD-3-Clause — Details →
v0.0.0-20220402154457-1a24189a369e 02 Apr 2022 none BSD-3-Clause — Details →
v0.1.0 02 Apr 2022 none BSD-3-Clause — Details →
v0.0.0-20220402154123-00dae7893ae5 02 Apr 2022 none BSD-3-Clause — Details →
v0.0.0-20210415151418-c5206de65a78 15 Apr 2021 none BSD-3-Clause — Details →
v0.0.0-20210222215041-dec221a1a07f 22 Feb 2021 none BSD-3-Clause — Details →
v0.0.0-20210222213544-e067c0a0c46d 22 Feb 2021 none BSD-3-Clause — Details →
v0.0.0-20201103104416-57fc603b7f52 03 Nov 2020 none BSD-3-Clause — Details →
v0.0.0-20201102150903-66718f75db0e 02 Nov 2020 none BSD-3-Clause — Details →
v0.0.0-20200830195227-52f69702a001 30 Aug 2020 none BSD-3-Clause — Details →
v0.0.0-20200619203921-c9ed90bd32dc 19 Jun 2020 none BSD-3-Clause — Details →
v0.0.0-20200408181440-2981468c0ff3 08 Apr 2020 none BSD-3-Clause — Details →
v0.0.0-20190322163127-6e380ad96778 22 Mar 2019 none BSD-3-Clause — Details →
v0.0.0-20190209200317-47dd539968c4 09 Feb 2019 none BSD-3-Clause — Details →
v0.0.0-20190129200600-3d128fbcedab 29 Jan 2019 none BSD-3-Clause — Details →
v0.0.0-20180114231543-2291e8f0f237 14 Jan 2018 none BSD-3-Clause — Details →

All 39 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 2

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

03 Vulnerabilities

Recorded vulnerabilities for software.sslmate.com/src/go-pkcs12

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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 software.sslmate.com/src/go-pkcs12

Is software.sslmate.com/src/go-pkcs12 safe to use?

Vulert records 2 vulnerabilities for software.sslmate.com/src/go-pkcs12 in Go: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is software.sslmate.com/src/go-pkcs12's Vulert package health score?

Vulert scores software.sslmate.com/src/go-pkcs12 93/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 software.sslmate.com/src/go-pkcs12 affected?

No. v0.7.4, 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.

Which version of software.sslmate.com/src/go-pkcs12 should I use?

v0.7.4 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 software.sslmate.com/src/go-pkcs12 have?

2 vulnerabilities are recorded for software.sslmate.com/src/go-pkcs12 in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new software.sslmate.com/src/go-pkcs12 vulnerabilities disclosed?

2 vulnerabilities were recorded for software.sslmate.com/src/go-pkcs12 in the last 12 months, and the oldest entry in this database dates to 22 Jun 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 software.sslmate.com/src/go-pkcs12 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 software.sslmate.com/src/go-pkcs12 for upcoming vulnerabilities?

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