Quarkus vulnerabilities
We track 12 vulnerabilities in Quarkus products across 2 products. 12 are rated high or critical, and none are known to be exploited. The most recent was published on August 31, 2026.
Latest Quarkus vulnerabilities
- 8.8 High severity
quarkus-qute: Improper Neutralization of Special Elements Used in a Template Engine
A flaw was found in the Qute template engine, which is used by Quarkus to generate dynamic content like HTML pages or emails. The issue exists in the component responsible for looking up data values (ReflectionValueResolver), which fails to properly block acce
- 9.1 Critical severity
Red Hat build of Quarkus: Authentication Bypass Using an Alternate Path or Channel
A vulnerability was found in Quarkus in the quarkus-security-webauthn module. The Quarkus WebAuthn module publishes default REST endpoints for registering and logging users in while allowing developers to provide custom REST endpoints. When developers provide
- 9.8 Critical severity
Red Hat build of Quarkus 2.13.9.Final: Improper Handling of Exceptional Conditions
A flaw was found in the json payload. If annotation based security is used to secure a REST resource, the JSON body that the resource may consume is being processed (deserialized) prior to the security constraints being evaluated and applied. This does not hap
- 9.1 Critical severity
Red Hat build of Quarkus 2.13.9: Missing Authorization
A flaw was found in Quarkus. This issue occurs when receiving a request over websocket with no role-based permission specified on the GraphQL operation, Quarkus processes the request without authentication despite the endpoint being secured. This can allow an
- 7.5 High severity
gradle-plugin: Cleartext Storage of Sensitive Information in an Environment Variable
A flaw was found in Quarkus, where it does not properly sanitize artifacts created using the Gradle plugin, allowing certain build system information to remain. This flaw allows an attacker to access potentially sensitive information from the build system with
- 7.5 High severity
Red Hat build of Quarkus 2.13.8.Final: Exposure of Sensitive Information to an Unauthorized Actor
A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used, which can allow attackers to access sensitive user data directly from the ID token or by using the access token
- 8.1 High severity
Openshift Serverless 1 on RHEL 8: Incorrect Authorization
A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy alt
- 7.5 High severity
Quarkus CORS filter allows simple GET and POST requests with invalid Origin to proceed.
Quarkus CORS filter allows simple GET and POST requests with invalid Origin to proceed. Simple GET or POST requests made with XMLHttpRequest are the ones which have no event listeners registered on the object returned by the XMLHttpRequest upload property and
- 7.5 High severity
Jackson-databind: Deserialization of Untrusted Data
In FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. An application is vulnerable only with certain customized choices for dese
- 7.5 High severity
Jackson-databind: Deserialization of Untrusted Data
In FasterXML jackson-databind before versions 2.13.4.1 and 2.12.17.1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled.
- 8.8 High severity
quarkus: Incorrect Authorization
A flaw was found in Quarkus. The state and potentially associated permissions can leak from one web request to another in RestEasy Reactive. This flaw allows a low-privileged user to perform operations on the database with a different set of privileges than in
- 9.8 Critical severity
Postgresql Jdbc Driver: Improper Initialization
pgjdbc is the offical PostgreSQL JDBC Driver. A security hole was found in the jdbc driver for postgresql database while doing security research. The system using the postgresql library will be attacked when attacker control the jdbc url or properties. pgjdbc