Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2023-4346: KNX Connection Authorization Option 1 Device Lockout

Published Aug 29, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS1.4%72nd percentile
CISA KEVYesAdded Jul 15, 2026
In the wildActivePer CISA KEV
Vendor
Knx
IdentifiersCVE-2023-4346CWE-645 · Overly Restrictive Account Lockout…

CVE-2023-4346 is an overly restrictive account lockout mechanism vulnerability in implementations of KNX Connection Authorization that support Option 1. Affected devices use a BCU key to establish a device password, but the key often cannot be reset without knowledge of the current password. An attacker able to access the KNX installation over its connected network, or able to physically access a device, can purge devices that lack additional security options and set a BCU key. This can permanently lock legitimate owners out of affected devices.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes a high-impact availability failure: legitimate operators can lose the ability to access or reset affected KNX devices. This can disrupt KNX building-automation installations and their dependent functions. In many implementations, recovery may not be possible through normal reset procedures and may require hardware replacement.

Mitigation

If you can’t patch tonight, do this now.

Isolate KNX installations from untrusted networks, strictly limit access to networks capable of communicating with KNX devices, and enforce physical security for devices and installation interfaces. Enable additional KNX security options where available, inventory devices using Connection Authorization Option 1, and restrict administrative or commissioning access to authorized personnel.

Remediation

Patch, then assume compromise.

Apply vendor-specific updates, configuration changes, or guidance for affected KNX devices. Where supported, migrate away from Connection Authorization Option 1 and enable stronger or additional security options. Replace devices that cannot be recovered or remediated through supported vendor procedures.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
KnxConnection Authorizationapplication
FAQ

Frequently asked questions

Is CVE-2023-4346 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jul 15, 2026.
Is there a public exploit for CVE-2023-4346?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2023-4346.
Is there a patch for CVE-2023-4346?
Apply vendor-specific updates, configuration changes, or guidance for affected KNX devices. Where supported, migrate away from Connection Authorization Option 1 and enable stronger or additional security options.
What products are affected by CVE-2023-4346?
Knx Connection Authorization.
How severe is CVE-2023-4346?
CVE-2023-4346 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.4% (72nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

29 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity19Community discussion across Reddit, Mastodon, and other social sources.