Is there a public exploit for CVE-2026-93432?

No public exploit for CVE-2026-93432 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-93432?

CVE-2026-93432 scores CVSS 6.1 (v3.1), rated medium. EPSS puts the chance of exploitation in the next 30 days at 0.54%.

What does CVE-2026-93432 affect?

CVE-2026-93432 affects Red Hat Red Hat build of Quarkus 3.33.4.redhat, Red Hat build of Quarkus 3.27.6.redhat, Red Hat Build of Apache Camel 3.33.4.redhat.

6.1 Medium

A flaw was found in the Quarkus Qute template engine.

CVE-2026-93432

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.

Assessment

CVSS: 6.1 (v3.1)
Severity: Medium
EPSS: 0.54% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 18 September 2026
Last updated: 6 November 2026
Affected: Red Hat · Red Hat Build of Apache Camel 3.33.4.redhat · Red Hat build of Quarkus 3.27.6.redhat · Red Hat build of Quarkus 3.33.4.redhat
Assigner: redhat

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 5 + 3? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-93432