CVE-2025-56266: n/a
Source CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 2.8% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Sep 2025
Detectable: evidence found.
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
1. Immediate network-level controls: Restrict access to the Avigilon ACM web interface to trusted internal networks only. Implement firewall rules and VPN access to prevent exposure to the internet. 2. Input validation and monitoring: Although a patch is not yet available, organizations should monitor HTTP requests to the ACM interface for suspicious Host header values and anomalous traffic patterns. 3. Segmentation: Isolate the ACM servers within a secure network segment with strict access controls to limit lateral movement in case of compromise. 4. Vendor engagement: Engage with Avigilon support to obtain information on patches or mitigations and apply updates as soon as they become available. 5. Incident response readiness: Prepare to detect and respond to potential exploitation attempts by enabling detailed logging and monitoring of ACM server activity. 6. Temporary workaround: If feasible, implement web application firewalls (WAF) or reverse proxies that validate and sanitize Host headers before forwarding requests to the ACM server. 7. Review and harden authentication and authorization mechanisms on the ACM platform to reduce the impact of potential code execution.
Description
A Host Header Injection vulnerability in Avigilon ACM v7.10.0.20 allows attackers to execute arbitrary code via supplying a crafted URL.
References
- github.com/nikolas-ch/CVEs/tree/main/AvigilonACM_v7.10.0.20/ (opens in a new tab)
- github.com/nikolas-ch/CVEs/tree/main/AvigilonACM_v7.10.0.20/HostHeaderInjection (opens in a new tab)
- github.com/nikolas-ch/CVEs/blob/main/AvigilonACM_v7.10.0.20/HostHeaderInjection/HostHeaderInjection.txt (opens in a new tab)