VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/bincyber/go-sqlcrypter: vulnerability history, versions and safety

github.com/bincyber/go-sqlcrypter is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 0 release, from Jan 2024 to Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded L1 U2
i
3 with no fix published

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

See the unfixed vulnerabilities →
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 github.com/bincyber/go-sqlcrypter vulnerabilities

Vulert verdict on github.com/bincyber/go-sqlcrypter v0.3.0 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.3.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 05 Jun 2024 i
  • Highest CVSS 3.7 i
  • With no published fix 3 i
  • Stars 13 i
  • Last release 4 months ago i
  • Licence MIT 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 github.com/bincyber/go-sqlcrypter, 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.0.0-20260603043558-ffc5a83eec6f 03 Jun 2026 none MIT — Details →
v0.3.1-0.20260603043558-ffc5a83eec6f 03 Jun 2026 none MIT — Details →
v0.3.1-0.20260602191249-e11f2c4b8ad4 02 Jun 2026 none MIT — Details →
v0.3.0 02 Jun 2026 none MIT — Details →
v0.2.1-0.20260519044919-bd1a6ceb9e3c 19 May 2026 none MIT — Details →
v0.0.0-20260518041408-a177db9a43a5 18 May 2026 none MIT — Details →
v0.2.1-0.20260518041408-a177db9a43a5 18 May 2026 none MIT — Details →
v0.0.0-20260404110629-23f072a21473 04 Apr 2026 none MIT — Details →
v0.2.1-0.20260404110629-23f072a21473 04 Apr 2026 none MIT — Details →
v0.0.0-20221111224913-9ff66eacb689 11 Nov 2022 none MIT — Details →
v0.1.1-0.20221111224913-9ff66eacb689 11 Nov 2022 none MIT — Details →
v0.2.0 11 Nov 2022 none MIT — Details →
v0.0.0-20220507143709-4792137b6491 07 May 2022 none MIT — Details →
v0.0.0-20220507143709-e624fa9c6778 07 May 2022 none MIT — Details →
v0.1.0 07 May 2022 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/bincyber/go-sqlcrypter

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
IV Collision Vulnerability in go-sqlcrypter 3.7 low No fix published 20 May 2024
IV Collision Vulnerability in go-sqlcrypter N/A unrated No fix published 30 Jan 2024
IV Collision Vulnerability in go-sqlcrypter N/A unrated No fix published 05 Jun 2024

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 github.com/bincyber/go-sqlcrypter

Is github.com/bincyber/go-sqlcrypter safe to use?

Vulert records 3 vulnerabilities for github.com/bincyber/go-sqlcrypter in Go: 0 critical, 0 high, 0 medium and 1 low, plus 2 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is github.com/bincyber/go-sqlcrypter's Vulert package health score?

Vulert scores github.com/bincyber/go-sqlcrypter 65/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).

Is the latest version of github.com/bincyber/go-sqlcrypter affected?

No. v0.3.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.

Which version of github.com/bincyber/go-sqlcrypter should I use?

v0.3.0 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 github.com/bincyber/go-sqlcrypter have?

3 vulnerabilities are recorded for github.com/bincyber/go-sqlcrypter in the Go ecosystem: 0 critical, 0 high, 0 medium and 1 low, plus 2 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 github.com/bincyber/go-sqlcrypter vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/bincyber/go-sqlcrypter in the last 12 months, and the oldest entry in this database dates to 30 Jan 2024. 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 github.com/bincyber/go-sqlcrypter 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 github.com/bincyber/go-sqlcrypter for upcoming vulnerabilities?

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