Nixpkgs Security Tracker

Login with GitHub

Details of issue NIXPKGS-2026-0355

NIXPKGS-2026-0355
published on 27 Feb 2026
updated 3 weeks, 2 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    7 packages
    • xcaddy
    • caddyfile-language-server
    • vimPlugins.nvim-treesitter-parsers.caddy
    • tree-sitter-grammars.tree-sitter-caddyfile
    • vscode-extensions.matthewpi.caddyfile-support
    • python313Packages.tree-sitter-grammars.tree-sitter-caddyfile
    • python314Packages.tree-sitter-grammars.tree-sitter-caddyfile
  • @LeSuisse accepted
  • @LeSuisse removed
    4 maintainers
    • @ryan4yin
    • @techknowlogick
    • @Br1ght0ne
    • @stepbrobd
  • @LeSuisse published on GitHub
Caddy's mTLS client authentication silently fails open when CA certificate file is missing or malformed

Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, two swallowed errors in `ClientAuthentication.provision()` cause mTLS client certificate authentication to silently fail open when a CA certificate file is missing, unreadable, or malformed. The server starts without error but accepts any client certificate signed by any system-trusted CA, completely bypassing the intended private CA trust boundary. Any deployment using `trusted_ca_cert_file` or `trusted_ca_certs_pem_files` for mTLS will silently degrade to accepting any system-trusted client certificate if the CA file becomes unavailable. This can happen due to a typo in the path, file rotation, corruption, or permission changes. The server gives no indication that mTLS is misconfigured. Version 2.11.1 fixes the vulnerability.

Affected products

caddy
  • ==< 2.11.1

Matching in nixpkgs

Ignored packages (7)

Package maintainers

Ignored maintainers (4)
Upstream advisory: https://github.com/caddyserver/caddy/security/advisories/GHSA-hffm-g8v7-wrv7