Vulnerability Database · Go · Package report

github.com/uptrace/bun/driver/pgdriver: vulnerability history, versions and safety

github.com/uptrace/bun/driver/pgdriver is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Jun 2025 to Jul 2025. 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
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 github.com/uptrace/bun/driver/pgdriver v1.3.0 i

Updated on 23 Oct 2026

Action needed: v1.3.0 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.3.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 21 Jul 2025 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Stars 4,992 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence BSD-2-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 github.com/uptrace/bun/driver/pgdriver, 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
v1.3.1-0.20261003111454-0b7aa4629a4a 03 Oct 2026 M1 U1 BSD-2-Clause Yes Details →
v1.3.1-0.20261003105213-1d47fb81585b 03 Oct 2026 M1 U1 BSD-2-Clause Yes Details →
v1.3.0 01 Oct 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.19-0.20260930130816-691d97d1812f 30 Sep 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.19-0.20260923081935-2b56250bfd68 23 Sep 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.19-0.20260821141715-16613b290b9c 21 Aug 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.19-0.20260722090128-0e5e86826862 22 Jul 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.19-0.20260717144348-1a289f81f448 17 Jul 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.19-0.20260525101056-90001370d50e 25 May 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.19-0.20260408065208-ea46de8e20c1 08 Apr 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.18 28 Feb 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.17 21 Feb 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.17-0.20260221112953-44ac056ac35d 21 Feb 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.17-0.20260221105238-5c2b3d150688 21 Feb 2026 M1 U1 BSD-2-Clause Yes Details →
v1.2.17-0.20251221114735-cabcffd47e35 21 Dec 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.17-0.20251122094202-2d95435f5821 22 Nov 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.17-0.20251122084928-125717b2ce43 22 Nov 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16 20 Nov 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20251025090940-9f8a5f38b886 25 Oct 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20251021123705-a5efcd802d63 21 Oct 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20251020113822-00498d0a9d45 20 Oct 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20251020080220-972780b436b5 20 Oct 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20251017010935-106cc081023e 17 Oct 2025 M1 U1 BSD-2-Clause Yes Details →
v0.0.0-20250927064007-d9f273fc119f 27 Sep 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20250927064007-d9f273fc119f 27 Sep 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20250925110005-042b10aa50f6 25 Sep 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20250830012911-26996878ae81 30 Aug 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20250826131321-1d3e21a6f426 26 Aug 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20250824142301-c12edf090a9f 24 Aug 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20250822141525-16ebb0916c2b 22 Aug 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20250809153831-45c406b38660 09 Aug 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.16-0.20250725093016-412336026c73 25 Jul 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.15 18 Jul 2025 M1 U1 BSD-2-Clause Yes Details →
v0.0.0-20250717033604-5c5af417e8b4 17 Jul 2025 M1 U1 BSD-2-Clause Yes Details →
v0.0.0-20250710065204-9464a84bdf8f 10 Jul 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.15-0.20250710065204-9464a84bdf8f 10 Jul 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.14 16 Jun 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.13 11 Jun 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.13-0.20250609084643-4bda447436ad 09 Jun 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.12 08 Jun 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.12-0.20250512032224-d087f423f3b4 12 May 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.12-0.20250407080759-04da1b6d1c63 07 Apr 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.11 06 Mar 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.11-0.20250304081731-b2e2a0d3b070 04 Mar 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.10 18 Feb 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.10-0.20250218062638-1090d4d1f3af 18 Feb 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.9 26 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.9-0.20250125063716-4b02d19eae80 25 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.9-0.20250122124652-7d22ddd263b2 22 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.9-0.20250122085242-40f68ba7b1d9 22 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.9-0.20250122084017-c40e4f3c50c7 22 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20250118084027-815e11a023d2 18 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.9-0.20250115110323-dbae5e64bc78 15 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.9-0.20250106050727-ec5d81ebeb03 06 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.8 06 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.8-0.20250106033204-e8aaa4610cc0 06 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.8-0.20250101071657-254c441dacbd 01 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.7 01 Jan 2025 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241223024547-fcf8a4f98323 23 Dec 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241206060409-014b142c4ec4 06 Dec 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241204060350-96baf25fb761 04 Dec 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241203165138-7703a2e931f6 03 Dec 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241129070916-8b05a1316dd5 29 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241126124946-928d0779110e 26 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241125022320-89e9d5169f8a 25 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241122111038-ae8bdd31cd22 22 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241122083800-6986d164714c 22 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241122062805-993ae63911e7 22 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241122035354-7e826e063b62 22 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.7-0.20241121134904-cb319f8e0b5f 21 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.6 20 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.6-0.20241120120334-02d497c23a29 20 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.6-0.20241118024642-c6b302ff06f6 18 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.6-0.20241116065658-4fcf18a8cdf5 16 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.6-0.20241113140010-abcd7799981f 13 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.6-0.20241112161427-b10bd391df89 12 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.6-0.20241109100353-5d55190f8bab 09 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.6-0.20241104052319-1b62093ccf06 04 Nov 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.4-0.20241026085619-b0fb54c4cff0 26 Oct 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.5 26 Oct 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.4-0.20241021054314-3ef44ce1cdd9 21 Oct 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.4-0.20240922072313-d87deffb1d61 22 Sep 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.3 31 Aug 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.3-0.20240831054131-6c83b05f27c7 31 Aug 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.2 29 Aug 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.2-0.20240712062632-1573ae7c2fff 12 Jul 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.2-0.20240702055224-6ffe11dc8f85 02 Jul 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.2-0.20240610104221-5be346ff68e6 10 Jun 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.2-0.20240515115107-f2f77e5c6bd7 15 May 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.2-0.20240407104356-b005dc2a9034 07 Apr 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.2-0.20240403060008-7bc330f152cf 03 Apr 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.1 02 Apr 2024 M1 U1 BSD-2-Clause Yes Details →
v1.2.0 02 Apr 2024 M1 U1 BSD-2-Clause Yes Details →
v1.1.18-0.20240326073620-664e2f154f11 26 Mar 2024 M1 U1 BSD-2-Clause Yes Details →
v1.1.18-0.20240129120547-ed6ed74d5379 29 Jan 2024 M1 U1 BSD-2-Clause Yes Details →
v1.1.18-0.20240129105606-9052fc4cdf3a 29 Jan 2024 M1 U1 BSD-2-Clause Yes Details →
v1.1.17 11 Jan 2024 M1 U1 BSD-2-Clause Yes Details →
v1.1.17-0.20240111065442-19a82643726e 11 Jan 2024 M1 U1 BSD-2-Clause Yes Details →
v1.1.17-0.20231001121055-8a4383505d7e 01 Oct 2023 M1 U1 BSD-2-Clause Yes Details →
v1.1.16 16 Sep 2023 M1 U1 BSD-2-Clause Yes Details →
v1.1.16-0.20230916055458-0c2115269e71 16 Sep 2023 M1 U1 — Yes Details →
v1.1.15 10 Sep 2023 M1 U1 — Yes Details →
v1.1.15-0.20230910083446-9a314e0d9c6a 10 Sep 2023 M1 U1 — Yes Details →
v1.1.15-0.20230701074403-838a3bce1805 01 Jul 2023 M1 U1 — Yes Details →
v1.1.15-0.20230625075419-4d8e9e38bd87 25 Jun 2023 M1 U1 — Yes Details →
v1.1.15-0.20230610061804-5ceba076668e 10 Jun 2023 M1 U1 — Yes Details →
v0.0.0-20230524111717-dacffd2ac21a 24 May 2023 M1 U1 — Yes Details →
v1.1.14 24 May 2023 M1 U1 — Yes Details →
v1.1.13 06 May 2023 M1 U1 — Yes Details →
v1.1.13-0.20230308071428-7cd855e64a02 08 Mar 2023 M1 U1 — Yes Details →
v1.1.12 20 Feb 2023 M1 U1 — Yes Details →
v1.1.11 01 Feb 2023 M1 U1 — Yes Details →
v1.1.10 16 Jan 2023 M1 U1 — Yes Details →
v0.0.0-20230108112247-28c5c07b0060 08 Jan 2023 M1 U1 — Yes Details →
v1.1.10-0.20230108112247-28c5c07b0060 08 Jan 2023 M1 U1 — Yes Details →
v1.1.10-0.20230105105302-07c788236b58 05 Jan 2023 M1 U1 — Yes Details →
v0.0.0-20221227210409-67a448897eaa 27 Dec 2022 M1 U1 — Yes Details →
v1.1.10-0.20221206090415-9552cb582826 06 Dec 2022 M1 U1 — Yes Details →
v1.1.10-0.20221203130216-996fead2595f 03 Dec 2022 M1 U1 — Yes Details →
v1.1.10-0.20221201095209-b455b1704d95 01 Dec 2022 M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/uptrace/bun/driver/pgdriver

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 github.com/uptrace/bun/driver/pgdriver

Is github.com/uptrace/bun/driver/pgdriver safe to use?

Vulert records 2 vulnerabilities for github.com/uptrace/bun/driver/pgdriver 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 github.com/uptrace/bun/driver/pgdriver's Vulert package health score?

Vulert scores github.com/uptrace/bun/driver/pgdriver 83/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 github.com/uptrace/bun/driver/pgdriver affected?

Yes. v1.3.0, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/uptrace/bun/driver/pgdriver should I use?

v1.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/uptrace/bun/driver/pgdriver have?

2 vulnerabilities are recorded for github.com/uptrace/bun/driver/pgdriver 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 github.com/uptrace/bun/driver/pgdriver vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/uptrace/bun/driver/pgdriver in the last 12 months, and the oldest entry in this database dates to 12 Jun 2025. 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/uptrace/bun/driver/pgdriver 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/uptrace/bun/driver/pgdriver for upcoming vulnerabilities?

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