Quick answers
- Is CVE-2026-105098 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105098 being exploited in the wild.
- How severe is CVE-2026-105098?
- Medium severity, with a CVSS score of 4.3, published 4 October 2026.
- Which products and versions are affected?
- Omega Solution CoinEx Crypto 2025.
- Is there a fix for CVE-2026-105098?
- No fixed version is recorded yet. Implement response DTOs that explicitly whitelist only necessary fields (id, name, profileImage) and remove sensitive fields such as password, userId, roleId, isActivated, isVerified, and lastOnline from all API responses.</anigation> </invoke> 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-105098 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-105098?
- Check whether you run Omega Solution CoinEx Crypto 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.
How to fix
Implement response DTOs that explicitly whitelist only necessary fields (id, name, profileImage) and remove sensitive fields such as password, userId, roleId, isActivated, isVerified, and lastOnline from all API responses.</anigation> </invoke>
Technical details
The GET /ticket/customer endpoint in the Support Ticket API returns the complete customer object instead of filtering sensitive fields, disclosing bcrypt password hashes, internal user IDs, role IDs, and account metadata unrelated to ticket retrieval. The vulnerability requires authentication as a customer but allows any authenticated user to extract their own sensitive data. The API violates the principle of least privilege by exposing fields never needed for ticket display.
Affected products
- Omega Solution CoinEx Crypto 2025
Timeline
- 2026-10-04: disclosed: CVE published to NVD
- 2026-07-17: other: PoC disclosed on GitHub