Vulnerability Database · Go · github.com/coredns/caddy · Version

github.com/coredns/caddy v0.7.1

No vulnerabilities in this database cover v0.7.1.

Every vulnerability Vulert holds for github.com/coredns/caddy was tested against this version and none of them covers it. That is the good answer, not a guarantee — the package page shows which versions are affected.

Critical 0 High 0 Medium 0 Low 0 Unrated 0

All github.com/coredns/caddy versions & vulnerabilities → Source repository Search the database for this package →

Released 02 Jun 2015 Licence Apache-2.0 Also known from other sources 0 Newer releases 72 Database updated 23/Oct/2026

Release and licence data published by the Go module proxy. 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.

Scan your app free →

01 Vulnerabilities affecting this version

github.com/coredns/caddy v0.7.1 vulnerabilities

No vulnerability in the Vulert database covers github.com/coredns/caddy v0.7.1. See the versions that are affected →

Looking for another version, or everything Vulert holds for github.com/coredns/caddy?

All versions → Full vulnerability list →

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 v0.7.1

Is github.com/coredns/caddy v0.7.1 vulnerable?

No. No vulnerability in the Vulert database covers github.com/coredns/caddy v0.7.1. Every vulnerability Vulert holds for github.com/coredns/caddy was tested against this release and none of them covers it — the good answer, though not a guarantee, since new vulnerabilities are published for packages all the time.

Is v0.7.1 the latest release of github.com/coredns/caddy?

No. v0.7.1 was published 02 Jun 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.