CVE-2025-44595: Halo · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
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 26 Oct 2026.
What to do
AI-suggested
European organizations should implement the following specific mitigations: 1) Immediately audit and sanitize all user inputs in the /halo_host/archives/{name} endpoint, ensuring proper encoding and escaping of special characters to prevent script injection. 2) Deploy Web Application Firewalls (WAFs) with rules targeting reflected XSS patterns on the affected URL paths to block malicious payloads. 3) Educate users and staff about the risks of clicking untrusted links, especially those purporting to come from internal or trusted sources. 4) Monitor web server logs for unusual or suspicious requests to the vulnerable endpoint that may indicate exploitation attempts. 5) Engage with the Halo vendor or community to obtain or request patches or updates addressing this vulnerability as soon as they become available. 6) Implement Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce the impact of potential XSS attacks. 7) Regularly review and update incident response plans to include scenarios involving XSS exploitation and data leakage. These steps go beyond generic advice by focusing on the specific vulnerable endpoint, user education, and layered defenses.
Description
Halo v2.20.17 and before is vulnerable to Cross Site Scripting (XSS) in /halo_host/archives/{name}.