CVE-2026-27668
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRUGGEDCOM CROSSBOW SAM-P versions prior to V5.8 contain an improper privilege management vulnerability where User Administrators can administer groups they belong to. This allows an authenticated User Administrator to escalate their own privileges and grant themselves access to any device group at any access level.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed RUGGEDCOM CROSSBOW SAM-P versionAccess the device admin interface or use the system information panel to determine the current SAM-P software version. This is typically found under System > Information or a similar administrative menu.Affected if The installed version is prior to V5.8 (e.g., V5.7, V5.6, V5.5, or earlier)
-
Confirm User Administrator role is activeCheck the user account settings to verify if the logged-in account or accounts under review have the User Administrator role assigned.Affected if User Administrator role is assigned to any account
-
Review group membership configurationExamine the group administration settings to determine whether administrators can modify groups to which they themselves belong.Affected if User Administrators can edit or modify groups they are currently members of
-
Check group access level assignmentsInspect the device group configuration to see what access levels are available and how they are assigned to different user groups.Affected if Any group allows elevated access levels that could be granted through self-modification
You are affected if your RUGGEDCOM CROSSBOW SAM-P version is prior to V5.8 and User Administrator accounts exist that can modify groups they are assigned to.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to RUGGEDCOM CROSSBOW SAM-P V5.8 or later to remediate the improper privilege management vulnerability.
V5.8 or later
- Upgrade RUGGEDCOM CROSSBOW SAM-P to version V5.8 or later
- After upgrading, verify that User Administrators can no longer administer groups they belong to
- Confirm that privilege escalation to device groups is no longer possible for User Administrators
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27668 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data