# CVE-2026-27668: A vulnerability has been identified in RUGGEDCOM CROSSBOW Secure Access Manager Primary (SAM-P) (All versions < V5.8).


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-r593-vh4q-g7mv

## What is CVE-2026-27668?

CVE-2026-27668 is a high-severity vulnerability in Siemens RUGGEDCOM CROSSBOW Secure Access Manager Primary (SAM-P), published on 14 Apr 2026. 

### Official description

A vulnerability has been identified in RUGGEDCOM CROSSBOW Secure Access Manager Primary (SAM-P) (All versions < V5.8). User Administrators are allowed to administer groups they belong to. This could allow an authenticated User Administrator to escalate their own privileges and grant themselves access to any device group at any access level.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-27668 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27668 is a high-severity vulnerability in Siemens RUGGEDCOM CROSSBOW Secure Access Manager Primary (SAM-P), published on 14 Apr 2026. 
Exploitation: There is no known exploitation of CVE-2026-27668 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM CROSSBOW Secure Access Manager Primary (SAM-P). 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-27668/ (Markdown: https://insights.sbomify.com/CVE-2026-27668/index.md)
```

## Sources

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

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