dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-4272

HIGH · 8.1 CVSS v3.1 Published 2026-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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
Missing Authentication for Critical Function vulnerability in Honeywell Handheld Scanners allows Authentication Abuse.This issue affects Handheld Scanners: from C1 Base(Ingenic x1000) before GK000432BAA, from D1 Base(Ingenic x1600) before HE000085BAA, from A1/B1 Base(IMX25) before BK000763BAA_BK000765BAA_CU000101BAA. This vulnerability could allow a remote attacker within Bluetooth range of the scanner's base station has the capability to remotely execute system commands on the host connected to the base station without authentication. This issue has been assigned  CVE-2026-4272 https://nvd.nist.gov/vuln/detail/CVE-2026-4272 and rated with a severity of High. Honeywell strongly recommends that users upgrade to the latest version identified to resolve the vulnerability.

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

Missing authentication in Honeywell handheld scanner base stations (C1, D1, A1/B1 models) allows remote attackers within Bluetooth range to execute system commands on connected hosts without any credentials. The vulnerability affects the Bluetooth communication interface between the scanner base and host system.

MitigationUpgrade scanner firmware to the latest versions (GK000432BAA for C1, HE000085BAA for D1, BK000763BAA/BK000765BAA/CU000101BAA for A1/B1) as specified by Honeywell.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Identify Honeywell base station model
    Locate the model number label on the bottom or back of the Honeywell scanner base station. Look for model identifiers C1, D1, A1, or B1 in the product name or model number.
    Affected if The base station model is one of: C1 Base, D1 Base, A1 Base, or B1 Base.
  2. Check installed firmware version
    Access the base station configuration interface or check the firmware version through the Honeywell management software or scanner display menu. Compare the firmware version against the fixed versions: GK000432BAA (C1), HE000085BAA (D1), BK000763BAA/BK000765BAA/CU000101BAA (A1/B1).
    Affected if The installed firmware version is older than the fixed versions listed, or the firmware version cannot be verified.
  3. Verify Bluetooth status on base station
    Check the base station configuration settings or LED indicators to determine if Bluetooth connectivity is currently enabled.
    Affected if Bluetooth is enabled on the base station and the device is in an area where unauthorized Bluetooth attackers could be within range.
  4. Check for connected host systems
    Identify any host systems (computers, terminals, point-of-sale devices) that are connected to or communicate through the base station.
    Affected if The base station is actively connected to host systems and Bluetooth is enabled, allowing potential command injection to reach those hosts.

A user is affected if they own a C1, D1, A1, or B1 base station with Bluetooth enabled and firmware versions older than GK000432BAA, HE000085BAA, or BK000763BAA/BK000765BAA/CU000101BAA respectively.

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 scanner firmware to the latest versions (GK000432BAA for C1, HE000085BAA for D1, BK000763BAA/BK000765BAA/CU000101BAA for A1/B1) as specified by Honeywell.

Recommended fix High confidence

C1 Base: GK000432BAA or later; D1 Base: HE000085BAA or later; A1/B1 Base: BK000763BAA_BK000765BAA_CU000101BAA or later

  1. Identify your Honeywell Handheld Scanner base model (C1 Base with Ingenic x1000, D1 Base with Ingenic x1600, or A1/B1 Base with IMX25)
  2. Determine the current firmware version of your scanner base station
  3. Download the latest firmware version from Honeywell's official support website for your specific model
  4. Follow Honeywell's official firmware update instructions to apply the upgrade to your scanner base station
  5. Verify the firmware has been successfully updated to the fixed version

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
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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