How severe is CVE-2026-44091?

CVE-2026-44091 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability high.

Is CVE-2026-44091 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-44091?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-44091 published?

CVE-2026-44091 was published on 2026-07-30 and last updated on 2026-07-31.

CVE-2026-44091

CVE-2026-44091 is a critical-severity vulnerability with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-501.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
CVSS v4: 8.8
EPSS exploit prediction: 0% (26th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-501
Published: 2026-07-30
Last modified: 2026-07-31

Description

An unauthenticated remote attacker can post a malicious ID to the MQTT Broker results in the creation of a new configuration entry in the system configuration. This may lead to integrity and availability loss.

Frequently asked questions

What is CVE-2026-44091?: An unauthenticated remote attacker can post a malicious ID to the MQTT Broker results in the creation of a new configuration entry in the system configuration. This may lead to integrity and availability loss.
How severe is CVE-2026-44091?: CVE-2026-44091 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability high.
Is CVE-2026-44091 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-44091?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-44091 published?: CVE-2026-44091 was published on 2026-07-30 and last updated on 2026-07-31.

References

https://www.certvde.com/en/advisories/VDE-2026-008/

Other CWE-501 vulnerabilities

CVE-2026-25725 — Critical (CVSS 10.0): Claude Code is an agentic coding tool. Prior to version 2.1.2, Claude Code's bubblewrap sandboxing mechanism failed to…
CVE-2025-48938 — Critical (CVSS 9.8): go-gh is a collection of Go modules to make authoring GitHub CLI extensions easier. A security vulnerability has been…
CVE-2024-49050 — High (CVSS 8.8): Visual Studio Code Python Extension Remote Code Execution Vulnerability
CVE-2023-28597 — High (CVSS 8.3): Zoom clients prior to 5.13.5 contain an improper trust boundary implementation vulnerability. If a victim saves a local…
CVE-2024-23682 — High (CVSS 8.2): Artemis Java Test Sandbox versions before 1.8.0 are vulnerable to a sandbox escape when an attacker includes class…
CVE-2026-33828 — High (CVSS 7.8): Trust boundary violation in Windows Attestation allows an authorized attacker to elevate privileges locally.

Browse all CWE-501 vulnerabilities →