Answer in brief
CVE-2023-4346 records a High severity (CVSS 7.5) vulnerability in CVE Program Container. The current sources mark it as known exploited. The current feed maps KNX Association/KNX Protocol Connection Authorization Option 1 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps KNX Association/KNX Protocol Connection Authorization Option 1 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| KNX Association/KNX Protocol Connection Authorization Option 1generic | 0 | Not reported |
Published upstream
Aug 29, 2023
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
Added to CISA KEV
Jul 15, 2026
Evidence: source:kev:kev:kev:recordKNX devices that use KNX Connection Authorization and support Option 1 are, depending on the implementation, vulnerable to being locked and users being unable to reset them to gain access to the device. The BCU key feature on the devices can be used to create a password for the device, but this password can often not be reset without entering the current password. If the device is configured to interface with a network, an attacker with access to that network could interface with the KNX installation, purge all devices without additional security options enabled, and set a BCU key, locking the device. Even if a device is not connected to a network, an attacker with physical access to the device could also exploit this vulnerability in the same way.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-4346 records a High severity (CVSS 7.5) vulnerability in CVE Program Container. The current sources mark it as known exploited. The current feed maps KNX Association/KNX Protocol Connection Authorization Option 1 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps KNX Association/KNX Protocol Connection Authorization Option 1 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| KNX Association/KNX Protocol Connection Authorization Option 1generic | 0 | Not reported |
Published upstream
Aug 29, 2023
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
Added to CISA KEV
Jul 15, 2026
Evidence: source:kev:kev:kev:recordKNX devices that use KNX Connection Authorization and support Option 1 are, depending on the implementation, vulnerable to being locked and users being unable to reset them to gain access to the device. The BCU key feature on the devices can be used to create a password for the device, but this password can often not be reset without entering the current password. If the device is configured to interface with a network, an attacker with access to that network could interface with the KNX installation, purge all devices without additional security options enabled, and set a BCU key, locking the device. Even if a device is not connected to a network, an attacker with physical access to the device could also exploit this vulnerability in the same way.
Quoted source text, attributed separately from HOL analysis.