UnrealIRCd CVE-2026-114713 lets ordinary chat users act as the server; here's how to hot-patch it on your clients' IRC servers.
On an UnrealIRCd chat network with two or more linked servers, an ordinary user could speak with the server's own authority, disconnecting and banning whoever they like. CISA added that flaw, CVE-2026-114713, to its Known Exploited Vulnerabilities catalog on 13 November 2026, four days after the project warned it was under attack. Check every client's IRC servers today.
module-status shows the patch level.bundle-20261107 or upgrade to 6.2.7.1 on every server, as UnrealIRCd's advisory directs; on version 5, blacklist the labeled-response module and restart.CVE-2026-114713 is an UnrealIRCd vulnerability, a delimiter-escaping flaw (CWE-140) in the labeled-response module of the open-source IRC server; IRC is the decades-old group-chat protocol. The module doesn't escape the IRCv3 "label" tag, a note an app attaches to match replies, so any user on a network of two or more linked servers can inject commands that run with server authority, per the CVE record. Maintainer Bram Matthys calls it "the most critical issue found in UnrealIRCd in the past 15 years", and NVD lists it at 8.6 (CVSS).
It is being exploited: according to SecurityOnline, the project said on 9 November 2026, "We are seeing bad guys exploiting this issue on the internet right now."
Every affected line and its fix, from the UnrealIRCd 6.2.7.1 advisory unless noted:
bundle-20261107. The hot-patch doesn't work on Windows, so Windows servers install 6.2.7.1 from UnrealIRCd's release notice.blacklist-module "labeled-response"; plus a full restart, then a move to 6.2.7.1.unrealircd-6.1.10-1.el9: affected, and Red Hat bug 2568818 lists no fixed build yet. Build 6.2.7.1 from source until one ships.The same release fixes eight more bugs, including two that let a normal user reveal another user's IP address, so patch single-server setups too.
Steps 1, 4 and 5 run in one shell session on a Linux IRC server, as a normal user with sudo; steps 2 and 3 run from your machine across the fleet. No fetched source dates the first attack, so search the oldest retained logs. On-disk logs may cover only a short period, so also search the client's syslog archive or SIEM; a clean result can't rule out an earlier break-in. The advisory publishes no indicators of compromise.
Preserve evidence. Copies every install's logs, config and data/ folder, where tkl.db keeps bans, then hashes them. Pass: the hash list includes at least one file under logs/.
D=/root/ir-unrealircd-$(hostname)-$(date +%F)
sudo mkdir -p "$D"
sudo bash -c "cp -a --parents /home/*/unrealircd/logs /home/*/unrealircd/conf /home/*/unrealircd/data \"$D\"/"
# EPEL package installs keep files under /etc and /var/log
rpm -ql unrealircd 2>/dev/null | grep -E '^/(var/log|etc)/' | xargs -r sudo cp -a --parents -t "$D"
sudo find "$D" -type f -exec sha256sum {} + | sudo tee "$D.sha256"
Read each install's patch level. Runs the advisory's own module check on every host in irc-hosts.txt. Pass: each host shows 6.2.7.1 or 5.0-hot-patch-bundle-20261107; a bare 5.0 means unpatched.
# irc-hosts.txt: one irc-user@host per line (installs under ~/unrealircd)
while read -r H; do echo "$H"; ssh -n "$H" 'cd ~/unrealircd && ./unrealircd module-status | grep labeled-response; rpm -q unrealircd 2>/dev/null'; done < irc-hosts.txt
# rpm: EPEL's 6.1.10-1.el9 is affected. Windows servers: as an IRCop, /MODULE -all remote.server.name
Find IRC servers missing from the inventory. Scans the usual IRC ports, 6667 and 6697 per UnrealIRCd's FAQ, across each client's external ranges; IRC also runs on other ports, so the asset inventory stays the primary list. Pass: both ports show closed or filtered on every address without a known IRC server.
nmap -Pn -p 6667,6697 -sV --open -iL client-external-ranges.txt -oG irc-sweep.txt
Search the logs for kills and bans. Matches the disconnect, ban and spamfilter formats in UnrealIRCd's log-message list. Pass: after excluding the client's own opers and services, no lines remain.
# replace the names with the client's opers and services
sudo grep -rahE 'Client killed:|-Line added:|Spamfilter added:' "$D" | grep -vE '\[by: (NickServ|OperServ|<oper-nick>)'
List who became an IRC operator. Shows every oper login the logs recorded, since opers can issue the same commands. Pass: each name shown is one of the client's own opers.
sudo grep -rah 'is now an IRC Operator' "$D"
Close the hole first, then remove what attackers left, then recheck.
Block bad labels now. As an IRCop, add the advisory's spamfilter; it protects the network only if every linked server runs 6.0.4 or newer, per the advisory. Pass: the log's last Spamfilter added: line contains label=.
# on IRC, as an IRCop:
# /SPAMFILTER add -regex T block - Invalid_label ^label=(?![^\r\n;\x20]*\z)
sudo grep -ah 'Spamfilter added:' /home/<irc-user>/unrealircd/logs/* | tail -n 1
Hot-patch every Linux server. Runs the no-restart patch and its check on each host in irc-hosts.txt. Pass: every host prints 6.2.7.1 or 5.0-hot-patch-bundle-20261107.
# irc-hosts.txt: one irc-user@host per line; if a hot-patch fails, run ./unrealircd upgrade
while read -r H; do echo "$H"; ssh -n "$H" 'cd ~/unrealircd && ./unrealircd hot-patch bundle-20261107 && ./unrealircd module-status | grep labeled-response'; done < irc-hosts.txt
Disable the module on version 5 and older. Add the advisory's line to every server's config and restart, since a rehash isn't enough; clients lose labeled replies until the upgrade. Pass: /MODULE -all lists no labeled-response.
# irc-v5-hosts.txt: one irc-user@host per line for servers on version 5 or older
while read -r H; do ssh -n "$H" 'echo '\''blacklist-module "labeled-response";'\'' >> ~/unrealircd/conf/unrealircd.conf && cd ~/unrealircd && ./unrealircd restart'; done < irc-v5-hosts.txt
Remove rogue bans. Lift each ban from check 4 set by someone who isn't a client oper, using the "-" prefix form in the IRCop guide; kills only disconnect, so they need no undoing. Pass: the banned user connects again.
# on IRC, as an IRCop:
# /GLINE -<user@host>
# /SPAMFILTER del <match-type> <target> <action> <tkltime> <reason> <match-string>
Recheck. Rerun checks 2 and 3. Pass: check 2 prints 6.2.7.1 or the bundle line on all hosts.
About two days passed between the fix and the exploitation warning. UnrealIRCd 6.2.7.1 and the hot-patch shipped on 7 November 2026, the oss-sec advisory followed on 8 November, the warning on 9 November, per Daily Security Review, and the CISA KEV listing on 13 November.
The bugs surfaced in an internal audit done with AI help. Matthys writes that he has spent about 100 hours on AI-assisted auditing since February 2026, and argues that daemons with no recent security fixes may simply not have been examined that way yet.
KinoSec's autonomous external network pentest checks whether each client's IRC ports, such as 6667 and 6697, answer from the internet, so a forgotten UnrealIRCd server turns up as a finding with remediation in the report you hand your client. An IRC server set up for a community chat or a legacy developer channel, by someone who has since left, is the kind of service that misses a two-day patch window. The pentest doesn't read the server's logs or module list; checks 2, 4 and 5 do that. For your clients' perimeters, see autonomous internal and external network pentesting with Poseidon. For another self-hosted comms server that took orders from strangers, read how FreeSWITCH phone servers were hijacked by a text message.
A single unlinked server can't be hit by the critical label-tag injection, because the bug needs a network of two or more linked servers, per the CVE record. It is still affected by the other eight bugs fixed in UnrealIRCd 6.2.7.1, including two IP-address leaks, per the advisory. Patch it the same way.
First, read the patch level with ./unrealircd module-status | grep labeled-response as the IRC user in the install folder; 6.2.7.1 or 5.0-hot-patch-bundle-20261107 means patched. Second, search the logs with grep -ahE 'Client killed:|-Line added:' logs/* and review every setter who isn't a client oper or services. Third, list oper logins with grep -ah 'is now an IRC Operator' logs/*.
No. The advisory's SPAMFILTER rule protects the network against the critical issue only if every linked server runs UnrealIRCd 6.0.4 or newer, and it does not fix the other eight bugs, per the advisory. Use it for the minutes before hot-patch bundle-20261107 or 6.2.7.1 goes on.
Only if someone owns them. Ask each client who maintains any IRC server you find and whether it must be reachable from outside; if the client can't name an owner, take it offline. UnrealIRCd 5 has been end-of-life since 2023-07-01, per the advisory, so a server still on it should be upgraded to 6.2.7.1 or retired.