Red Hat Integration Camel Quarkus 2
8 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Red Hat Integration Camel Quarkus 2, a product in the devtools ci space. Use it to gauge the current risk picture and drill into individual advisories.
Red Hat Integration Camel Quarkus 2 CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 1 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 8 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High4
- Medium4
Latest CVEs
The 8 most recently published vulnerabilities affecting Red Hat Integration Camel Quarkus 2.
- CVE-2024-3884Undertow: outofmemory when parsing form data encoding with application/x-www-form-urlencoded7.5
- CVE-2024-3653Undertow: learningpushhandler can lead to remote memory dos attacks5.3
- CVE-2023-5675Quarkus: authorization flaw in quarkus resteasy reactive and classic when "quarkus.security.jaxrs.deny-unannotated-endpoints" or "quarkus.security.jaxrs.default-roles-allowed" properties are used.6.5
- CVE-2024-2700Quarkus-core: leak of local configuration properties into quarkus applications7.0
- CVE-2024-1300Io.vertx:vertx-core: memory leak when a tcp server is configured with tls and sni support5.4
- CVE-2024-1023Io.vertx/vertx-core: memory leak due to the use of netty fastthreadlocal data structures in vertx6.5
- CVE-2024-1635Undertow: out-of-memory error after several closed connections with wildfly-http-client protocol7.5
- CVE-2023-6267Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.8.6
Product grouping is registry-driven, with AI assist and human review. How it works