Skip to main content
VulnerabilityPublished Updated

CVE-2026-45692: caddyserver caddy · Partial String Comparison

Affects caddyserver caddySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.11.3 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.11.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade caddy and caddyserver/caddy to 2.11.3.

Affected software

ProductAffectedFixed in
caddyservercaddyAffected
  • >=2.4.0 <2.11.3
Fixed in
  • 2.11.3
GitHubcaddyserver/caddypkg:github/caddyserver/caddyOther threatsAffected
  • >=2.4.0 <2.11.3
Fixed in
  • 2.11.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade caddyserver caddy to version 2.11.3 or later, where this vulnerability is fixed. Patch status is confirmed by the description stating the fix is in 2.11.3. No other mitigation or temporary workaround is indicated.

Description

Caddy is an extensible server platform that uses TLS by default. From 2.4.0 until 2.11.3, the authorization layer and the /config traversal layer do not agree on what object the path refers to. In this case, a path authorized for one config object is accepted, but then resolves to a different config object during traversal. This happens because the authorization layer uses string prefix matching and the /config traversal layer parses array indices numerically using strconv.Atoi(). This vulnerability is fixed in 2.11.3.

References

Community reviews

Loading reviews…