# CVE-2026-81455: Missing authorization in ThinOS 10

> Unauthenticated remote attackers can bypass authentication to gain unauthorized access to Dell ThinOS 10 systems.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-whqh-fv4r-27g8

## What is CVE-2026-81455?

CVE-2026-81455 is a high-severity missing authorization vulnerability in Dell ThinOS 10, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dell ThinOS 10, versions prior to SecurityAddon_2605.10.2766_T10, contain a Missing Authentication for Critical Function vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Unauthorized access.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-81455 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81455 is a high-severity missing authorization vulnerability in Dell ThinOS 10, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81455 in the wild and no public exploit code.

Affected product: Dell ThinOS 10. 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-81455/ (Markdown: https://insights.sbomify.com/CVE-2026-81455/index.md)
```

## Sources

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

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