Skip to main content
Vulnerability Database/CVE-2026-102367

CVE-2026-102367: mall4j Auth Bypass Vulnerability

CVE-2026-102367 is an authentication bypass flaw in mall4j that allows disabled users to maintain access through token refresh. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-102367 Overview

CVE-2026-102367 is an insufficient session expiration vulnerability [CWE-613] affecting mall4j through version 4.0, an open-source Java e-commerce platform maintained by gz-yami. The flaw resides in the POST /token/refresh endpoint, which fails to validate the enabled flag on a user account before issuing a new session token. Disabled accounts can therefore indefinitely renew their access tokens, defeating the administrative control intended to revoke access.

Critical Impact

A disabled user retaining a valid refresh token can maintain persistent authenticated access to the mall4j application, undermining account deactivation as a security control.

Affected Products

  • mall4j (gz-yami) versions through 4.0
  • yami-shop-security-common module TokenController component
  • yami-shop-security-common module TokenStore component

Discovery Timeline

  • 2026-09-29 - CVE-2026-102367 published to the National Vulnerability Database (NVD)
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-102367

Vulnerability Analysis

The vulnerability sits in the token refresh workflow of the mall4j security module. When a client submits a refresh token to POST /token/refresh, the TokenController delegates to TokenStore to issue a new access token. The refresh logic verifies the token's cryptographic validity and expiration but does not re-check whether the underlying user account is still active. As a result, an administrator disabling a user through the platform's management interface does not terminate that user's ability to obtain fresh access tokens.

The issue is a business logic and access control failure rather than a memory or injection defect. It permits horizontal persistence: any attacker or insider who obtained a refresh token while the account was enabled can continue to authenticate long after the account has been disabled.

Root Cause

The root cause is missing state validation in the refresh flow. The TokenStore implementation (see lines 121-130 of TokenStore.java) does not query the user's enabled attribute before minting a new token. The TokenController similarly performs no account-status gate.

Attack Vector

Exploitation requires an attacker to possess a valid refresh token issued while the target account was still enabled. The attacker submits the refresh token to the /token/refresh endpoint over the network and receives a new access token, regardless of the account's current disabled status. A public proof-of-concept demonstrating the bypass is available at the GitHub PoC repository.

No synthetic exploitation code is reproduced here. Refer to the VulnCheck advisory and the linked PoC for reproduction details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-102367

Indicators of Compromise

  • Successful POST /token/refresh responses associated with user identifiers whose account status is enabled=false in the database.
  • Access token issuance events for accounts that were administratively disabled prior to the refresh timestamp.
  • Repeated refresh requests from a single client sustaining a session that outlives an account-disable action.

Detection Strategies

  • Correlate application audit logs for account-disable events with subsequent /token/refresh successes tied to the same user identifier.
  • Instrument the TokenStore refresh path to log the user's enabled flag at issuance time and alert when a token is minted for a disabled principal.
  • Baseline expected refresh frequency per account and flag long-lived sessions that persist beyond typical inactivity windows.

Monitoring Recommendations

  • Forward mall4j application and access logs to a centralized analytics platform and query for refresh events by disabled accounts.
  • Monitor administrative changes to the sys_user (or equivalent) table alongside authentication telemetry to identify persistence after deactivation.
  • Alert on refresh token reuse patterns that continue beyond a defined administrative revocation event.

How to Mitigate CVE-2026-102367

Immediate Actions Required

  • Audit all currently active sessions and invalidate refresh tokens for any account that has been disabled.
  • Patch the TokenStore refresh logic to reload the user entity and reject the request when enabled is false.
  • Rotate signing keys used for refresh tokens to force reauthentication across the user base.

Patch Information

As of publication, no fixed release is referenced in the NVD entry. Operators should track the mall4j GitHub repository for upstream commits addressing the TokenController and TokenStore components and review the VulnCheck advisory for remediation guidance.

Workarounds

  • Add a server-side filter or interceptor in front of /token/refresh that loads the principal from the user store and returns 401 when the account is disabled.
  • Shorten refresh token lifetime and require reauthentication more frequently to limit the window of abuse.
  • Maintain a server-side token revocation list and explicitly revoke refresh tokens when an administrator disables an account.
bash
# Example reverse-proxy rule to block refresh endpoint pending patch
# NGINX snippet - deny /token/refresh until account status enforcement is deployed
location = /token/refresh {
    return 403;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.