Called exploited 1051 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing2.9y
- Last sighting23d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 15, 2026
- EUVDENISA, European Unionlisted Jul 15, 2026
- VulnCheck KEVcommercial researchlisted Jul 15, 2026
- CIRCLaggregator, mirrors the abovelisted Jul 15, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationprevidian.com/CVE-2023-4346
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
3 public reports collected from VulnCheck and CIRCL, first on Jul 15, 2026. Each links to its original source. We have not verified them.
Description
KNX Association KNX Protocol Connection Authorization Option 1 contains an overly restrictive account lockout mechanism vulnerability that could allow an attacker to purge all devices without additional security options enabled and set a BCU key to lock the device.
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
