It was found that Quarkus 2.10.x does not terminate HTTP requests header context which may lead to unpredictable behavior.
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.
Link | Tags |
---|---|
https://github.com/quarkusio/quarkus/issues/26748 | issue tracking exploit third party advisory |