dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-8381

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A broken access control vulnerability exists in the TeamViewer DEX Platform (On‑Premises) prior version 9.2. Certain backend API endpoints do not correctly enforce authorization checks, allowing an authenticated user with low privileges to perform actions and access resources intended only for higher‑privileged roles. An attacker with low‑privileged credentials may exploit this to gain unauthorized access to administrative or sensitive functionality.

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 confidence

This is a broken access control vulnerability in TeamViewer DEX Platform (On-Premises) where certain backend API endpoints fail to properly enforce authorization checks. An authenticated user with low privileges can escalate their access to perform administrative actions or view sensitive resources intended only for higher-privileged roles.

MitigationUpgrade TeamViewer DEX Platform to version 9.2 or later, which contains the corrected authorization enforcement for the affected API endpoints.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm TeamViewer DEX Platform deployment
    Identify if your environment runs TeamViewer DEX Platform On-Premises. Check for TeamViewer-related services, installation directories, or consult your IT inventory/documentation for the deployed solution name.
    Affected if The system is not TeamViewer DEX Platform On-Premises
  2. Determine installed version
    Locate the installed TeamViewer DEX Platform version. Check the application documentation for version lookup (typically via administrative UI, configuration files, or system information panel). Compare the version against 9.2.
    Affected if Installed version is 9.1 or earlier (versions prior to 9.2 contain the vulnerability)
  3. Verify API endpoint exposure
    Determine if backend API endpoints are accessible to authenticated users. Check network configuration, firewall rules, and API access controls to confirm endpoints are reachable.
    Affected if API endpoints are exposed and accessible to authenticated users
  4. Confirm user role configuration
    Review the system for presence of role-based access control (RBAC) with multiple privilege levels. Identify if low-privilege (non-administrative) user accounts exist in the system.
    Affected if Multiple user roles exist with low-privilege users present in the system

If running TeamViewer DEX Platform On-Premises version 9.1 or earlier with exposed API endpoints and low-privilege users present, the environment is affected by this authorization bypass vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TeamViewer DEX Platform to version 9.2 or later, which contains the corrected authorization enforcement for the affected API endpoints.

Recommended fix Moderate confidence

TeamViewer DEX Platform version 9.2

  1. 1. Backup all current TeamViewer DEX Platform configuration and data
  2. 2. Verify current installed version by checking the TeamViewer DEX Platform admin interface or system information
  3. 3. Download TeamViewer DEX Platform version 9.2 or later from the official TeamViewer download center or support portal
  4. 4. Review TeamViewer DEX Platform upgrade documentation for specific upgrade procedures
  5. 5. Execute the upgrade following vendor-provided installation instructions
  6. 6. After upgrade, verify that the authorization controls are functioning correctly by testing low-privilege account access to high-privilege endpoints
  7. 7. Confirm the version has been updated to 9.2 or later in the admin interface
Caveat Review TeamViewer release notes for version 9.2 to check for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8381 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8381 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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