# CVE-2026-19395: An empty <img> attribute value in styled text triggers a parser error that halts the device.

> An attacker can halt an embedded device by providing styled text with an empty image attribute, causing a parser error in Qt for MCUs.

- **Severity:** Medium 6.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-4vr6-gg46-c2vh, RHSA-2026:41387, RHSA-2026:57634

## What is CVE-2026-19395?

CVE-2026-19395 is a medium-severity denial of service vulnerability in Qt for MCUs, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Qt for MCUs, a Text element that displays styled text halts the device if an <img> tag in the text contains an attribute with an empty value. The text parser passes the empty value to an internal check that only accepts non-empty values. The check fails and reports an error, and the default error handler halts the device.

Weakness: CWE-617 (Reachable Assertion), CWE-230 (Improper Handling of Missing Values)

## Which versions are affected by CVE-2026-19395?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qt5` | Red Hat:hummingbird:1 | All versions | 0:5.15.18-3.hum1 |
| `qt5-filesystem` | Red Hat:hummingbird:1 | All versions | 0:5.15.18-3.hum1 |
| `qt5-rpm-macros` | Red Hat:hummingbird:1 | All versions | 0:5.15.18-3.hum1 |
| `qt5-srpm-macros` | Red Hat:hummingbird:1 | All versions | 0:5.15.18-3.hum1 |
| `qt6` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-1.hum1 |
| `qt6-filesystem` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-1.hum1 |
| `qt6-rpm-macros` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-1.hum1 |
| `qt6-srpm-macros` | Red Hat:hummingbird:1 | All versions | 0:6.11.2-1.hum1 |

## How do I fix CVE-2026-19395?

Apply the vendor's patch.

## Is CVE-2026-19395 being exploited?

There is no known exploitation of CVE-2026-19395 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19395 and fix it if it is affected.

What it is: CVE-2026-19395 is a medium-severity denial of service vulnerability in Qt for MCUs, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19395 in the wild and no public exploit code.

Affected product: Qt for MCUs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19395/ (Markdown: https://insights.sbomify.com/CVE-2026-19395/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19395
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19395
- OSV: https://osv.dev/vulnerability/CVE-2026-19395

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19395/
Summaries are generated and may contain mistakes; the official description above is the record.