dbcve.org
CWE-1313Weakness · CWE-1313

CVE-2026-36027

MEDIUM · 6.8 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click 7 weeks old

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
An issue in Code27 Companion Hub SQ3A.220705.003.A1 allows a physically proximate attacker to execute arbitrary code via the USB debugging (ADB) and Android Debug Bridge components

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

The Code27 Companion Hub device (firmware SQ3A.220705.003.A1) contains a vulnerability where the USB debugging (ADB) interface is accessible to physically proximate attackers, allowing them to execute arbitrary code on the device. This requires physical USB access to the device.

MitigationDisable USB debugging (ADB) in production builds or restrict physical access to the device; if ADB is required for development, ensure it is only enabled in controlled environments with limited physical access.

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

CVSS:3.1/AV:P/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. Confirm device model
    Identify if the device is a Code27 Companion Hub. This may be visible on the device label, in system information, or via `getprop ro.product.name` or `getprop ro.product.device` if ADB is accessible.
    Affected if Device model is Code27 Companion Hub
  2. Check firmware version
    Retrieve the installed firmware version. On Android-based devices, run `getprop ro.build.version.incremental` or `getprop ro.build.fingerprint` via ADB or check in Settings > About Phone.
    Affected if Firmware version matches or is within the range of SQ3A.220705.003.A1
  3. Verify ADB interface status
    Check if USB debugging (ADB) is enabled on the device. On Android devices, go to Settings > Developer Options > USB Debugging, or run `getprop persist.sys.usb.config` to see if 'adb' is present in the USB configuration.
    Affected if USB debugging (ADB) is enabled and accessible via USB connection
  4. Test ADB access
    Connect the device via USB to a computer and attempt to run `adb devices` to see if the device is listed and accessible for ADB commands.
    Affected if Device responds to ADB commands, indicating the interface is reachable

The environment is affected if the device is a Code27 Companion Hub running firmware SQ3A.220705.003.A1 (or compatible version) AND USB debugging (ADB) is enabled and accessible via USB connection.

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

Disable USB debugging (ADB) in production builds or restrict physical access to the device; if ADB is required for development, ensure it is only enabled in controlled environments with limited physical access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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