Finding and attribution
In affected configurations, try_files cleans a request such as /.env/./ into /.env while path matchers still evaluate the original /.env/ path. This can bypass suffix, exact-path, glob or anchored-regex rules before the rewrite and disclose static files such as .env files, backups or configuration. Prefix and */.* rules still block, and nothing is executed.
Product: Caddy (try_files, file_server, php_fastcgi and FrankenPHP php_server configurations). AI system: Anthropic OSS Scanner (model not specified for this finding). Team / organization: Anthropic and Caddy maintainers.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): The Caddy advisory explicitly says the issue was discovered by Anthropic's OSS Scanner and supplies scanner identifier ANT-2026-VAGWNYYZ. The Anthropic program sources establish model-based scanning, but do not identify the model used for this case or the human validation steps.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The primary advisory establishes a publicly disclosed vulnerability and scanner attribution; it does not establish exploitation in the wild or zero-day status. No CVE is known, so this record is identified by GHSA.
Remediation status: fix documented. Fixed in Caddy 2.11.8 by preserving the trailing slash on cleaned candidates so slash-terminated file paths do not match regular files. Deployed patch status is not checked.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 4 Nov 2026. AI attribution dated 4 Nov 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: data disclosure.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Case-level evidence: data disclosure.
Prerequisites / affected scope: An unauthenticated client can request a dot-segment path that bypasses suffix/exact-path rules and retrieve otherwise blocked static files. The advisory explicitly says nothing is executed..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: Fixed in Caddy 2.11.8 by preserving the trailing slash on cleaned candidates so slash-terminated file paths do not match regular files. Deployed patch status is not checked.