CVE-2025-58056VulnerabilityPublished 15 Oct 2025Updated 3 Nov 2026

Red Hat Security Advisory: Red Hat Build of Apache Camel 4.10 for Quarkus 3.20 update is now available (RHBQ 3.20.3.GA)

Affects Red HatSource GCVE Database

Compare

Not known to be exploited.

Data as of 3 Nov 2026, 17:46 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Red Hat has released an official update (RHBQ 3.20.3.GA) that addresses this vulnerability. Users should apply this update after backing up their existing installations. Additionally, to mitigate the issue, enforce strict RFC compliance on all front-end proxies and load balancers to reject or normalize lone LF characters in chunk extensions before forwarding requests. Input validation at the application or proxy layer should also be configured to block malformed chunked requests, ensuring consistent parsing across all components in the request path.

Description

A moderate severity vulnerability (CVE-2025-58056) affects the Netty HTTP/1.1 chunked encoding parser used in Red Hat Build of Apache Camel 4.10 for Quarkus 3.20. The flaw allows newline (LF) characters in chunk extensions to be misinterpreted, potentially enabling HTTP request smuggling attacks in very specific deployment scenarios involving reverse proxies that mishandle such characters. The vulnerability requires a niche configuration to be exploitable and does not pose a universal risk to Netty-based servers. Red Hat has released an update (RHBQ 3.20.3.GA) addressing this issue.

Impact

The vulnerability can enable HTTP request smuggling attacks under very specific conditions where a reverse proxy mishandles lone LF characters in chunk extensions and forwards them unmodified to Netty. Successful exploitation could allow attackers to bypass access controls or corrupt HTTP responses. However, the risk is limited because most real-world reverse proxies normalize or reject malformed chunked requests, and Netty itself does not introduce risk without such proxies. Therefore, the impact is moderate and not widespread.

Summary

CVE-2025-58056 is a vulnerability in Netty's HTTP/1.1 chunked encoding parser where lone LF characters in chunk extensions are incorrectly treated as the end of the chunk-size line instead of requiring a proper CRLF sequence. This parsing discrepancy can be exploited in rare cases where a reverse proxy interprets the same input differently, potentially enabling HTTP request smuggling attacks such as bypassing access controls or corrupting responses. The vulnerability affects Red Hat Build of Apache Camel 4.10 for Quarkus 3.20 and has been rated moderate severity by Red Hat due to its limited exploitability, which depends on specific proxy configurations. Red Hat has issued an update (RHBQ 3.20.3.GA) to address this issue and recommends enforcing strict RFC compliance on front-end proxies and load balancers to reject or normalize lone LF characters in chunk extensions.

CWE-444Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling) (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
Implementation
Use a web server that employs a strict HTTP parsing procedure, such as Apache.
Implementation
Use only SSL communication.
Implementation
Terminate the client session after each request.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.5 (opens in a new tab)
Attack patterns
HTTP Response Smuggling (opens in a new tab)
HTTP Request Smuggling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2026, 17:46 UTC

WeaknessesCWE-444

Technical details

References

Community reviews

Related threats