CVE-2026-93432
Io.quarkus.qute:quarkus-core: cross-site scripting (xss) and json injection via qute {#eval} section in quarkus
What happened?
A flaw was found in the Quarkus Qute template engine. When the {#eval} section helper processes a sub-template, it fails to pass the parent template's content type information. This bypasses standard escaping mechanisms, allowing untrusted data to be output as raw, unescaped text. This vulnerability can lead to Cross-Site Scripting (XSS) and JSON Injection, potentially allowing a remote attacker to execute arbitrary code in a user's browser or manipulate data.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| io.quarkus.qute/qute-coreRed Hat | unaffected: 3.33.4.redhat-00004 to < * | See vendor advisory |
| io.quarkus.qute/qute-coreRed Hat | unaffected: 3.27.6.redhat-00004 to < * | See vendor advisory |
| io.quarkus.qute/qute-coreRed Hat | unaffected: 3.33.4.redhat-00004 to < * | See vendor advisory |
| exploit-intelligence/agent-client-rhel9Red Hat | Default status: affected | See vendor advisory |
| qute-coreRed Hat | Default status: affected | See vendor advisory |
| qute-generatorRed Hat | Default status: affected | See vendor advisory |
| qute-coreRed Hat | Default status: affected | See vendor advisory |
| qute-coreRed Hat | Default status: affected | See vendor advisory |
| rhbk/keycloak-rhel9-operatorRed Hat | Default status: affected | See vendor advisory |
| qute-generatorRed Hat | Default status: affected | See vendor advisory |
| qute-coreRed Hat | Default status: affected | See vendor advisory |
| qute-generatorRed Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.