How to Hot-Patch UnrealIRCd and Verify the Fix
Security Intermediate 5 min read

How to Hot-Patch UnrealIRCd and Verify the Fix

How to hot-patch UnrealIRCd for CVE-2026-114713 without a restart: apply the workaround, run the bundle, verify each server and handle version 5.

Published: November 15, 2026 • Updated: November 15, 2026
unrealircdhot-patchpatch managementirc

To hot-patch UnrealIRCd for CVE-2026-114713, apply the network-wide SPAMFILTER workaround, run ./unrealircd hot-patch bundle-20261107 on every server from 6.0.0 to 6.2.7, then confirm each one with module-status. The hot-patch fixes the flaw without a restart, so users stay connected. Servers that cannot take the hot-patch upgrade to 6.2.7.1, and UnrealIRCd 5 servers blacklist the labeled-response module and restart.

What is an UnrealIRCd hot-patch?

An UnrealIRCd hot-patch is a bundle of fixed modules that the server builds and loads while it is running, then activates with a rehash. It changes the code of the affected modules without disconnecting users, which a full upgrade and restart would do.

The project published bundle-20261107 on November 7, 2026, alongside UnrealIRCd 6.2.7.1. It covers all nine security issues fixed in that release, including CVE-2026-114713, which CISA added to its exploited list on November 13. The commands below come from the maintainer's oss-security advisory.

Before you start

  • List every server. The flaw abuses links between servers, so a single unpatched leaf leaves the network exposed. Include hubs, leaves and any services or test servers that link in.
  • Record versions. Note which servers run 6.0.0 to 6.2.7, which run 5.x and which run older releases. The hot-patch covers only 6.0.0 to 6.2.7.
  • Check how each server was installed. The commands below run from the UnrealIRCd directory of a source install. Distribution packages, such as unrealircd-6.1.10-1.el9 in EPEL 9, follow the package manager's update path instead. As of November 9, Red Hat's tracking bugs for the package fix were still open.
  • Have IRC operator access. You need it for the workaround and for checking remote servers.

Step 1: apply the SPAMFILTER workaround

The advisory gives a one-line SPAMFILTER command, run once as an IRC operator, that blocks label tags containing invalid characters. The advisory presents it as a network-wide workaround, which covers linked servers while you patch them one at a time. Copy the command exactly from the advisory: it contains a regular expression, and a single changed character breaks it.

The advisory notes one limit: the workaround protects the network only when all linked servers run 6.0.4 or newer. If any server is older, move it up the list for patching or upgrading.

Step 2: hot-patch UnrealIRCd on each server

From the UnrealIRCd directory on each 6.x server, run:

./unrealircd hot-patch bundle-20261107

On success the last line reads "Patch installed and server rehashed correctly. All should be good now!" Older 6.x versions print "Done! All should be good now" instead. Either message means the patched module is loaded.

If the build fails, check the UnrealIRCd FAQ entry on failed hot-patches. The advisory calls out one known cause: a distribution upgrade on the host since UnrealIRCd was compiled can break the build. In that case, upgrade instead (see below).

How do you verify the UnrealIRCd hot-patch worked?

Run the module-status command on the server and check the version of the labeled-response module. A patched server shows the hot-patch bundle name or version 6.2.7.1; an unpatched one shows only the old module version.

On 6.0.2 and later:

./unrealircd module-status|grep labeled-response

Read the output this way:

  • labeled-response 5.0-hot-patch-bundle-20261107: the hot-patch is installed.
  • A version showing 6.2.7.1: the server runs the fixed release.
  • 5.0 with no bundle name: the hot-patch did not apply. Repeat step 2 or upgrade instead.
  • No output at all: check from IRC instead.

To check from IRC as an operator, run MODULE -all on the local server and find labeled-response in the list. For another server on the network, use MODULE -all remote.server.name. This is the fastest way to confirm a whole network from one session.

Upgrade when the hot-patch is not an option

On Unix systems, run the built-in upgrade and then restart the server:

./unrealircd upgrade

On Windows, or if you prefer a clean install, download 6.2.7.1 from unrealircd.org. A restart disconnects that server's users, so schedule it per server and let users reconnect to other linked servers in the meantime.

How do you protect UnrealIRCd 5 servers?

Add a line to the configuration on every UnrealIRCd 5 server that blacklists the labeled-response module, then restart the server. A rehash is not enough, because the module is already loaded until the process restarts.

blacklist-module "labeled-response";

UnrealIRCd 5 reached end of life on July 1, 2023, and receives no fixes. The blacklist removes this one attack path. The other eight bugs fixed in 6.2.7.1 may also affect it, and the maintainer did not test 5.x, 4 or 3.2.x for them. Put the end-of-life servers on a dated plan to move to version 6.

Check for signs of misuse

The project reported exploitation starting within two days of the release. After patching, review each server's logs from November 7 onward:

  • KILL and GLINE actions that no operator recalls issuing.
  • Bans, kills or mode changes attributed to a server rather than a person.
  • New or changed operator accounts and server links.

Anything unexplained means someone exercised server authority on your network. Review operator credentials, link passwords and services accounts, and keep the logs.

Quick checklist

  1. SPAMFILTER workaround applied once, network-wide.
  2. Hot-patch run on every 6.0.0 to 6.2.7 server.
  3. module-status or MODULE -all shows the bundle or 6.2.7.1 everywhere.
  4. Failed or Windows servers upgraded to 6.2.7.1 and restarted.
  5. UnrealIRCd 5 servers blacklist labeled-response and were restarted.
  6. Logs reviewed since November 7.

For the root cause, see what CRLF injection is and how to prevent it. For why one module bug reached every server, read why linked server trust turns one bug into a takeover.