VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/coredns/caddy: vulnerability history, versions and safety

github.com/coredns/caddy 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/coredns/caddy vulnerabilities

Vulert verdict on github.com/coredns/caddy v1.1.4 i

Updated on 23 Oct 2026

Good news: v1.1.4, the version you would install today, has no known vulnerabilities.

Package health score 61/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on v1.1.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.1.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 22 i
  • OpenSSF scorecard 1/10 i
  • Last release 9 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/coredns/caddy, 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.1.4 29 Dec 2025 none Apache-2.0 — Details →
v1.1.4-0.20250930002214-15135a999495 30 Sep 2025 none Apache-2.0 — Details →
v1.1.3 20 Sep 2025 none Apache-2.0 — Details →
v1.1.2 19 Sep 2025 none Apache-2.0 — Details →
v1.1.2-0.20250919154045-fabd98a6df6e 19 Sep 2025 none Apache-2.0 — Details →
v0.0.0-20241029205200-8de985351a98 29 Oct 2024 none Apache-2.0 — Details →
v1.1.2-0.20241029205200-8de985351a98 29 Oct 2024 none Apache-2.0 — Details →
v1.1.2-0.20221011154453-b1ad5f2b4194 11 Oct 2022 none Apache-2.0 — Details →
v1.1.2-0.20211011014022-028c1b2b9603 11 Oct 2021 none Apache-2.0 — Details →
v1.1.2-0.20211008135337-8ed50a359300 08 Oct 2021 none Apache-2.0 — Details →
v0.0.0-20210512162810-8adcfe62194e 12 May 2021 none Apache-2.0 — Details →
v1.1.1 12 May 2021 none Apache-2.0 — Details →
v1.1.1-0.20210512162810-8adcfe62194e 12 May 2021 none Apache-2.0 — Details →
v1.1.0 21 Jul 2020 none Apache-2.0 — Details →
v0.11.6-0.20190306213507-47b78714b8af 06 Mar 2019 none Apache-2.0 — Details →
v0.11.5 04 Mar 2019 none Apache-2.0 — Details →
v0.11.4 15 Feb 2019 none Apache-2.0 — Details →
v0.11.3 05 Feb 2019 none Apache-2.0 — Details →
v0.11.3-0.20190126072017-0ecc5c46bff9 26 Jan 2019 none Apache-2.0 — Details →
v0.11.2 16 Jan 2019 none Apache-2.0 — Details →
v0.11.2-0.20181206003323-09188981c477 06 Dec 2018 none Apache-2.0 — Details →
v0.11.1 12 Nov 2018 none Apache-2.0 — Details →
v0.11.1-0.20180902212810-d47b041923da 02 Sep 2018 none Apache-2.0 — Details →
v0.11.1-0.20180612230053-6965075825dc 12 Jun 2018 none Apache-2.0 — Details →
v0.11.0 10 May 2018 none Apache-2.0 — Details →
v0.10.14 20 Apr 2018 none Apache-2.0 — Details →
v0.10.13 18 Apr 2018 none Apache-2.0 — Details →
v0.10.13-0.20180402141721-917a60409417 02 Apr 2018 none Apache-2.0 — Details →
v0.10.12 27 Mar 2018 none Apache-2.0 — Details →
v0.10.11 20 Feb 2018 none Apache-2.0 — Details →
v0.10.11-0.20180116183749-e9515425e0b1 16 Jan 2018 none Apache-2.0 — Details →
v0.10.11-0.20171022222744-fc75527eb5ea 22 Oct 2017 none Apache-2.0 — Details →
v0.10.10 09 Oct 2017 none Apache-2.0 — Details →
v0.10.10-0.20170922144555-0a624f87ffd8 22 Sep 2017 none Apache-2.0 — Details →
v0.10.9 12 Sep 2017 none Apache-2.0 — Details →
v0.10.8 08 Sep 2017 none Apache-2.0 — Details →
v0.10.7 25 Aug 2017 none Apache-2.0 — Details →
v0.10.6 28 Jul 2017 none Apache-2.0 — Details →
v0.10.5 27 Jul 2017 none Apache-2.0 — Details →
v0.10.4 28 Jun 2017 none Apache-2.0 — Details →
v0.10.3 19 May 2017 none Apache-2.0 — Details →
v0.10.2 02 May 2017 none Apache-2.0 — Details →
v0.10.1 02 May 2017 none Apache-2.0 — Details →
v0.10.0 20 Apr 2017 none Apache-2.0 — Details →
v0.9.5 24 Jan 2017 none Apache-2.0 — Details →
v0.9.4 21 Dec 2016 none Apache-2.0 — Details →
v0.9.3 28 Sep 2016 none Apache-2.0 — Details →
v0.9.2 20 Sep 2016 none Apache-2.0 — Details →
v0.9.1 17 Aug 2016 none Apache-2.0 — Details →
v0.9.0 19 Jul 2016 none Apache-2.0 — Details →
v0.8.3 26 Apr 2016 none Apache-2.0 — Details →
v0.8.3-0.20160423154948-6f5cff539367 23 Apr 2016 none Apache-2.0 — Details →
v0.8.2 25 Feb 2016 none Apache-2.0 — Details →
v0.8.2-0.20160218011103-1ef7f3c4b1c4 18 Feb 2016 none Apache-2.0 — Details →
v0.8.1 12 Jan 2016 none Apache-2.0 — Details →
v0.8.1-0.20151206172332-41bdd77545c8 06 Dec 2015 none Apache-2.0 — Details →
v0.8.0 04 Dec 2015 none Apache-2.0 — Details →
v0.7.7-0.20151115010025-7d46a7d5f426 15 Nov 2015 none Apache-2.0 — Details →
v0.7.7-0.20151108002544-8628a50b7dd2 08 Nov 2015 none Apache-2.0 — Details →
v0.7.7-0.20151103040631-295d21f37de8 03 Nov 2015 none Apache-2.0 — Details →
v0.7.7-0.20151027064324-0f19df8a81e0 27 Oct 2015 none Apache-2.0 — Details →
v0.7.6 28 Sep 2015 none Apache-2.0 — Details →
v0.7.5 05 Aug 2015 none Apache-2.0 — Details →
v0.7.4 30 Jul 2015 none Apache-2.0 — Details →
v0.7.3 15 Jul 2015 none Apache-2.0 — Details →
v0.7.2 01 Jul 2015 none Apache-2.0 — Details →
v0.7.2-0.20150607002736-13db60d38245 07 Jun 2015 none Apache-2.0 — Details →
v0.7.1 02 Jun 2015 none Apache-2.0 — Details →
v0.7.0 25 May 2015 none Apache-2.0 — Details →
v0.6.0 06 May 2015 none Apache-2.0 — Details →
v0.5.1 30 Apr 2015 none Apache-2.0 — Details →
v0.5.0 28 Apr 2015 none Apache-2.0 — Details →

All 72 versions Vulert tracks for this package. 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/coredns/caddy

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/coredns/caddy

Is github.com/coredns/caddy safe to use?

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

Vulert scores github.com/coredns/caddy 61/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).

Is the latest version of github.com/coredns/caddy affected?

No. v1.1.4, 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.

Which version of github.com/coredns/caddy should I use?

v1.1.4 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/coredns/caddy have?

0 vulnerabilities are recorded for github.com/coredns/caddy 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/coredns/caddy vulnerabilities disclosed?

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

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