CVE-2026-114713: Patch Actively Exploited UnrealIRCd

Linked UnrealIRCd servers blocking a malicious labeled-response message

UnrealIRCd administrators should treat CVE-2026-114713 as an incident-response priority, not a routine maintenance item. The UnrealIRCd project disclosed the flaw on November 7, 2026 and reported active exploitation shortly afterward. CISA added it to the Known Exploited Vulnerabilities catalog on November 13, set a November 16 remediation deadline for covered federal systems, and marked forensic triage as required.

The defect affects networks with two or more linked UnrealIRCd servers. A normal connected user can inject server-to-server commands that run with server authority. The vendor says this can enable actions such as KILL and GLINE. This guide explains the exposure, the supported hot patch and upgrade paths, how to verify every node, and how to preserve useful evidence without reproducing the exploit.

What CVE-2026-114713 does

The vulnerability is an improper neutralization of delimiters in the IRCv3 labeled-response module. Red Hat’s technical analysis says the module does not correctly escape the label tag before data crosses a server link. On an IRC network with linked daemons, a remote, unauthenticated network user can manipulate that boundary and inject a server-to-server command.

The injected command is not handled with the attacker’s ordinary user privileges. It is executed with the authority of a trusted server. That trust-boundary failure is why the practical impact is much larger than a malformed client message. An attacker may disrupt users, add network-wide bans, or abuse other commands available on the server link.

UnrealIRCd 6.2.7.1 also fixes eight other security issues, including denial-of-service conditions and cases that could expose a user’s IP address. Even if your topology does not currently include linked servers, the full upgrade remains the safer long-term action.

Who is exposed

  • Highest priority: internet-accessible UnrealIRCd 6.0.0 through 6.2.7 nodes participating in a network of two or more linked servers.
  • Also affected: UnrealIRCd 5. The project says version 5 is similarly affected and has been end of life since July 1, 2023.
  • Uncertain legacy risk: older end-of-life branches were not fully checked. The vendor warns that several fixed bugs may reach back to 3.2.x.
  • Reduced exploitability, not a waiver: a standalone 6.x server does not meet the documented linked-server precondition, but it still lacks the other fixes shipped in 6.2.7.1.

Inventory the entire IRC network, not only the public entry node. A mixed state where one linked server is patched and another is not is not a verified remediation.

Immediate response plan

Preserve evidence before disruptive changes

CISA marks forensic triage as required for this KEV entry. If operationally safe, record each node’s version, module state, process start time, configuration checksum, server-link peers, and relevant log retention before restarting or replacing it. Copy logs to a protected location and record collection times. Exact paths vary by installation, so use the paths defined in your UnrealIRCd configuration rather than assuming a distribution default.

Prioritize review of server-link events, operator actions, unexpected KILL or GLINE activity, new or modified ban lines, account or privilege changes, configuration reloads, and unusual bursts of IRC commands around suspicious sessions. The vendor has not published a universal set of attacker indicators, so an absence of a public IOC list is not evidence of non-exploitation.

For a broader evidence-preservation workflow, see our KEV incident-response guide for edge systems. The products differ, but the order of operations is useful: scope exposure, preserve volatile evidence, remediate, verify, then monitor.

Apply the vendor’s temporary workaround

As an IRC operator, the project recommends adding this network spam filter first:

/SPAMFILTER add -regex T block - Invalid_label ^label=(?![^rn;x20]*z)

This is temporary risk reduction, not the complete fix. According to the vendor, it protects linked servers against the critical issue only when every server is running 6.0.4 or later. It does not address the other eight security problems fixed in the release.

Hot patch every supported 6.x node

On Unix-like systems running UnrealIRCd 6.0.0 through 6.2.7, the vendor provides a no-restart bundle:

./unrealircd hot-patch bundle-20261107

The expected final message is Patch installed and server rehashed correctly. All should be good now! Older supported builds may instead end with Done! All should be good now. Treat any other result as a failure that needs investigation or an upgrade.

Upgrade when hot patching is unavailable

Windows systems cannot use this hot-patch path. For Windows, failed hot patches, and normal maintenance windows, upgrade to UnrealIRCd 6.2.7.1 or a later supported release. On Unix-like systems, the project documents:

./unrealircd upgrade
./unrealircd restart

Follow your normal change-control process, preserve the current configuration and binaries, and confirm the daemon returns with all intended links. Operators on UnrealIRCd 5 or older should migrate to a supported 6.x release rather than treating the legacy module blacklist as a durable fix.

Verify the fix on every linked server

