Security readout for executives and security teams
Plain-English summary
Caddy before 2.11.1 can accept unintended configuration changes through its local admin API when origin enforcement is not enabled. Malicious web content could cause a browser to submit a new Caddy JSON configuration to the local /load endpoint, changing server behavior. The business risk is unauthorized service reconfiguration, not direct data theft based on current sources.
Executive priority
Prioritize remediation for internet-facing services managed by Caddy and systems where administrators browse the web from the same host. This is a moderate-risk integrity issue with a vendor fix available. Treat it as a timely patching task rather than an emergency unless critical systems could be reconfigured through the local admin API.
Technical view
CVE-2026-27589 is a CWE-352 cross-origin request issue affecting Caddy versions before 2.11.1. The default local admin API at 127.0.0.1:2019 exposes POST /load, which replaces the running configuration. Without enforce_origin configured, cross-origin requests may be accepted and applied. CVSS v4.0 is 6.9, with high integrity impact and proof-of-concept evidence referenced.
Likely exposure
Exposure is most likely where Caddy versions before 2.11.1 run with the admin API enabled and origin enforcement not configured. Risk is higher on administrator workstations or servers where a browser can reach the local admin listener. The issue is not listed in CISA KEV in the provided data.
Exploitation context
The sources describe cross-origin configuration application via attacker-controlled web content and a local admin API. They do not state confirmed active exploitation. A public PoC attachment is referenced in the source bundle, so defenders should assume practical testing is possible while avoiding conclusions about real-world exploitation.
Researcher notes
Key conditions are Caddy <2.11.1, admin API availability, and missing enforce_origin. The vulnerable state-changing endpoint is /load and replaces the entire running configuration. Current provided evidence supports a fix in 2.11.1 and referenced PoC material, but does not support claims of active exploitation or broader affected products.
Mitigation direction
- Upgrade Caddy to version 2.11.1 or later.
- Enable admin API origin enforcement where applicable.
- Review Caddy vendor advisory and release notes for configuration-specific guidance.
- Restrict access to the admin API to trusted local contexts only.
- Monitor for unexpected Caddy configuration changes or admin listener changes.
Validation and detection
- Inventory Caddy instances and identify versions before 2.11.1.
- Check whether the admin API is enabled and listening locally.
- Review configuration for enforce_origin settings on the admin API.
- Compare running Caddy configuration against approved baselines.
- Review logs or change records for unexpected /load configuration updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-27589 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/caddyserver/caddy/security/advisories/GHSA-879p-475x-rqh2CVE reference · x_refsource_CONFIRM
- https://github.com/caddyserver/caddy/releases/tag/v2.11.1CVE reference · x_refsource_MISC
- https://github.com/user-attachments/files/25079818/poc.zipCVE reference · x_refsource_MISC
- https://github.com/user-attachments/files/25079820/PR_DESCRIPTION.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.