CVE-2026-67921
CSRF in Halo CMS <=2.25.4 enables remote code execution
Is CVE-2026-67921 being exploited?
Not confirmed. CVE-2026-67921 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-67921?
CVE-2026-67921 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67921?
Yes. A fix has been recorded for CVE-2026-67921. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67921 affect?
CVE-2026-67921 affects Halo CMS <=2.25.4, CorsConfigurer.java, CsrfConfigurer.java. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67921?
Upgrade Halo CMS to patched release (>=2.25.5) or apply vendor fix and harden admin CSRF protections.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
CSRF in CorsConfigurer/CsrfConfigurer allows remote attackers to execute arbitrary code on Halo CMS servers, enabling site takeover and data exfiltration.
Immediate action required