● Low · CVSS 2.9

How to Fix CVE-2026-0992: Critical Vulnerability in Red Hat Hardened Images

Q: Is CVE-2026-0992 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-0992?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Red Hat Hardened Images run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-22366: Improper control of filename for include/require statement in php program ('php. — Improper control of filename for include/require statement in php program ('php.
How to Fix CVE-2026-44671: Critical Vulnerability in zitadel — Critical Vulnerability in zitadel
How to Fix CVE-2026-32249: NFA regex engine NULL pointer dereference affects Vim < 9.2.0137 in vim , NFA regex engine NULL pointer dereference affects Vim < 9.2.0137 in vim
How to Fix CVE-2026-33323: Critical Vulnerability in parse-server , Critical Vulnerability in parse-server
How to Fix CVE-2026-20753: Critical Vulnerability in Slim Bootloader may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable local code execution. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (high) impacts. , Critical Vulnerability in Slim Bootloader may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable local code execution. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (high) impacts.

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 2.9 - Low
Actively exploited?	Not currently listed in CISA KEV
Affected	Red Hat Hardened Images - see advisory for affected version ranges
Fixed in	2.15.2-0.3.hum1
Type (CWE)	CWE-400: Uncontrolled Resource Consumption

What is CVE-2026-0992?

CVE-2026-0992 is a security flaw in Red Hat Hardened Images. A flaw was found in the libxml2 library. This uncontrolled resource consumption vulnerability occurs when processing XML catalogs that contain repeated <nextCatalog> elements pointing to the same downstream catalog.

Why this CVE matters

Unpatched network-facing software is the leading initial-access vector in public breach reporting. Treat any CVSS-9 class flaw on an internet-reachable system as urgent, regardless of whether public exploit code has been observed yet.

For deployments of Red Hat Hardened Images that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

Check your installed Red Hat Hardened Images version against the affected ranges in the vendor advisory linked below. If you cannot determine the version, treat the system as potentially affected and apply the patched build.

Open Red Hat Hardened Images's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-0992

The fix is to upgrade Red Hat Hardened Images to version * or later.

Affected versions confirmed in the CVE record:

Red Hat Hardened Images < *

Patch via the OS package manager (Linux)


<!-- enrich_agent_2:v1 -->
# 1. Update the package metadata.
sudo apt update                                  # Debian / Ubuntu
sudo dnf check-update                            # RHEL / Rocky / AlmaLinux / Fedora
sudo zypper refresh                              # openSUSE

# 2. Pull the patched version `*` of Red Hat Hardened Images from Red Hat.
sudo apt install --only-upgrade red-hat-hardened-images
sudo dnf upgrade red-hat-hardened-images
sudo zypper update red-hat-hardened-images

# 3. Restart the affected service so the patched binary is the running binary.
sudo systemctl restart red-hat-hardened-images || true

# 4. Verify the running version.
red-hat-hardened-images --version

Verify the fix worked


<!-- enrich_agent_2:v1 -->
# 1. Confirm the running version matches the fixed-in version from the advisory.
#    Cross-check against the vendor advisory: https://access.redhat.com/errata/RHSA-2026:7519

# 2. Re-scan with your vulnerability scanner. The scanner should no longer flag
#    this CVE on the patched host.
# Example with Nmap NSE:
nmap -sV --script vuln <target-host>

# 3. Inspect the service / kernel logs for crash-loops or rollback events in
#    the first hour after the upgrade.
journalctl -u <service-name> --since "1 hour ago"
dmesg --since "1 hour ago"

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-0992.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-0992 being exploited in the wild?