# CVE-2026-1842: HyperCloud Improper Refresh Token Validation and Access Token Invalidation Allows Long-Term Unauthorized Access

> Attackers with disclosed tokens can maintain long-term unauthorized access to HyperCloud resources due to improper refresh token validation and lack of access token invalidation.

- **Severity:** Medium 6.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2026
- **Updated:** 20 Feb 2026
- **Also known as:** GHSA-2x2g-fcpp-7fr9

## What is CVE-2026-1842?

CVE-2026-1842 is a medium-severity authentication bypass vulnerability in SoftIron HyperCloud, published on 20 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-1842?


## How do I fix CVE-2026-1842?

No fix has been published for CVE-2026-1842 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1842 being exploited?

There is no known exploitation of CVE-2026-1842 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1842 and fix it if it is affected.

What it is: CVE-2026-1842 is a medium-severity authentication bypass vulnerability in SoftIron HyperCloud, published on 20 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1842 in the wild and no public exploit code.

Affected product: SoftIron HyperCloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1842/ (Markdown: https://insights.sbomify.com/CVE-2026-1842/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1842
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1842
- OSV: https://osv.dev/vulnerability/CVE-2026-1842

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1842/
Summaries are generated and may contain mistakes; the official description above is the record.
