Medium · CVSS 4.9CVE-2026-24329

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

Answer in brief

CVE-2026-24329 records a Medium severity (CVSS 4.9) vulnerability in Wildfly-core: wildfly core: denial of service via malformed payload injection by an authenticated administrative user.. The current sources do not mark it as known exploited. The current feed maps Red Hat/wildfly-core-security (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 11, 2026Updated Nov 5, 2026Source checked Nov 9, 2026First seen by HOL Aug 11, 2026Material review Nov 5, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 4.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 4.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/wildfly-core-security (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Red Hat/wildfly-core-securitygeneric	*	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Red Hat/wildfly-core-security.
Review the reported fix. Source-reported workaround: 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.

Evidence timeline and material changes

Published upstream
Aug 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 11, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.

Package

Affected range

Fixed version

Red Hat/wildfly-core-securitygeneric

Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Red Hat/wildfly-core-security.

Review the reported fix. Source-reported workaround: 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.

Sources and claim methodology

Upstream source description

Quoted source text, attributed separately from HOL analysis.