# CVE-2026-105098: Omega Solution CoinEx Crypto information disclosure in Support Ticket API

Source: https://junglewise.ai/threats/cve-2026-105098-a-security-flaw-has-been-discovered-in-omega-solution-coinex  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-04. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-105098 · Severity: medium · CVSS 4.3 · Published 2026-10-04

Omega Solution CoinEx Crypto is a cryptocurrency exchange platform with a support ticket system. The Support Ticket API endpoint inadvertently exposes sensitive customer account data including password hashes, internal user IDs, and verification status when retrieving support tickets. An authenticated attacker can retrieve this information remotely, potentially enabling offline password cracking and account compromise.

Technologies: [Omega Solution CoinEx Crypto](https://junglewise.ai/threats/technologies/coinex-crypto). Vendors: [Omega Solution](https://junglewise.ai/threats/vendors/omega-solution).

## 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

## References

- [https://github.com/4m3rr0r/PoCVulDb/issues/26](https://github.com/4m3rr0r/PoCVulDb/issues/26)
- [https://vuldb.com/cve/CVE-2026-105098](https://vuldb.com/cve/CVE-2026-105098)

## Related threats

- [Omega Solution CoinEx Crypto authorization bypass in Customer Information API](https://junglewise.ai/threats/cve-2026-105097-a-vulnerability-was-identified-in-omega-solution-coinex-crypto)
- [Omega Solution CoinEx Crypto authorization bypass in Customer Profile API](https://junglewise.ai/threats/cve-2026-105096-a-vulnerability-was-determined-in-omega-solution-coinex-crypto)