CVE-2026-67921: halo-cms · Cross-Site Request Forgery (CSRF)
Affects halo-cmsSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 2.25.5 as a priority.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.25.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
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
Upgrade com.halo-dev/halo-cms to 2.25.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.halo-dev/halo-cmspkg:maven/com.halo-dev/halo-cmsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
CVE-2026-67921 is a critical Cross-Site Request Forgery (CSRF) vulnerability in Halo CMS versions prior to 2.25.5. It affects the CorsConfigurer.java and CsrfConfigurer.java components, allowing remote attackers to execute arbitrary code. The vulnerability has a high CVSS score of 9.3, indicating severe impact on confidentiality and integrity.