dbcve.org
CWE-367Weakness · CWE-367

CVE-2026-13742

MEDIUM · 5.9 CVSS v4.0 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Zero-click 8 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
Honeywell IQ MultiAccess, all versions prior to and including version 28, contain an improper digital signature verification vulnerability. An attacker could potentially exploit this vulnerability, leading to the replacement of downloaded file with a malicious one. Honeywell also recommends updating to the most recent version of this product, service, or offering [V27 SP1, V28 SP1]

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 Honeywell IQ MultiAccess product contains an improper digital signature verification vulnerability in its file download mechanism. This allows an attacker to potentially replace legitimate downloaded files with malicious ones, exploiting the lack of proper cryptographic validation before file acceptance.

MitigationUpdate Honeywell IQ MultiAccess to version V27 SP1 or V28 SP1 (or later) as recommended by the vendor to remediate this vulnerability.

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
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Honeywell IQ MultiAccess installation
    Check for the product by searching for IQ MultiAccess processes, services, or web application components. Look for installed software listings or running services named 'MultiAccess' or 'IQ MultiAccess' on the system.
    Affected if The product is not found or not installed on the system (not affected)
  2. Identify installed version
    Locate the version information through the application web interface (typically in an About or System Info page), check installed package files, or query the application directly for its version number. Compare this against the fixed versions V27 SP1 and V28 SP1.
    Affected if The installed version is earlier than V27 SP1 or V28 SP1, or the version cannot be determined but is assumed to be older
  3. Verify file download feature is enabled
    Check whether the file download mechanism in the web application is accessible and enabled. Look for download links, file transfer features, or update download functionality within the IQ MultiAccess interface.
    Affected if File download functionality is present and accessible in the application
  4. Check for signature validation configuration
    Examine the application configuration files or settings related to file download and update mechanisms. Look for settings that control digital signature verification or cryptographic validation of downloaded files.
    Affected if Signature verification is disabled, not configured, or absent from the download settings

The environment is affected if Honeywell IQ MultiAccess is installed with a version earlier than V27 SP1 or V28 SP1 and the file download feature is enabled and accessible.

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

Update Honeywell IQ MultiAccess to version V27 SP1 or V28 SP1 (or later) as recommended by the vendor to remediate this vulnerability.

Recommended fix Moderate confidence

V28 SP1 (or V27 SP1 for V27.x line)

  1. 1. Identify the currently installed version of Honeywell IQ MultiAccess
  2. 2. If running a version prior to V27, upgrade directly to V27 SP1 or later
  3. 3. If running V27.x, upgrade to V27 SP1
  4. 4. If running V28.x, upgrade to V28 SP1
  5. 5. After upgrade, verify the digital signature verification functionality is working correctly
  6. 6. Consult Honeywell release notes for any configuration changes required post-upgrade

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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