dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-30495

HIGH · 8.8 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
The Optoma CinemaX P2 projector (firmware TVOS-04.24.010.04.01, Android 8.0.0) exposes Android Debug Bridge (ADB) on TCP port 5555 over the network without requiring authentication. The device is configured with ro.adb.secure=0, which disables RSA key verification. Additionally, a functional su binary exists at /system/xbin/su that grants root privileges without authentication. An attacker on the same network can connect to the device via ADB, obtain a shell, and escalate to root privileges, gaining complete control of the device. This allows extraction of stored WiFi credentials, installation of persistent malware, and access to all device data.

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 · high confidence

The Optoma CinemaX P2 projector runs Android 8.0 with ADB listening on TCP port 5555 without authentication, and has ro.adb.secure=0 which disables RSA key verification. A root-enabled su binary exists at /system/xbin/su, allowing any local or network attacker to gain full root access in two commands.

MitigationIsolate the device on a restricted VLAN or block port 5555 at the network perimeter; contact Optoma for a firmware update that disables ADB or enables authentication.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 checks

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

  1. Identify the device model
    Check if the device is an Optoma CinemaX P2 projector by reviewing device documentation, network scanning results showing the device hostname, or physical inspection of the device
    Affected if The device is an Optoma CinemaX P2 projector
  2. Check the firmware version
    Access the projector settings menu (usually under System > About > Firmware Version) or query the device via ADB if already accessible using 'getprop ro.build.version.incremental' or 'getprop ro.tvos.version'
    Affected if The firmware version is TVOS-04.24.010.04.01
  3. Verify ADB is listening on port 5555
    Run a network port scan against the projector IP address targeting TCP port 5555, or use 'adb connect <projector_ip>:5555' from an ADB client to test connectivity
    Affected if Port 5555 is open and accepting ADB connections without prompting for authentication
  4. Confirm ADB authentication is disabled
    If ADB connect succeeds without any key verification prompt, this indicates ro.adb.secure=0. You can also verify by running 'adb shell' immediately after connecting - it should grant shell access without RSA key verification
    Affected if ADB shell access is granted immediately without any authentication or key verification prompt
  5. Check for root escalation vector
    Once connected via ADB, run 'adb shell su -c id' or check if /system/xbin/su exists using 'adb shell ls -la /system/xbin/su'
    Affected if The su binary exists at /system/xbin/su and executing it grants root privileges without credentials

If you have an Optoma CinemaX P2 projector running firmware TVOS-04.24.010.04.01 with port 5555 open and accessible without ADB authentication, your device is affected by this 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate the device on a restricted VLAN or block port 5555 at the network perimeter; contact Optoma for a firmware update that disables ADB or enables authentication.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30495 — 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-30495 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