CVE-2026-1842
Received Received - Intake
Token Misuse in HyperCloud Enables Prolonged Unauthorized Access

Publication date: 2026-02-20

Last updated on: 2026-02-20

Assigner: SoftIron

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-20
Last Modified
2026-02-20
Generated
2026-05-07
AI Q&A
2026-02-20
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
softiron hypercloud From 2.3.5 (inc) to 2.6.8 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-613 According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability affects HyperCloud versions 2.3.5 through 2.6.8, where refresh tokens were improperly allowed to be used directly for resource access.

Additionally, the system failed to invalidate previously issued access tokens when a refresh token was used.

Since refresh tokens have a much longer lifetime (default one year), an authenticated client could use a refresh token instead of an access token to maintain long-term access without the usual token rotation.

Moreover, old access tokens remained valid even after refresh, allowing concurrent or extended use beyond the intended session boundaries.

This means that if a token is disclosed, it could allow prolonged unauthorized access.


How can this vulnerability impact me? :

The vulnerability can lead to prolonged unauthorized access to resources because refresh tokens can be used directly for resource access without proper invalidation of old access tokens.

An attacker or unauthorized user who obtains a refresh token could maintain access for up to a year without needing to re-authenticate or rotate tokens.

This extended access increases the risk of data exposure, unauthorized actions, and potential compromise of sensitive systems.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart