CVE-2026-94449
Quarkus-smallrye-fault-tolerance: quarkus-smallrye-fault-tolerance: memory leak in @applyguard leads to denial of service
What happened?
A flaw was found in the SmallRye Fault Tolerance library, which is used by Quarkus to provide strategies like retries and circuit breakers for microservices. The issue occurs when using the ApplyGuard or ApplyFaultTolerance annotations, where the library fails to release internal tracking objects after each request. This causes a steady increase in memory usage that eventually leads to the application slowing down and crashing due to lack of memory.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| io.quarkus/quarkus-smallrye-fault-toleranceRed Hat | unaffected: 3.33.4.redhat-00004 to < * | See vendor advisory |
| io.quarkus/quarkus-smallrye-fault-toleranceRed Hat | unaffected: 3.27.6.redhat-00004 to < * | See vendor advisory |
| io.quarkus/quarkus-smallrye-fault-toleranceRed Hat | unaffected: 3.33.4.redhat-00004 to < * | See vendor advisory |
| exploit-intelligence/agent-client-rhel9Red Hat | Default status: unknown | See vendor advisory |
| quarkus-smallrye-fault-toleranceRed Hat | Default status: affected | See vendor advisory |
| quarkus-smallrye-fault-toleranceRed Hat | Default status: affected | See vendor advisory |
| quarkus-smallrye-fault-toleranceRed Hat | Default status: unaffected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.