Skip to content
major vulnerability· requires attention

Enables remote code execution in Quarkus' Qute template engine used in many Java microservices; server takeover risk across enterprise apps.

Web

CVE-2026-12894

8.8
High
EPSS 0.37%Patch availableSep 1, 2026

Qute template engine RCE in Quarkus via ReflectionValueResolver bypass.

common questions

Is CVE-2026-12894 being exploited?

Not confirmed. CVE-2026-12894 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-12894?

CVE-2026-12894 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-12894?

Yes. A fix has been recorded for CVE-2026-12894. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-12894 affect?

CVE-2026-12894 affects Quarkus Qute template engine, Applications using Qute templates, Java microservices built on Quarkus. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-12894?

Apply vendor patch immediately; block untrusted templates and restrict access as temporary mitigation.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Quarkus Qute template engineApplications using Qute templatesJava microservices built on Quarkus
impact

Remote code execution and full server takeover by supplying or influencing template text to bypass Java internals protection.

action required

Immediate action required

affected versions
Quarkus quarkus-qute
  • affected>= 3.27.0 and < 3.27.5.SP1
  • affected>= 3.33.0 and < 3.33.3.SP1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free