Skip to main content
CVE-2026-87830VulnerabilityPublished

Wildfly:

Affects wildflySource GCVE Database

0
Compare
Authoritative record:CVE-2026-87830· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade to 39.0.1-r13 as a priority.

Data as of 20 Nov 2026, 03:24 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 39.0.1-r13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade wildfly to 39.0.1-r13.

Affected software

ProductAffectedFixed in
CleanStartwildflypkg:apk/cleanstart/wildfly?arch=aarch64Other threatsAffected
  • <39.0.1-r13
Fixed in
  • 39.0.1-r13
CleanStartwildflypkg:apk/cleanstart/wildfly?arch=x86_64Other threatsAffected
  • <39.0.1-r13
Fixed in
  • 39.0.1-r13

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 patch by upgrading Wildfly to version 39.0.1-r13 or later, where this vulnerability is fixed. No additional mitigation steps are indicated by the vendor.

Description

A critical security vulnerability exists in the Wildfly package's StAX streaming WS-SecurityPolicy validator. Certain relative or unsupported XPath expressions can be transformed into paths that never match the actual XML element path, potentially undermining security policy validation. This flaw affects versions prior to 39.0.1-r13 and has a high impact on confidentiality and integrity. A fix is available in version 39.0.1-r13.

References

Community reviews

Loading reviews…