Quarkus vulnerabilitiesNone on the known-exploited list.
Quarkus has 45 published vulnerabilities across 5 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Quarkus, with 45. If you run Quarkus software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Quarkus products have the most vulnerabilities?
Quarkus leads with 45 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Quarkus vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Quarkus's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Quarkus flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 33%CVE-2022-4116Critical
A vulnerability was found in quarkus. This security flaw happens in Dev UI Config Editor which is vulnerable to drive-by localhost attacks leading to remote code execution.
- 27%CVE-2017-18640High
The Alias feature in SnakeYAML before 1.26 allows entity expansion during a load operation, a related issue to CVE-2003-1564.
- 18%CVE-2020-25649High
A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly.
- 9.0%CVE-2020-13956Medium
Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request...
- 8.7%CVE-2021-26291Critical
Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository...
- 7.5%CVE-2021-2471Medium
Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J).
- 6.7%CVE-2021-37714High
jsoup is a Java library for working with HTML.
- 6.6%CVE-2021-37137High
The Snappy frame decoder function doesn't restrict the chunk length which may lead to excessive memory usage.
- 6.2%CVE-2021-38153Medium
Some components in Apache Kafka use `Arrays.equals` to validate a password or key, which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful.
All Quarkus products we track.
5 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Quarkus? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A vulnerability was found in quarkus. This security flaw happens in Dev UI Config Editor which is vulnerable to drive-by localhost attacks leading to remote code execution.
- Matched to
- Quarkus on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 45 published vulnerabilities across 5 products and 448 versions from Quarkus.
None of Quarkus's vulnerabilities is on the list of flaws known to be exploited today.
Quarkus, with 45 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Quarkus products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.