https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T21:38:28.686095+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cleanstart-2026-wk22640 CLEANSTART-2026-WK22640 — Caddy is an extensible server platform that uses TLS by default 2026-10-02T21:38:28.764351+00:00

Affected: CleanStart: caddy

Security vulnerability affects the caddy package. Caddy is an extensible server platform that uses TLS by default.

 https://cve.radiocsirt.org/vuln/euvd-2026-330723 EUVD-2026-330723 2026-10-02T21:38:28.764404+00:00 EUVD-2026-330723 https://cve.radiocsirt.org/vuln/fkie_cve-2026-45692 fkie_cve-2026-45692 2026-10-02T21:38:28.764420+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-x5w9-xh9r-mvfc GHSA-x5w9-xh9r-mvfc — Caddy: Remote Admin Authorization Bypass in `/config` API via Array Index Normalization 2026-10-02T21:38:28.764446+00:00

Affected: Go: github.com/caddyserver/caddy/v2

This report is not about a normal textual prefix-expansion case.

The issue here is that 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.

## AI Disclosure

The reporter used an LLM to help review the code, reason about the behavior, and help draft this report. The reporter manually reproduced and validated the issue locally, confirmed the relevant source paths, and captured the requests and responses below.

## Summary

A remote admin client certificate restricted to the following path:

```text /config/apps/http/servers/srv/routes/0 ``` can still read and modify a different array element by requesting:

/config/apps/http/servers/srv/routes/01

This happens because:

- the authorization layer uses string prefix matching - the /config traversal layer parses array indices numerically using strconv.Atoi()

So:

- authorization sees /.../01 as matching /.../0 - traversal resolves 01 to numeric index 1 - the request therefore targets routes[1], not routes[0]

This is not just a prefix-match quirk. It is an authorization-to-object mismatch.

## Why This Is In Scope

This is a security bug in Caddy's own code:

- no browser behavior is involved - no dependency bug is involved - no external system compromise is involved - no third-party s…

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-45692 UBUNTU-CVE-2026-45692 2026-10-02T21:38:28.764626+00:00

Affected: Ubuntu:Pro:24.04:LTS: caddy, Ubuntu:25.10: caddy, Ubuntu:Pro:26.04:LTS: caddy

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.