Exploited CVEs / CVE-2023-4346

CVE-2023-4346

KNX Association KNX Protocol Connection Authorization Option 1 Overly Restrictive Account Lockout Mechanism Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-07-29; treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

HighCISA KEV

Actively exploited KNX Association KNX Protocol Connection Authorization Option 1 vulnerability, High severity, CVSS 7.5. Added to the CISA KEV catalog 2026-07-15.

Senserva AI read on CVE-2023-4346CISA required actionOfficial fix for CVE-2023-4346Admin questions#104 hottest CVE right now

Risk summary

CVSS base
7.5
EPSS exploit probability
<1%
Severity
High
Added to KEV
2026-07-15
CISA due date
2026-07-29
Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-07-29; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated July 26, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion for CVE-2023-4346

This is a KNX building automation protocol flaw where the Connection Authorization Option 1 account lockout can be abused to purge all devices and set a BCU key that locks them out permanently, effectively bricking KNX installations that lack extra security options. Anyone running KNX for lighting, HVAC, access control, or other building systems on reachable networks is exposed. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-07-15, so attacks are confirmed despite the modest 1 percent EPSS score, and Severity is High at CVSS 7.5.

Do this: Enable KNX Secure or the additional security options on your KNX devices and restrict KNX bus and IP interfaces to trusted networks only.

AI-generated from public data, 2026-07-22. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2023-4346

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for CVE-2023-4346

Published
2026-07-15
Last revised
2026-07-15
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-07-29.

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.

Official fix for CVE-2023-4346

Check the vendor's security advisory channel for the patched KNX Protocol Connection Authorization Option 1 versions and workarounds.

Common questions about CVE-2023-4346

Is CVE-2023-4346 actively exploited?

Yes. CVE-2023-4346 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-07-15, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is <1%.

What is the CISA deadline and required action for CVE-2023-4346?

CISA set the federal (BOD 22-01) remediation due date at 2026-07-29. The verbatim required action: 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.

What fixes CVE-2023-4346?

Check the vendor's security advisory for the patched KNX Protocol Connection Authorization Option 1 versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2023-4346?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2023-4346's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

Three Free Unlimited Audits: all users, all settings, all patches, all tenants. All you do is register.

Three free audits, across every tenant you manage: 1 scan to find, 2 to review your fixes. It finds:

Includes our advanced Claude MCP: everything you need to run full audits.

Lexicon: the terms on this page
CVE
Common Vulnerabilities and Exposures. A unique ID for one publicly known vulnerability, such as CVE-2025-1234.
KB
Microsoft Knowledge Base article. The identifier for a specific Microsoft update.
KEV
CISA Known Exploited Vulnerabilities. CVEs confirmed exploited in the wild. Fix these first.
CVSS
Common Vulnerability Scoring System. A standardized Severity score from 0 to 10.
EPSS
Exploit Prediction Scoring System. The probability a CVE will be exploited in the next 30 days.
MSRC
Microsoft Security Response Center. Microsoft's Patch Tuesday advisories and KB-to-CVE mapping.
NVD
National Vulnerability Database (NIST). Authoritative CVE metadata and CVSS scores.
Ransomware
The vulnerability is linked to known ransomware activity.
Reference: Microsoft CVE and vulnerability management, the full CVE-to-patch lookup ranked by real-world risk, and the Microsoft patching guide, how Intune, Windows Autopatch, Defender, and Azure Update Manager fit together.
Data notice: this page, the feeds, and the API are provided as is, for informational purposes only, without warranty of any kind. Senserva, LLC does not guarantee the accuracy, completeness, or timeliness of third-party data (MSRC, NVD, CISA KEV, EPSS) and accepts no liability for actions taken based on it; verify against the authoritative vendor advisory before acting. Built daily with Senserva Trustworthy AI. All use of this data is subject to the Senserva EULA.