Quick answers
- Is CVE-2026-102367 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102367 being exploited in the wild.
- How severe is CVE-2026-102367?
- Medium severity, with a CVSS score of 5.4, published 29 September 2026.
- Which products and versions are affected?
- Gz-Yami Mall4j through 4.0.
- Is there a fix for CVE-2026-102367?
- 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-102367 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102367?
- Check whether you run Gz-Yami Mall4j 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
The POST /token/refresh endpoint fails to validate the enabled flag on user accounts when issuing new session tokens, allowing disabled accounts to refresh valid tokens indefinitely. This is an authorization bypass in the session management logic that requires the attacker to possess a previously valid token from a now-disabled account. The vulnerability affects the core authentication layer across all authenticated functionality.
Affected products
- gz-yami mall4j through 4.0
Timeline
- 2026-09-29: disclosed