Vulnerability Database · Go · Package report

github.com/briansmith/ring: vulnerability history, versions and safety

github.com/briansmith/ring is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 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.

Vulert verdict on github.com/briansmith/ring v0.0.0-20260722180013-840167e18e4f i

Updated on 23 Oct 2026

Careful: v0.0.0-20260722180013-840167e18e4f has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v0.0.0-20260722180013-840167e18e4f — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 15 May 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 4,108 i
  • OpenSSF scorecard 5/10 i
  • Last release 3 months ago i
  • Licence Apache-2.0 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/briansmith/ring, 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-20260722180013-840167e18e4f 22 Jul 2026 U1 Apache-2.0 No Details →
v0.0.0-20260715185039-c866e606f406 15 Jul 2026 U1 Apache-2.0 No Details →
v0.0.0-20260630221839-19b21ad9641b 30 Jun 2026 U1 Apache-2.0 No Details →
v0.0.0-20260630000711-fc6c02f04ce5 30 Jun 2026 U1 Apache-2.0 No Details →
v0.0.0-20260625180301-33f1755ca766 25 Jun 2026 U1 Apache-2.0 No Details →
v0.0.0-20260623224453-f60ab8f7b123 23 Jun 2026 U1 Apache-2.0 No Details →
v0.0.0-20260623213840-981027baf856 23 Jun 2026 U1 Apache-2.0 No Details →
v0.0.0-20260609032329-7d3dbbb41f19 09 Jun 2026 U1 Apache-2.0 No Details →
v0.0.0-20260520205234-b8d24b40d8df 20 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260520175418-bfbeca5916f8 20 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260520161832-38e12f2d154f 20 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260520155204-399eaefea4dc 20 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260519204305-29b12ee22be1 19 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260519201434-75dc1c37aaaa 19 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260519001309-c3e3579d85a3 19 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260518235609-2868e83259ac 18 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260518230826-5b2ad97ccc0b 18 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260518215001-2bef357c9ddb 18 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260518201108-972a8a6f003e 18 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260516173552-3bf90a106855 16 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260513185814-b14e5d3e5a53 13 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260511182215-c560a0fc84ef 11 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260508183632-99d1fadee6b9 08 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260507164510-d280695858f8 07 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260502185716-1ffab73ab506 02 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260501180422-caa9e1d1d8be 01 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260501170744-b77db884c6a0 01 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260501001736-6ad242a25814 01 May 2026 U1 Apache-2.0 No Details →
v0.0.0-20260430184143-8d0c53da1120 30 Apr 2026 U1 Apache-2.0 No Details →
v0.0.0-20260428200659-e6833be3a8b7 28 Apr 2026 U1 Apache-2.0 No Details →
v0.0.0-20260428191829-e86e18b0eec4 28 Apr 2026 U1 Apache-2.0 No Details →
v0.0.0-20260428183905-4d4209042fe5 28 Apr 2026 U1 Apache-2.0 No Details →
v0.0.0-20260428002504-cae93a78e06c 28 Apr 2026 U1 Apache-2.0 No Details →
v0.0.0-20260427221118-52bef9e7b020 27 Apr 2026 U1 Apache-2.0 No Details →
v0.0.0-20260420235148-33104744bdcd 20 Apr 2026 U1 Apache-2.0 No Details →
v0.0.0-20260411215526-d6495237ba63 11 Apr 2026 U1 Apache-2.0 No Details →
v0.0.0-20260323210237-12e0ad13042c 23 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260322230456-56ac0fb4b7f3 22 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260322041353-e19bc29f9925 22 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260319230051-6b3568299ddd 19 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260319162223-2eb5ece693e6 19 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260317204027-b04eed0a2f30 17 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260317201052-f57a362d6d36 17 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260316232817-e26dd862c9c2 16 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260316225346-7183be337917 16 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260316211759-3c9fff5f2e2e 16 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260312212749-da0eded9b0d9 12 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260312202729-a47232cb07c5 12 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260310181202-a8dc60e0e1a1 10 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309184533-767e8b41c1d1 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309085205-0ab752abe456 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309082933-5780943b60a6 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309080719-71eedd9d1a86 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309073543-c06bcd8e21ed 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309040204-6b9e60b7b9fb 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309033359-f5506315baaf 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309024933-3c6d0ca8abab 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309021618-e2e709c5e46a 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260309004810-418d0aeb0a50 09 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260308234051-fd82e12703bb 08 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260308214508-ca28aa291443 08 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260307212914-cd659c1f523b 07 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260306222112-e7fb084795df 06 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260306210626-360980e66762 06 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260306020519-e542a427a370 06 Mar 2026 U1 Apache-2.0 No Details →
v0.0.0-20260227233715-5a602e214b88 27 Feb 2026 U1 Apache-2.0 No Details →
v0.0.0-20260227224553-d946103f7125 27 Feb 2026 U1 Apache-2.0 No Details →
v0.0.0-20260223200548-2e633004338d 23 Feb 2026 U1 Apache-2.0 No Details →
v0.0.0-20260221210926-709ca4237521 21 Feb 2026 U1 Apache-2.0 No Details →
v0.0.0-20260217202124-c2037aa4d33c 17 Feb 2026 U1 Apache-2.0 No Details →
v0.0.0-20260212205404-0e8ece44e7fc 12 Feb 2026 U1 Apache-2.0 No Details →
v0.0.0-20260211231707-ffb0456ee593 11 Feb 2026 U1 Apache-2.0 No Details →
v0.0.0-20260209210246-267fccd2b070 09 Feb 2026 U1 Apache-2.0 No Details →
v0.0.0-20251031000059-522afb658067 31 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251030211928-b13ac9476d28 30 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251030154326-f0c0366d6dc4 30 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251027184621-59f237055b34 27 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251027170125-0c6dbaa664ab 27 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251024163122-e9f69ec963c8 24 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251022193641-472acf696e17 22 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251010235814-be7c46f5772b 10 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251010231142-74dd7694e791 10 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20251009235818-fff8ebf8a788 09 Oct 2025 U1 Apache-2.0 No Details →
v0.0.0-20250930024440-867f1d3134ee 30 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250930003236-ac41d3bd642a 30 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250929233055-c46a9990eebb 29 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250929232240-981cea266776 29 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250929154937-b93c3264bbbd 29 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250929152630-63f5a4577879 29 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250929034756-a89cf76bb231 29 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250929032439-b14b86952557 29 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250929021535-66cebe0458ab 29 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250927180933-e0c3426ae00b 27 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250927165753-4dae6296ef4e 27 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250927161849-2dd97f23b228 27 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250926230708-c127c244d0cd 26 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250926032605-32c527172613 26 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250926004353-a08a4e781694 26 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250925205040-9bb73ca0fc7e 25 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250925201750-9c8bd5b8b5d4 25 Sep 2025 U1 Apache-2.0 No Details →
v0.0.0-20250925173757-87609cbc30c4 25 Sep 2025 U1 — No Details →
v0.0.0-20250822045112-1bb94b3b8638 22 Aug 2025 U1 — No Details →
v0.0.0-20250821213227-2c890da9f3d7 21 Aug 2025 U1 — No Details →
v0.0.0-20250812180913-d018db62e1a4 12 Aug 2025 U1 — No Details →
v0.0.0-20250812080604-187457060e55 12 Aug 2025 U1 — No Details →
v0.0.0-20250810201348-67728f3463c8 10 Aug 2025 U1 — No Details →
v0.0.0-20250808013846-8ca60f4800de 08 Aug 2025 U1 — No Details →
v0.0.0-20250807185305-0d0579129554 07 Aug 2025 U1 — No Details →
v0.0.0-20250807174526-a9f81f02c55a 07 Aug 2025 U1 — No Details →
v0.0.0-20250806221952-161ad3cf1ea0 06 Aug 2025 U1 — No Details →
v0.0.0-20250804202534-b6e447a1da2c 04 Aug 2025 U1 — No Details →
v0.0.0-20250804183815-ae8fa0bc9583 04 Aug 2025 U1 — No Details →
v0.0.0-20250802203959-1f96c99015fe 02 Aug 2025 U1 — No Details →
v0.0.0-20250802192405-a31ab1773d21 02 Aug 2025 U1 — No Details →
v0.0.0-20250802191201-9878a610c61e 02 Aug 2025 U1 — No Details →
v0.0.0-20250802181720-30e1f00f6033 02 Aug 2025 U1 — No Details →
v0.0.0-20250801232111-42ac2601fd7a 01 Aug 2025 U1 — No Details →
v0.0.0-20250801205358-fe6e086a9a05 01 Aug 2025 U1 — No Details →
v0.0.0-20250801201756-5c225e578221 01 Aug 2025 U1 — No Details →
v0.0.0-20250801192553-b6630015d6e4 01 Aug 2025 U1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/briansmith/ring

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 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/briansmith/ring

Is github.com/briansmith/ring safe to use?

Vulert records 1 vulnerabilities for github.com/briansmith/ring in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/briansmith/ring's Vulert package health score?

Vulert scores github.com/briansmith/ring 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/briansmith/ring affected?

Yes. v0.0.0-20260722180013-840167e18e4f, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/briansmith/ring should I use?

v0.0.0-20260722180013-840167e18e4f 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/briansmith/ring have?

1 vulnerability is recorded for github.com/briansmith/ring in the Go ecosystem: 0 critical, 0 high, 0 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/briansmith/ring vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/briansmith/ring in the last 12 months, and the oldest entry in this database dates to 15 May 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/briansmith/ring 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/briansmith/ring for upcoming vulnerabilities?

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