Wildfly: unauthenticated remote attacker can create arbitrary durable queues via the CORE protocol, leading to
Affects wildflySource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 42.0.0-r1 soon.
Data as of 21 Nov 2026, 02:01 UTC
- Patch
- Available – fixed in 42.0.0-r1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
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 20 Nov 2026.
What to do
Upgrade wildfly to 42.0.0-r1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CleanStartwildflypkg:apk/cleanstart/wildfly?arch=aarch64Other threats | Affected
| Fixed in
|
CleanStartwildflypkg:apk/cleanstart/wildfly?arch=x86_64Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official fix by upgrading Wildfly to version 42.0.0-r1 or later. Since a patch is available, updating to the fixed version fully mitigates the vulnerability.
Description
A security vulnerability in Wildfly allows an unauthenticated remote attacker to create arbitrary durable queues via the CORE protocol. This can lead to unauthorized manipulation of the broker state and potential denial of service conditions. The issue affects Wildfly versions prior to 42.0.0-r1. A fix is available in version 42.0.0-r1.