VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/cockroachdb/pebble: vulnerability history, versions and safety

github.com/cockroachdb/pebble is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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 github.com/cockroachdb/pebble vulnerabilities

Vulert verdict on github.com/cockroachdb/pebble v1.1.5 i

Updated on 23 Oct 2026

Good news: Vulert has no vulnerability on record for github.com/cockroachdb/pebble in the Go ecosystem. That is a good sign, not a guarantee — keep an eye on the versions you run.

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

What to do: Run a supported release and keep monitoring: new vulnerabilities are published for packages every day. Nothing yet: a new vulnerability can appear at any time — Vulert alerts you if one affects this package. Monitor it with Vulert →

  • Current release v1.1.5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 6,061 i
  • OpenSSF scorecard 3/10 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 github.com/cockroachdb/pebble, 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-20261022140221-751712bce1bf 22 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261022140129-33282befc9ff 22 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261022140100-33618aa8d458 22 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261021160554-a995e890c06e 21 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261018163113-f60914a08d14 18 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261015145911-66b8074d8c73 15 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261015040434-77ba7b619a29 15 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261015040409-a7b8321871e3 15 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261013161138-1e7ac8591e6b 13 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261013014055-70b50023f8fe 13 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261009170919-0f1a75211389 09 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261007153016-afedb4b1c488 07 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261007153013-a476aa13e413 07 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20261007152945-815e4c21d027 07 Oct 2026 none BSD-3-Clause — Details →
