VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/docker/notary: vulnerability history, versions and safety

github.com/docker/notary is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in May 2022. 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 H1
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/docker/notary vulnerabilities

Vulert verdict on github.com/docker/notary v0.6.1 i

Updated on 23 Oct 2026

Action needed: v0.6.1 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

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

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 v0.6.1 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 3,290 i
  • OpenSSF scorecard 4/10 i
  • Last release 102 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/docker/notary, 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.6.2-0.20200107030026-48b3e3445928 07 Jan 2020 H1 Apache-2.0 Yes Details →
v0.0.0-20190722142325-02d9e3444a1e 22 Jul 2019 H1 Apache-2.0 Yes Details →
v0.0.0-20190524024310-a09c05a6a746 24 May 2019 H1 Apache-2.0 Yes Details →
v0.6.2-0.20180416083904-d4f8e4a98e77 16 Apr 2018 H1 Apache-2.0 Yes Details →
v0.6.1 10 Apr 2018 H1 Apache-2.0 Yes Details →
v0.6.0 28 Feb 2018 H1 Apache-2.0 Yes Details →
v0.5.2-0.20171120211650-a41821feaf59 20 Nov 2017 H1 Apache-2.0 Yes Details →
v0.0.0-20171005204928-fab4c6708bc2 05 Oct 2017 H1 Apache-2.0 Yes Details →
v0.5.2-0.20171005204928-fab4c6708bc2 05 Oct 2017 H1 Apache-2.0 Yes Details →
v0.0.0-20170908063616-8a1de3cfc3f1 08 Sep 2017 H1 Apache-2.0 Yes Details →
v0.5.2-0.20170908063616-8a1de3cfc3f1 08 Sep 2017 H1 Apache-2.0 Yes Details →
v0.5.1 28 Aug 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170821232618-f2744d5270b0 21 Aug 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170724062900-655850e94dcb 24 Jul 2017 H1 Apache-2.0 Yes Details →
v0.0.0-20170608174111-7c74907a055b 08 Jun 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170608174111-7c74907a055b 08 Jun 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170530180339-e2c0ea50274f 30 May 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170516230934-3ca0cbd96a5a 16 May 2017 H1 Apache-2.0 Yes Details →
v0.0.0-20170426222228-3b3e77c4492a 26 Apr 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170426222228-3b3e77c4492a 26 Apr 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170405210435-86e2ee95b867 05 Apr 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170316182538-ff7a2868d681 16 Mar 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170308211215-9917b884bb45 08 Mar 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170302181526-4182ca013662 02 Mar 2017 H1 Apache-2.0 Yes Details →
v0.0.0-20170302164930-c04e3e6d0588 02 Mar 2017 H1 Apache-2.0 Yes Details →
v0.3.1-0.20170302164930-c04e3e6d0588 02 Mar 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170302164930-c04e3e6d0588 02 Mar 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170221221706-05cdbbc9c3cd 21 Feb 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170216162719-2768619f40a3 16 Feb 2017 H1 Apache-2.0 Yes Details →
v0.4.4 07 Jan 2017 H1 Apache-2.0 Yes Details →
v0.5.1-0.20170106182700-2549066cc4cf 06 Jan 2017 H1 Apache-2.0 Yes Details →
v0.4.3 03 Jan 2017 H1 Apache-2.0 Yes Details →
v0.5.0 14 Nov 2016 H1 Apache-2.0 Yes Details →
v0.4.2-0.20161105105001-efdf8078c0e0 05 Nov 2016 H1 Apache-2.0 Yes Details →
v0.4.2-0.20161026170834-3ca7b7284b09 26 Oct 2016 H1 Apache-2.0 Yes Details →
v0.4.2-0.20161023051100-02ce554179fe 23 Oct 2016 H1 Apache-2.0 Yes Details →
v0.0.0-20161001004805-c8aa8cf53cbc 01 Oct 2016 H1 Apache-2.0 Yes Details →
v0.4.2 01 Oct 2016 H1 Apache-2.0 Yes Details →
v0.4.1 30 Sep 2016 H1 Apache-2.0 Yes Details →
v0.4.0 21 Sep 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160810004455-b4d4ab6c96e1 10 Aug 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160803212613-a6fda67663e1 03 Aug 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160718170927-7a154ed8ec62 18 Jul 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160629180326-ecc2e2b5ed79 29 Jun 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160622223441-0517d5728ed4 22 Jun 2016 H1 Apache-2.0 Yes Details →
v0.0.0-20160609174042-0826dbe20108 09 Jun 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160609174042-0826dbe20108 09 Jun 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160609020126-bfab7201b36a 09 Jun 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160609001408-07265a36352d 09 Jun 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160608174353-a1f1fb449e34 08 Jun 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160607191608-4a1c4c9c856a 07 Jun 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160603161917-1a700552b2d7 03 Jun 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160526213722-2989c44576c7 26 May 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160524015921-2da7f31a682b 24 May 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160513211754-0256cee017d0 13 May 2016 H1 Apache-2.0 Yes Details →
v0.3.1-0.20160512204301-f9cfc7500e0f 12 May 2016 H1 Apache-2.0 Yes Details →
v0.3.0 10 May 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC5.0.20160510160440-658a25c4efe1 10 May 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC6 10 May 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC4.0.20160505175014-1f8e5d586346 05 May 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC5 05 May 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC4.0.20160505081250-26cbc805e126 05 May 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC4.0.20160504011048-6bd4f94199bc 04 May 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC2.0.20160429212401-134bdbcb9043 29 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC3 29 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC4 29 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC2.0.20160428201824-27469f01fe24 28 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC2.0.20160428175656-2166f845432a 28 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC1.0.20160427221706-f5b4b5f81000 27 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC2 27 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC1.0.20160427175858-04ec865b314f 27 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC1.0.20160427000448-2a3c301274b8 27 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC1.0.20160427000012-1976982685c4 27 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC1.0.20160426235922-01bbd532c6a0 26 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC1.0.20160422001530-12429b74d4e5 22 Apr 2016 H1 Apache-2.0 Yes Details →
v0.3.0-RC1 19 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160419224656-31f02ec0f70a 19 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160419203926-1abf013e6915 19 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160419180156-26a95ef5a33f 19 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160419175841-09f81717080f 19 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160415023805-11a4a060a6d3 15 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160415023804-0088233c935f 15 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160415023803-01a988a8177e 15 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160415023803-227092b94216 15 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160413035615-18fa8a2fc686 13 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160412213346-01da4b1a1114 12 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160412213346-229d64e0e053 12 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160411195726-22d46f847cc4 11 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160408012802-31851edf8187 08 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160405220852-1396e8890dd4 05 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160404185314-0a025196ce00 04 Apr 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160330093817-39c3f460062a 30 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160328230823-0a60261fabc0 28 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160324182654-041642fdb004 24 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160324173736-08c6669473a7 24 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160322182011-151b72c990d7 22 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160321184000-fe7742ca7075 21 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160318180640-1aad80743938 18 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160317162702-127c4f26cfc1 17 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160316011727-07b9f504e49c 16 Mar 2016 H1 Apache-2.0 Yes Details →
v0.2.1-0.20160311024446-206d02ab4d8c 11 Mar 2016 H1 — Yes Details →
v0.2.1-0.20160310053046-06ba32ea47f1 10 Mar 2016 H1 — Yes Details →
v0.2.1-0.20160310020347-00cadc9734bc 10 Mar 2016 H1 — Yes Details →
v0.2.1-0.20160301234502-2e331971de42 01 Mar 2016 H1 — Yes Details →
v0.2.1-0.20160227022623-08c0da745fa4 27 Feb 2016 H1 — Yes Details →
v0.0.0-20160226210347-1a668bb34d60 26 Feb 2016 H1 — Yes Details →
v0.2.0 25 Feb 2016 H1 — Yes Details →
v0.0.0-20160223195531-22c220d4d2a9 23 Feb 2016 H1 — Yes Details →
v0.0.0-20160222232753-1e48fd35ffbc 22 Feb 2016 H1 — Yes Details →
v0.0.0-20160219222010-13de903ee173 19 Feb 2016 H1 — Yes Details →
v0.0.0-20160218195053-1932c42d0689 18 Feb 2016 H1 — Yes Details →
v0.0.0-20160218034011-14edbe33e115 18 Feb 2016 H1 — Yes Details →
v0.0.0-20160218021734-0d10758c32f8 18 Feb 2016 H1 — Yes Details →
v0.0.0-20160217051113-1db128778d9e 17 Feb 2016 H1 — Yes Details →
v0.0.0-20160217014510-071976b47d37 17 Feb 2016 H1 — Yes Details →
v0.0.0-20160216063841-10865d231092 16 Feb 2016 H1 — Yes Details →
v0.0.0-20160216063841-1d9e37568095 16 Feb 2016 H1 — Yes Details →
v0.0.0-20160208214002-0fdb2d189119 08 Feb 2016 H1 — Yes Details →
v0.0.0-20160208214002-27c8737bdc93 08 Feb 2016 H1 — Yes Details →
v0.0.0-20160204205906-008c923b5821 04 Feb 2016 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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/docker/notary

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-9258: Docker Notary Signature Algorithm Not Matched to Key vulnerability 7.5 high 0.1.0 14 May 2022

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/docker/notary

Is github.com/docker/notary safe to use?

Vulert records 1 vulnerabilities for github.com/docker/notary in Go: 0 critical, 1 high, 0 medium and 0 low. 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/docker/notary's Vulert package health score?

Vulert scores github.com/docker/notary 70/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/docker/notary affected?

Yes. v0.6.1, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/docker/notary should I use?

v0.6.1 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/docker/notary have?

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

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

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