ABB KNX Update Tool CVE-2026-12705

Q: What is the CVSS score of CVE-2026-12705?

CVE-2026-12705 has a CVSS 4.0 base score of 5.9 (Medium). CVSS vector: CVSS:4.0/AV:A/AC:H/AT:N/PR:L/UI:N/VC:N/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. EPSS exploitation probability: 0.1%.

EUVD-2026-45179 MEDIUM

Missing Support for Integrity Check (CWE-353)

2026-07-17 ABB

GHSA-gvmv-64wv-hj9r

Abb Information Disclosure Knx Update Tool Abb Knx Update Tool Bje

5.9

CVSS 4.0 · Vendor: ABB

Severity by source

Vendor (ABB) PRIMARY

5.9 MEDIUM

CVSS:4.0/AV:A/AC:H/AT:N/PR:L/UI:N/VC:N/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

vuln.today AI

6.4 MEDIUM

Adjacent vector and high complexity reflect MITM-on-local-KNX-segment requirement; PR:L confirms network access needed; no confidentiality impact aligns with update-integrity-only flaw.

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

4.0 AV:A/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ABB).

CVSS VectorVendor: ABB

Attack Vector

Adjacent

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

Jul 17, 2026 - 15:22 NVD

6.4 (MEDIUM) 5.9 (MEDIUM)

Analysis Generated

Jul 17, 2026 - 15:17 vuln.today

DescriptionCVE.org

Missing support for integrity check vulnerability in ABB KNX Update Tool (ABB), ABB KNX Update Tool (BJE).

This issue affects KNX Update Tool (ABB): through 2.0.175; KNX Update Tool (BJE): through 2.0.175.

AnalysisAI

Missing firmware integrity verification in ABB KNX Update Tool versions through 2.0.175 allows an adjacent network attacker with low-privilege access to inject tampered updates onto KNX building automation devices, leading to high integrity and availability impact. The vulnerability (CWE-353) means the tool accepts update packages without cryptographic validation, enabling a man-in-the-middle or rogue-update attack on the KNX bus segment. No public exploit code or CISA KEV listing has been identified at time of analysis, and active exploitation has not been confirmed.

Technical ContextAI

KNX is an open standard building automation protocol widely used in smart buildings for HVAC, lighting, access control, and energy management. ABB KNX Update Tool (CPE: cpe:2.3:a:abb:knx_update_tool_(abb):*:*:*:*:*:*:*:* and cpe:2.3:a:abb:knx_update_tool_(bje):*:*:*:*:*:*:*:*) is used to push firmware or configuration updates to KNX-connected devices on a local installation. CWE-353 (Missing Support for Integrity Check) indicates the update mechanism lacks cryptographic signing or hash verification of update payloads. Without this control, the tool cannot distinguish between legitimate vendor-supplied updates and maliciously crafted or intercepted packages. The BJE variant is the ABB subsidiary Busch-Jaeger Elektro branding of the same tool, both sharing the same affected version range through 2.0.175.

RemediationAI

Consult the ABB security advisory at https://search.abb.com/library/Download.aspx?DocumentID=9AKK108472A9270&LanguageCode=en&DocumentPartId=pdf&Action=Launch for the patched release version; an exact fixed version number is not confirmed in the currently available data beyond the statement that versions through 2.0.175 are affected - upgrade to any version superseding 2.0.175 once ABB releases a corrected build. As a compensating control pending a patch, restrict network-level access to the KNX IP gateway or update tool interface using firewall ACLs or VLAN segmentation so that only authorized technician workstations can reach the KNX update path, reducing the adjacency attack surface. Disable or block unauthenticated KNX IP tunneling sessions where not operationally required. Verify update package checksums manually using out-of-band vendor-provided hashes if available. Note that network segmentation does not eliminate the risk for insider-threat or compromised-workstation scenarios, and a proper code-level integrity check from ABB remains the definitive fix.