Do not stop at a successful installer message. From the shell on UnrealIRCd 6.0.2 or later, check the loaded module:

./unrealircd module-status | grep labeled-response

Interpret the result exactly:

  • labeled-response 5.0-hot-patch-bundle-20261107 means the vendor hot patch is loaded.
  • labeled-response 6.2.7.1 means the fixed release is running.
  • labeled-response 5.0 without the patch-bundle suffix means the node is not patched.
  • No result requires another verification method. An IRC operator can run MODULE -all, or MODULE -all remote.server.name for a remote linked node.

Capture the output for each server and compare it with the inventory. This is the same fleet discipline used in our Java fleet security-update audit: a deployment is complete only when the intended state is independently observed.

Safe hands-on lab: build a remediation inventory

This lab does not send exploit traffic. It classifies recorded version and module-status data so defenders can find nodes that still need action.

Prerequisites and isolated setup

  • Python 3.8 or later on an administrative workstation.
  • A CSV export created from your asset inventory and authorized verification output.
  • No connection from the script to production IRC servers.

Create inventory.csv:

server,version,linked,module_status,exposure
irc-a,6.2.7,yes,labeled-response 5.0,internet
irc-b,6.2.7,yes,labeled-response 5.0-hot-patch-bundle-20261107,internet
irc-c,6.2.7.1,yes,labeled-response 6.2.7.1,internal
irc-lab,6.2.6,no,labeled-response 5.0,internal
irc-old,5.2.4,yes,labeled-response 5.0,internet

Save the following as unrealircd_inventory.py:

#!/usr/bin/env python3
import csv, sys

FIXED = (6, 2, 7, 1)

def ver(value):
    try:
        return tuple(int(part) for part in value.strip().split("."))
    except ValueError:
        return None

with open(sys.argv[1], newline="", encoding="utf-8") as handle:
    print("server,status,reason")
    for row in csv.DictReader(handle):
        version = ver(row["version"])
        module = row["module_status"]
        linked = row["linked"].lower() == "yes"
        if version is None:
            status, reason = "REVIEW", "Unparseable version"
        elif version >= FIXED:
            status, reason = "FIXED", "Running 6.2.7.1 or later"
        elif "5.0-hot-patch-bundle-20261107" in module:
            status, reason = "HOT_PATCHED", "Vendor hot patch detected"
        elif version[0] <= 5:
            status, reason = "EOL", "Upgrade to a supported release"
        elif (6, 0, 0) <= version <= (6, 2, 7) and linked:
            status, reason = "AFFECTED", "Linked server lacks a verified fix"
        else:
            status, reason = "UPGRADE", "Security update still required"
        print(f'{row["server"]},{status},{reason}')

Run it against the sample data:

python3 unrealircd_inventory.py inventory.csv

Expected output:

server,status,reason
irc-a,AFFECTED,Linked server lacks a verified fix
irc-b,HOT_PATCHED,Vendor hot patch detected
irc-c,FIXED,Running 6.2.7.1 or later
irc-lab,UPGRADE,Exploit precondition reduced, but security update is still required
irc-old,EOL,Upgrade to a supported UnrealIRCd 6 release

Troubleshooting and cleanup

If the script reports an unparseable version, enter only the numeric release such as 6.2.7.1. If a module-status value contains commas, quote that CSV field. A HOT_PATCHED result proves only that the expected module string was recorded; confirm the output directly on the named host and verify all peers.

After review, move the completed inventory into your protected incident record. Remove the lab directory from shared workstations if it contains server names or exposure details:

rm -f inventory.csv unrealircd_inventory.py

Patch or hot patch: the decision

  • Use the hot patch now when the node is supported UnrealIRCd 6 on Unix-like systems and a restart would delay risk reduction.
  • Upgrade to 6.2.7.1 or later on Windows, when hot patching fails, during the next controlled restart, or when you need the simplest long-term state.
  • Retire or migrate EOL releases rather than relying on a partial workaround indefinitely.

In every path, verify the loaded module on each node, confirm all intended links, preserve the evidence needed to investigate prior exploitation, and continue monitoring operator-level actions after remediation.

Conclusion

CVE-2026-114713 crosses the most important boundary in a linked IRC network: it turns ordinary client input into commands trusted as server traffic. The combination of vendor-reported exploitation and CISA KEV inclusion makes fast, measured action necessary. Apply the temporary filter if its version preconditions are met, hot patch or upgrade every server, verify the result independently, and investigate the period before remediation.

Primary references

Similar Posts