Skip to main content
VulnerabilityPublished

CVE-2026-1842: SoftIron HyperCloud · Insufficient Session Expiration

Affects SoftIron HyperCloudSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 2.6.9 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.6.9
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade SoftIron HyperCloud to 2.6.9.

Affected software

ProductAffectedFixed in
SoftIronHyperCloudAffected
  • >=2.3.5 <2.6.9
Fixed in
  • 2.6.9

AI-suggested

Organizations should immediately upgrade to a patched version of SoftIron HyperCloud once available that correctly enforces token usage policies and invalidates old access tokens upon refresh. If you cannot patch yet, implement compensating controls such as reducing refresh token lifetimes to the minimum feasible duration, enforcing strict monitoring and alerting on token usage anomalies, and employing network segmentation to limit exposure of authentication endpoints. Additionally, enforce multi-factor authentication (MFA) to reduce the risk of token theft leading to unauthorized access. Regularly audit active sessions and revoke tokens associated with suspicious activity. Employ token binding or additional cryptographic protections if supported by the platform to prevent token replay. Finally, educate administrators and users about secure token handling practices and the risks of token leakage.

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.

References

Community reviews

Loading reviews…