Build of Apache Camel for Spring Boot vulnerabilitiesRanked by how likely they are to be used.
Build of Apache Camel for Spring Boot is made by Red Hat. We track 4 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Build of Apache Camel for Spring Boot, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Build of Apache Camel for Spring Boot vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Build of Apache Camel for Spring Boot's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Build of Apache Camel for Spring Boot 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.
- 2.6%CVE-2024-7885High
A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests.
- 2.3%CVE-2025-9784High
A flaw was found in Undertow where malformed client requests can trigger server-side stream resets without triggering abuse counters.
- 0.9%CVE-2026-28368High
A flaw was found in Undertow. This vulnerability allows a remote attacker to construct specially crafted requests where header names are parsed differently by Undertow compared to upstream proxies.
- 0.9%CVE-2026-28369High
A flaw was found in Undertow. When Undertow receives an HTTP request where the first header line starts with one or more spaces, it incorrectly processes the request by stripping these leading spaces.
Running Build of Apache Camel for Spring Boot? 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 Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This issue occurs when the parseProxyProtocolV1 method processes multiple requests on the same HTTP connection. As a result, different requests may share the same StringBuilder instance, potentially leading to information leakage between requests or responses. In some cases, a value from a previous request or response may be erroneously reused, which could lead to unintended data exposure. This issue primarily results in errors and connection termination but creates a risk of data leakage in multi-request environments.
- Matched to
- Build of Apache Camel for Spring Boot 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.
We track 4 published vulnerabilities listed under the name Build of Apache Camel for Spring Boot, across 1 version.
None of Build of Apache Camel for Spring Boot's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Build of Apache Camel for Spring Boot. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.