CISA list

Caddy versions

Caddy: update to 2.11.9. 1 and older no longer get fixes.

Data: .

Which Caddy branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected.

Which Caddy branch to run
BranchStatusNewest safe releaseUpgrade to
217 CVE records that this page readsFixes, no end date announced2.11.92.11.9 (this branch)
1Ended on 1 July 2020None, the branch has ended2.11.9 (move to 2)

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 17 CVE records that the CVE Numbering Authority GitHub_M (as the CVE List names it) published and that name Caddy. The fixes are from them. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here.

Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)