Vulnerability Database · Go · Package report
github.com/letsencrypt/boulder: vulnerability history, versions and safety
github.com/letsencrypt/boulder is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/letsencrypt/boulder v0.20261020.1 i
Updated on 23 Oct 2026
Good news: v0.20261020.1, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Key ecosystem project
- Community Active
What to do: Stay on v0.20261020.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.20261020.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.20261020.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 5,763 i
- Last release this month i
- Licence MPL-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/letsencrypt/boulder, 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.
- v0.20261020.2-0.20261021212842-f6d71764d4c5 21 Oct 2026
- v0.20261020.2-0.20261021170521-83a0fb449088 21 Oct 2026
- v0.20261020.2-0.20261020222217-2438a32086fe 20 Oct 2026
- v0.20261020.1 20 Oct 2026
- v0.20261020.1-0.20261020213051-5db65f49e38d 20 Oct 2026
- v0.20261020.1-0.20261020193500-ac98a6679957 20 Oct 2026
- v0.20261013.1-0.20261020152539-7d6dd30d3350 20 Oct 2026
- v0.20261020.0 20 Oct 2026
- v0.20261013.1-0.20261019234711-70d6effa7a17 19 Oct 2026
- v0.20261013.1-0.20261019184748-6f1e392cd024 19 Oct 2026
- v0.20261013.1-0.20261015025023-cf6406dd868f 15 Oct 2026
- v0.20261013.1-0.20261014220356-234f13a80ba3 14 Oct 2026
- v0.20261013.1-0.20261014203318-255d774719f7 14 Oct 2026
- v0.20261013.1-0.20261014183815-9e70762c7bb1 14 Oct 2026
- v0.20261013.1-0.20261013212916-7085ee897372 13 Oct 2026
- v0.20261006.1-0.20261008170801-f877538d2f0a 08 Oct 2026
- v0.20261013.0 08 Oct 2026
- v0.20261006.1-0.20261007211124-afe9fa5a4174 07 Oct 2026
- v0.20261006.1-0.20261006190724-18e542d216b3 06 Oct 2026
- v0.20260928.2-0.20261006165225-953014eb33ec 06 Oct 2026
- v0.20261006.0 06 Oct 2026
- v0.20260928.2-0.20261003000810-1578a1d051b8 03 Oct 2026
- v0.20260928.2-0.20261002221107-7f152dcb2ebb 02 Oct 2026
- v0.20260928.2-0.20261002112316-12cb328ccc4b 02 Oct 2026
- v0.20260928.2-0.20261001220239-8f7576fc6173 01 Oct 2026
- v0.20260928.2-0.20260930001717-7fe91f3324f2 30 Sep 2026
- v0.20260928.1 28 Sep 2026
- v0.20260921.1-0.20260928215056-74a49148270c 28 Sep 2026
- v0.20260928.0 28 Sep 2026
- v0.20260921.1-0.20260925171726-174cba842fb1 25 Sep 2026
- v0.20260921.1-0.20260923222505-884a968bfe08 23 Sep 2026
- v0.20260921.1-0.20260923162125-da514c9fa3dc 23 Sep 2026
- v0.20260921.1-0.20260922234632-e530f2a1056a 22 Sep 2026
- v0.20260921.1-0.20260921233232-d8d1974b3f62 21 Sep 2026
- v0.0.0-20260917042601-2a9172754e0c 17 Sep 2026
- v0.20260908.1-0.20260917042601-2a9172754e0c 17 Sep 2026
- v0.20260921.0 17 Sep 2026
- v0.20260908.1-0.20260915171115-e32c94d19706 15 Sep 2026
- v0.20260908.1-0.20260912003616-c5e0ef1e16f8 12 Sep 2026
- v0.0.0-20260908180821-a0cb60ea6acd 08 Sep 2026
- v0.20260901.1-0.20260908180821-a0cb60ea6acd 08 Sep 2026
- v0.20260908.0 08 Sep 2026
- v0.20260901.1-0.20260903211333-3d6e8a9c7c0e 03 Sep 2026
- v0.20260901.1-0.20260903145531-027096c92f39 03 Sep 2026
- v0.20260901.1-0.20260902215802-f2085ebb9662 02 Sep 2026
- v0.20260901.1-0.20260902202112-8621419fc182 02 Sep 2026
- v0.20260901.1-0.20260902195618-e1bb756a40ff 02 Sep 2026
- v0.20260901.1-0.20260902182736-076339dbdf69 02 Sep 2026
- v0.20260901.1-0.20260901235937-c5f1008d88f7 01 Sep 2026
- v0.20260901.1-0.20260901214930-062b996a6a64 01 Sep 2026
- v0.20260825.1-0.20260901195817-9ef4f9ddeae5 01 Sep 2026
- v0.20260901.0 01 Sep 2026
- v0.20260825.1-0.20260828164936-64602f551557 28 Aug 2026
- v0.20260825.1-0.20260826213352-e05784ba9436 26 Aug 2026
- v0.20260817.1-0.20260821200618-6d0e74df42a5 21 Aug 2026
- v0.20260825.0 21 Aug 2026
- v0.20260817.1-0.20260820162821-a6ef070ad715 20 Aug 2026
- v0.20260817.1-0.20260819221622-76f6514b9612 19 Aug 2026
- v0.20260811.1-0.20260817194441-9ae976ca6b7d 17 Aug 2026
- v0.20260817.0 17 Aug 2026
- v0.20260811.1-0.20260814220453-4aeb577586d3 14 Aug 2026
- v0.20260811.1-0.20260813235345-719414883549 13 Aug 2026
- v0.20260804.1-0.20260811183039-c67fdf6c3c7d 11 Aug 2026
- v0.20260811.0 11 Aug 2026
- v0.20260804.1-0.20260807165336-2d00c8e27919 07 Aug 2026
- v0.20260729.1-0.20260804172034-23902933e011 04 Aug 2026
- v0.20260804.0 04 Aug 2026
- v0.0.0-20260731130133-7bf6f1013016 31 Jul 2026
- v0.20260729.1-0.20260731130133-7bf6f1013016 31 Jul 2026
- v0.20260729.1-0.20260730223615-8f28a3edfb25 30 Jul 2026
- v0.20260729.1-0.20260730004048-d551d4be8023 30 Jul 2026
- v0.0.0-20260729235012-af5bd96d6961 29 Jul 2026
- v0.20260728.1-0.20260729235012-af5bd96d6961 29 Jul 2026
- v0.20260729.0 29 Jul 2026
- v0.20260728.1-0.20260728224540-3ebcb61ba0cc 28 Jul 2026
- v0.20260728.1-0.20260728171634-e62c93d78590 28 Jul 2026
- v0.20260720.1-0.20260727190421-d79dd218e746 27 Jul 2026
- v0.20260728.0 27 Jul 2026
- v0.20260720.1-0.20260724180358-9dca7a715e02 24 Jul 2026
- v0.20260720.1-0.20260723190331-2a47b9c36f15 23 Jul 2026
- v0.20260720.1-0.20260722160253-ab3945ae3737 22 Jul 2026
- v0.20260720.1-0.20260721165952-11ba9c4e191a 21 Jul 2026
- v0.20260720.1-0.20260721002122-6e73287c4c19 21 Jul 2026
- v0.0.0-20260720195017-b82d6679876a 20 Jul 2026
- v0.20260713.1-0.20260720195017-b82d6679876a 20 Jul 2026
- v0.20260720.0 20 Jul 2026
- v0.20260713.1-0.20260717203156-1c9b7e03018f 17 Jul 2026
- v0.20260630.1-0.20260716221452-3faa24f52f13 16 Jul 2026
- v0.20260713.1-0.20260716203749-048a7227af30 16 Jul 2026
- v0.20260713.1-0.20260714171045-ea49e42487a0 14 Jul 2026
- v0.0.0-20260713221220-f876e77b5e31 13 Jul 2026
- v0.20260707.1-0.20260713221220-f876e77b5e31 13 Jul 2026
- v0.20260713.0 13 Jul 2026
- v0.20260707.1-0.20260709163207-c7a466aa6626 09 Jul 2026
- v0.20260707.0 07 Jul 2026
- v0.20260630.1-0.20260707163948-8af69ff6fa57 07 Jul 2026
- v0.20260630.1-0.20260702221647-055b129893b0 02 Jul 2026
- v0.20260623.1-0.20260629171229-57551d14aaed 29 Jun 2026
- v0.20260630.0 29 Jun 2026
- v0.20260623.1-0.20260629032909-abfceb5f05ed 29 Jun 2026
- v0.20260615.1-0.20260622223936-f9e80fb1874d 22 Jun 2026
- v0.20260623.0 22 Jun 2026
- v0.20260615.1-0.20260622164706-3b540a97c311 22 Jun 2026
- v0.20260608.1-0.20260615200211-5e88babd5def 15 Jun 2026
- v0.20260615.0 15 Jun 2026
- v0.20260602.1-0.20260605200738-e4f4650962ff 05 Jun 2026
- v0.20260608.0 05 Jun 2026
- v0.0.0-20260604162240-c3c9094975ec 04 Jun 2026
- v0.20260526.1-0.20260602172121-7c555b014353 02 Jun 2026
- v0.20260602.0 02 Jun 2026
- v0.20260526.1-0.20260528183522-4c3d96cc4832 28 May 2026
- v0.20260518.1-0.20260526170354-2517a8f9a031 26 May 2026
- v0.20260526.0 26 May 2026
- v0.20260512.1-0.20260518220728-04140d07ee5a 18 May 2026
- v0.20260518.0 18 May 2026
- v0.20260504.1-0.20260512003646-c62e79673444 12 May 2026
- v0.20260512.0 12 May 2026
- v0.20260428.1-0.20260505000040-a8b77ac959c7 05 May 2026
- v0.20260504.0 05 May 2026
- v0.20260420.1-0.20260428204030-350fe31313c1 28 Apr 2026
The newest 120 of 2,263 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/letsencrypt/boulder
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
Questions
About github.com/letsencrypt/boulder
Is github.com/letsencrypt/boulder safe to use?
Vulert has no vulnerabilities on record for github.com/letsencrypt/boulder 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/letsencrypt/boulder's Vulert package health score?
Vulert scores github.com/letsencrypt/boulder 96/100, which reads as healthy. 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/letsencrypt/boulder affected?
No. v0.20261020.1, 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.
How many vulnerabilities does github.com/letsencrypt/boulder have?
0 vulnerabilities are recorded for github.com/letsencrypt/boulder 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/letsencrypt/boulder vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/letsencrypt/boulder 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/letsencrypt/boulder 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/letsencrypt/boulder for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/letsencrypt/boulder version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.