Quick answers
- Is CVE-2026-97182 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97182 being exploited in the wild.
- How severe is CVE-2026-97182?
- High severity, with a CVSS score of 7.3, published 24 September 2026.
- Which products and versions are affected?
- Halo-Dev Halo 2.15.0 through 2.25.4; also affects 2.26.1.
- Is there a fix for CVE-2026-97182?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-97182 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-97182?
- Check whether you run Halo-Dev Halo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Spring Expression Language (SpEL) injection vulnerability exists in ReplyNotificationSubscriptionHelper.java where user-supplied email addresses from guest comments are interpolated directly into SpEL expression strings without escaping. An attacker can inject SpEL operators (e.g., via email "a'||true||'a@example.com") to create an expression that always evaluates to true, matching all comment reply notifications regardless of intended recipient. The vulnerability requires guest comments enabled and reply notification configuration; exploitation is unauthenticated and remotely triggerable.
Affected products
- halo-dev Halo 2.15.0 through 2.25.4; also affects 2.26.1
Timeline
- 2026-09-24: disclosed
- 2026-09-24: exploited: public disclosure with proof of concept available