Repository navigation
Quarkus’s plan to address the critical vulnerability CVE-2026-111497? #57862
Replies: 2 comments
|
The fix is already on Maven Central even though Quarkus has not bumped it yet: Brotli4j 1.24.0 (24 Oct) bundles Brotli 1.2.1, and its advisory GHSA-x524-jrqf-vwq6 marks One trap if you override it yourself: the vulnerable decoder is C code that ships in the platform artifacts ( <dependencyManagement>
<dependencies>
<dependency>
<groupId>com.aayushatharva.brotli4j</groupId>
<artifactId>brotli4j-bom</artifactId>
<version>1.24.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<!-- then the Quarkus BOM import as before -->
</dependencies>
</dependencyManagement>Order matters, because Maven uses the first imported BOM that manages an artifact. Afterwards On exposure: the CVE is in the decoder, while Quarkus uses Brotli to compress responses, and only when |
|
Looks like there is a merged PR with the upgrade to Will we be getting a hotfix release soon? |
Uh oh!
There was an error while loading. Please reload this page.
Hello!
CVE-2026-111497, reported October 22, affects Brotli 1.0.3–1.2.0. A crafted stream may cause memory disclosure, denial of service, or code execution. Brotli4j 1.23.0, which vendors Brotli 1.2.0, in the affected range.
https://nvd.nist.gov/vuln/detail/cve-2026-111497
Looking at this repository, I haven't found an issue ticket addressing this concern and the latest pom(
https://github.com/quarkusio/quarkus/blob/main/bom/application/pom.xml) shows
<brotli4j.version>1.23.0</brotli4j.version>
Could you please share the plan?
All reactions