CVE Intelligence
Medium Cross-site scripting

CVE-2026-93432 — Io.quarkus.qute:quarkus-core: cross-site scripting (xss) and json injection via qute {#eval} section in quarkus

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.

Published Sep 18, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.42%
ahead of 35% of scored CVEs · Oct 15, 2026
Affects
Red Hat
Build Of Keycloak and 6 more
CVSS base
6.1
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Red Hat Build Of Keycloak, Red Hat Build Of Quarkus, Red Hat Exploit Intelligence…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Red Hat Build Of Keycloak versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Build Of Quarkus versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Exploit Intelligence versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat build of Apache Camel 4 for Quarkus 3 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat build of Apicurio Registry 3 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat build of Quarkus 3.27.6.redhat versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Fuse 7 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.1 CVSS 3.1 Medium 2.8 2.7 secalert@redhat.com via NIST National Vulnerability Database
6.1 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
6.1 CVSS 3.1 Medium — — redhat via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N (score shown at the top: secalert@redhat.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-79 · Cross-site Scripting (XSS)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor CSP violation reports and script payloads in reflected parameters.
web/proxy/WAF logsnetwork IDS/IPSapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · red hat/red hat build of quarkus 3.27.6.redhat, red hat/exploit intelligence, red hat/red hat build of apache camel 4 fo
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 6.1
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • CVE published
    Sep 18, 2026 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

5 on the record

Elsewhere on this site

Red Hat
every CVE for this vendor
Cross-site scripting
same class
CWE-79
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-85634 Wildfly-core: wildfly-core: deployer rbac role privilege escalation via path traversal in deployment name 4h
  • CVE-2026-87744 Io.quarkus:quarkus-hibernate-orm-rest-data-panache: missing authorization in quarkus rest data panache via dropped security annotations 3d
  • CVE-2026-94451 Quarkus-hibernate-orm-rest-data-panache: quarkus-hibernate-orm-rest-data-panache: information disclosure and dos via unvalidated sort parameter in rest data panache 3d
  • CVE-2026-109082 Keycloak-services: keycloak-services: ciba confidential-only contract not enforced for public clients 3d
  • CVE-2026-107889 Keycloak-services: keycloak-services: stored xss on login page via kcsanitize bypass 6d
  • CVE-2026-107623 Keycloak-services: keycloak-services: oidc dcr read-modify-write silently disables offline token revocation 7d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-93432 is "Io.quarkus.qute:quarkus-core: cross-site scripting (xss) and json injection via qute {#eval} section in quarkus", rated Medium. It affects Build Of Keycloak (Red Hat); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.1 describes technical severity. EPSS 0.42% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.