CVE-2026-45692

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-06-23 18:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-25 23:10 UTC Last updatedMost recent change to the record

Details

Published

2026-06-23 18:17 UTC

Last modified

2026-10-25 23:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-187

Record status

Modified

Affected

• Caddyserver Caddy < 2.11.3

Attack profile CVSS 3.1 · 5.4

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-45692.md and follow it. Check whether this project is affected by CVE-2026-45692. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

More options