halo-dev Halo up to 2.25.4/2.26.1 SpEL ReplyNotificationSubscriptionHelper.java neutralization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 1.06 |
Summary
A vulnerability identified as critical has been detected in halo-dev Halo up to 2.25.4/2.26.1. Affected by this vulnerability is an unknown functionality of the file application/src/main/java/run/halo/app/content/comment/ReplyNotificationSubscriptionHelper.java of the component SpEL Handler. Performing a manipulation results in neutralization. This vulnerability is cataloged as CVE-2026-97182. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in halo-dev Halo up to 2.25.4/2.26.1. It has been classified as critical. This affects some unknown functionality of the file application/src/main/java/run/halo/app/content/comment/ReplyNotificationSubscriptionHelper.java of the component SpEL Handler. The manipulation with an unknown input leads to a neutralization vulnerability. CWE is classifying the issue as CWE-707. The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.
It is possible to read the advisory at note-hxlab.wetolink.com. This vulnerability is uniquely identified as CVE-2026-97182. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at note-hxlab.wetolink.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: NeutralizationCWE: CWE-707 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/24/2026 Advisory disclosed09/24/2026 VulDB entry created
09/24/2026 VulDB entry last update
Sources
Advisory: note-hxlab.wetolink.comStatus: Not defined
CVE: CVE-2026-97182 (🔒)
GCVE (CVE): GCVE-0-2026-97182
GCVE (VulDB): GCVE-100-409299
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/24/2026 09:03Changes: 09/24/2026 09:03 (55)
Complete: 🔍
Submitter: hiro
Cache ID: 216::103
Submit
Accepted
- Submit #907507: halo-dev Halo 2.15.0 through 2.25.4 Improper Neutralization of Special Elements used in an Expressio (by hiro)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.