CVE-2026-1842

The record

HyperCloud versions 2.3.5 through 2.6.8 improperly allowed refresh tokens to be used directly for resource access and failed to invalidate previously issued access tokens when a refresh token was used. Because refresh tokens have a significantly longer lifetime (default one year), an authenticated client could use a refresh token in place of an access token to maintain long-term access without token rotation. Additionally, old access tokens remained valid after refresh, enabling concurrent or extended use beyond intended session boundaries. This vulnerability could allow prolonged unauthorized access if a token is disclosed.

Affected packages

Related vulnerabilities

• CVE-2026-55250 Maravel, a PHP framework oriented towards dependency injection, prior to version 10.74.0… CWE-613
• CVE-2026-86215 A vulnerability was identified in Mstfakts College-Management-System. CWE-613
• CVE-2026-55513 nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. CWE-613
• CVE-2026-61608 SolidInvoice is an open-source invoicing platform. CWE-613
• CVE-2026-84480 WWBN AVideo fails to validate password recovery token expiration in… CWE-613
• CVE-2026-84203 Memos versions 0.26.0 through 0.30.0 fail to revoke refresh tokens when a user changes… CWE-613
• CVE-2026-82909 A vulnerability was determined in QuantumNous new-api up to 1.0.0-rc.15. CWE-613
• CVE-2026-82469 Rodauth before 2.47.0 contains an authentication bypass vulnerability in the jwt_refresh… CWE-613