# CVE-2026-81473: Missing authorization in Rugged Control Center (RCC)

> A local low-privileged attacker can exploit improper authorization in Dell Rugged Control Center to elevate privileges.

- **Severity:** High 8.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-rpjr-64ph-wqh3

## What is CVE-2026-81473?

CVE-2026-81473 is a high-severity missing authorization vulnerability in Dell Rugged Control Center (RCC), published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Dell Rugged Control Center (RCC), versions prior to 5.2.206, contain an Improper Authorization vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of Privileges.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-81473 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81473 is a high-severity missing authorization vulnerability in Dell Rugged Control Center (RCC), published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-81473 in the wild and no public exploit code.

Affected product: Dell Rugged Control Center (RCC). 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-81473/ (Markdown: https://insights.sbomify.com/CVE-2026-81473/index.md)
```

## Sources

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

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