Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-24329

Wildfly-core: wildfly core: denial of service via malformed payload injection by an authenticated administrative user.

Products / packages Red Hat Fuse 7 · Red Hat JBoss Enterprise Application Platform 7 · Red Hat JBoss Enterprise Application Platform 8 · 3 more

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 15/11/2026, 00:15:33 UTC
redhat · CVSS:3.1 · 4.9
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Severity

medium4.9

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Source guidance available

Review the recorded instructions. Guidance may be a workaround rather than a fixed version.

What this means

A flaw in wildfly-core allows an authenticated administrative user to inject a malformed payload, causing the server to crash. The payload is written into the standalone.xml configuration file, requiring manual intervention to restore server operation. This results in a denial of service.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Red Hat · redhat

Red Hat Fuse 7

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:jboss_fuse:7

Red Hat · redhat

Red Hat JBoss Enterprise Application Platform 7

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:jboss_enterprise_application_platform:7

Red Hat · redhat

Red Hat JBoss Enterprise Application Platform 8

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:jboss_enterprise_application_platform:8

Red Hat · redhat

Red Hat JBoss Enterprise Application Platform Expansion Pack

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:jbosseapxp

Red Hat · redhat

Red Hat Process Automation 7

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:jboss_bpms:7

Red Hat · redhat

Red Hat Single Sign-On 7

0 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:red_hat_single_sign_on:7
Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Restrict network access to the WildFly management interface to trusted hosts only. Configure firewall rules to limit inbound connections to the management port (e.g., 9990) from only authorized IP addresses or subnets. Additionally, ensure that only necessary and trusted administrative users have credentials for the WildFly management console.

Example firewall rule using firewalld on Red Hat Enterprise Linux: firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_IP_ADDRESS>" port port="9990" protocol="tcp" accept' firewall-cmd --reload

This mitigation limits the attack surface by restricting who can access the administrative interface, thereby reducing the risk of an authenticated administrative user exploiting this vulnerability. Note that applying firewall rules may impact legitimate remote management operations if not configured correctly.

redhat guidance ↗

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

A flaw was found in wildfly-core. A remote user authenticated as an administrative user can inject a malformed payload into the Inet Address field through the Management Model. This injection causes the server to crash and become unrecoverable, as the payload is written into the standalone.xml configuration file. Manual intervention is required to restore server operation, leading to a denial of service.

References

2 sources

Inside the record

Evidence available

Package identity · not supplied
Version evidence · not supplied
Remediation guidance
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-24329

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-91 ↗

XML Injection

redhat

Related →
Contributing organizations · 2
redhat

Assigning organization

2026-11-05
CISA-ADP

Additional data publisher

2026-08-12

Timeline

All times UTC
  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.