v0.0.0-20260927013109-e0818dd07ec5 27 Sep 2026 none BSD-3-Clause — Details →
v0.0.0-20260924135503-652a081db94b 24 Sep 2026 none BSD-3-Clause — Details →
v0.0.0-20260918180620-ac8551c03255 18 Sep 2026 none BSD-3-Clause — Details →
v0.0.0-20260910015944-13596f1e1cea 10 Sep 2026 none BSD-3-Clause — Details →
v0.0.0-20260907153119-4669e65dbde5 07 Sep 2026 none BSD-3-Clause — Details →
v0.0.0-20260828194116-8ca7bf36e171 28 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260822143233-0457a364b877 22 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260814194718-235a3e8a5b9a 14 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260814194715-deadd6f4a5b8 14 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260814160745-be898db37f12 14 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260813173723-3d490097c279 13 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260810195854-db6d86fdbbaa 10 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260810195852-34786a57f952 10 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260810195848-b38bb9ace5cc 10 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260810193933-0fffd388aa30 10 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260806182117-d68e529d46c2 06 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260806182112-fd31f9534058 06 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260806182110-eee16f68a141 06 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260806181945-5365786c4c79 06 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260806181945-abab24a50ec8 06 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260806181945-f20cd5652e9e 06 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260804162114-14681d81301c 04 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260718061413-20bfd248d4c2 18 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260718061410-d10ff0778341 18 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260718061407-99bd55cbf486 18 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260718061346-264a7014c694 18 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260707124150-8fb150d9135d 07 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260703024023-7a5715d4264b 03 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260703021901-41f35d3cb7df 03 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260703021858-41bcff91f866 03 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260703021335-d11bee3dbab9 03 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20260623195010-aa9dc27c8e93 23 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260623195006-844499b24295 23 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260623195003-a3dbc21d6323 23 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260623195001-d98e22730ea2 23 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260622152211-48b632cd29bd 22 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260622152139-e50b05b8d12f 22 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260622152041-3b52a1827432 22 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260602192040-b6588354d334 02 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260602184823-8b9c157ab3e3 02 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260601224826-7be9edb17aee 01 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260601220101-615cb419ac7b 01 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260529192914-e39ebe210d37 29 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260529192222-3114100d650f 29 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260529184725-db3cc15a779e 29 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260528202118-1643098af72f 28 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260527173801-e56d0297843c 27 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260527170712-e675ee24184f 27 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260527152453-7c20ebb6590f 27 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260527152432-6470376021ab 27 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260527152431-13790f0039aa 27 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260527152428-73b9790c3e1f 27 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260527152407-fde0deb1ca1a 27 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260526160001-84f48387acd7 26 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260526151858-5f72e2140495 26 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260526014255-ade88dc74b24 26 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260524163854-457c8f102b6c 24 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260523000819-06387e65044c 23 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260522230553-debd9c83eba1 22 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260522224255-2722c6eb16f3 22 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260521014523-dff839c359e5 21 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260520180022-447ce53f4953 20 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260520013350-f82e3ff74d10 20 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260519200441-7fdf87f1b2fb 19 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260517144058-b4715d9ac5a2 17 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260517021807-43ed55be5850 17 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260515191109-25e0afe2fe86 15 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260515191109-458dc86643a3 15 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260515120244-6a5f3a4bdc83 15 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260514180738-019431aabf38 14 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260514124130-a8392fabe934 14 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260513201810-2ed1e34e8bc9 13 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260512222301-64af9cdd757b 12 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260512211116-e7ad94231f19 12 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260512165538-52849f5b0c10 12 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260512162936-34a101b009f5 12 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260511222506-032ab46220e6 11 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260509233351-4d7886c72fb3 09 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260508202932-56eeba0e1bdc 08 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260507233643-a9f9d9031113 07 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260507153324-255ced70d25b 07 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260506170320-7f431a57232f 06 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260505154852-a8f65fc1e39f 05 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260504182152-7112ed540266 04 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260504180209-7e45361427fa 04 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260501001252-653468ce9392 01 May 2026 none BSD-3-Clause — Details →
v0.0.0-20260430214646-c449e6203ec4 30 Apr 2026 none — — Details →
v0.0.0-20260430015639-92ad770029e4 30 Apr 2026 none — — Details →
v0.0.0-20260429152948-b94c8bde8183 29 Apr 2026 none — — Details →
v0.0.0-20260428233725-4affa364779d 28 Apr 2026 none — — Details →
v0.0.0-20260428160240-2fc75dfa8923 28 Apr 2026 none — — Details →
v0.0.0-20260427201442-babd2f323b0e 27 Apr 2026 none — — Details →
v0.0.0-20260424184603-521683eeeb9b 24 Apr 2026 none — — Details →
v0.0.0-20260424171904-e65daa8a439f 24 Apr 2026 none — — Details →
v0.0.0-20260424171840-cc5da027d4ac 24 Apr 2026 none — — Details →
v0.0.0-20260424171816-98f59c2f3f54 24 Apr 2026 none — — Details →
v0.0.0-20260423222614-758587f91744 23 Apr 2026 none — — Details →
v0.0.0-20260423043202-aeba97a41cf4 23 Apr 2026 none — — Details →
v0.0.0-20260422231655-7ba7d544ebaa 22 Apr 2026 none — — Details →
v0.0.0-20260422201210-f140dd54cbbd 22 Apr 2026 none — — Details →
v0.0.0-20260422012846-347213181b0b 22 Apr 2026 none — — Details →
v0.0.0-20260420194200-5106e152d66d 20 Apr 2026 none — — Details →
v0.0.0-20260420175855-10bf12317650 20 Apr 2026 none — — Details →
v0.0.0-20260420171030-f08461ba8d31 20 Apr 2026 none — — Details →
v0.0.0-20260417215743-9e98d04fee2f 17 Apr 2026 none — — Details →
v0.0.0-20260417180629-4e40d1dc4558 17 Apr 2026 none — — Details →

The newest 120 of 3,243 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 github.com/cockroachdb/pebble

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 github.com/cockroachdb/pebble

Is github.com/cockroachdb/pebble safe to use?

Vulert has no vulnerabilities on record for github.com/cockroachdb/pebble in Go 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 github.com/cockroachdb/pebble's Vulert package health score?

Vulert scores github.com/cockroachdb/pebble 84/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).

Which version of github.com/cockroachdb/pebble should I use?

v1.1.5 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/cockroachdb/pebble have?

0 vulnerabilities are recorded for github.com/cockroachdb/pebble in the Go 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 github.com/cockroachdb/pebble vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/cockroachdb/pebble 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 github.com/cockroachdb/pebble 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/cockroachdb/pebble for upcoming vulnerabilities?

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