UnrealIRCd CVE-2026-114713 Exploited, Added to CISA KEV
UnrealIRCd CVE-2026-114713 lets any user on linked servers run commands with server authority. It is exploited and in CISA KEV. Hot-patch now.
UnrealIRCd CVE-2026-114713 lets any ordinary user on a network with two or more linked servers inject commands that run with server authority. The project shipped UnrealIRCd 6.2.7.1 and a no-restart hot-patch on November 7, 2026, then warned two days later that attackers were exploiting it. CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 13 with a November 16 deadline. If you run UnrealIRCd 6.0.0 through 6.2.7, hot-patch or upgrade every linked server today.
What happened with UnrealIRCd CVE-2026-114713
UnrealIRCd maintainer Bram Matthys (Syzop) pre-announced a critical security release on November 4, 2026 and published it on Saturday, November 7 at 15:00 UTC. The release fixes nine security issues. One of them, CVE-2026-114713, the project calls the most critical UnrealIRCd issue in 15 years. According to the oss-security advisory, the issues were found during an internal audit assisted by AI.
The CVE record was published on November 8. By November 9 the project had added an exploitation notice to its advisory, quoted in press coverage as "We are seeing bad guys exploiting this issue on the internet right now." Red Hat's tracking bug for the flaw records the same thing: "Upstream reports active exploitation attempts."
CISA added CVE-2026-114713 to the KEV catalog on November 13, 2026. The due date for federal agencies is November 16, three days later, and CISA marked the entry for its forensic triage requirements. Ransomware use is listed as unknown.
Who is affected
The CVE record lists UnrealIRCd 6.0.0 before 6.2.7.1 as vulnerable. The flaw sits in the labeled-response module, which is part of the standard build. Exploitation needs a network with at least two linked servers, which describes most public IRC networks and many internal chat deployments that link a hub and leaf servers for redundancy.
Specific groups to check:
- UnrealIRCd 6 networks on any release from 6.0.0 to 6.2.7. The hot-patch covers this whole range.
- UnrealIRCd 5 networks. Version 5 is affected by the critical issue and has been end of life since July 1, 2023. No fix is coming for it.
- Older releases (3.2.x and 4). The maintainer did not test these. He notes that many of the bugs fixed in 6.2.7.1 likely date back to 3.2.x.
- Distribution packages. Red Hat's bug notes that EPEL 9 still ships unrealircd-6.1.10-1.el9, which is in the affected range. A patch was attached on November 8, but the Fedora and EPEL tracking bugs were still open on November 9. Check your package version rather than assuming a repository update has landed.
Single-server deployments with no links are outside the stated exploitation condition, but they still receive the other eight fixes and should be updated.
Technical analysis
IRCv3 lets clients attach message tags to commands. The labeled-response extension lets a client add a label tag to a request so the server can copy the same label onto its reply. The IRCv3 message-tags specification requires tag values to escape semicolons, spaces, backslashes, carriage returns and line feeds, because those characters delimit tags and protocol lines.
UnrealIRCd's labeled-response module did not escape the label when echoing it back into replies. Because IRC uses line breaks to separate commands, an unescaped label can carry extra protocol lines into server-to-server traffic. A linked server then treats those lines as if they came from a trusted peer. That is the failure class CWE-140, improper neutralization of delimiters, and it is a close relative of CRLF injection.
The impact is control of the network rather than code execution on the host. The advisory says a normal user can run commands with server or IRC operator authority, such as KILL (disconnect a user) and GLINE (network-wide ban). The CVE record scores it CVSS 3.1 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N): no privileges, no user interaction, high integrity impact and a changed scope, because the damage crosses from one server to every server that trusts it. The project rates it higher than the score suggests, and that is reasonable for operators: one unprivileged connection can reshape a whole linked network. The trust model behind linked servers is why a single module bug reaches that far.
The other eight fixes include two ways for a normal user to reveal another user's IP address, a crash a normal user can trigger through CHGIDENT from Services, a blacklist recheck that could hang the server, a counting error that rejects all new connections as "server full," a possible TLS renegotiation flood and a possible crash in whowasdb.
What to do now
Work through these on every server in the network, not only the one users connect to.
- Apply the network-wide workaround first. The advisory gives a one-line SPAMFILTER command, run as an IRC operator, that blocks label tags containing invalid characters. Copy it exactly from the oss-security advisory rather than retyping it. The advisory notes it protects the network only when all linked servers run 6.0.4 or newer.
- Hot-patch UnrealIRCd 6.0.0 through 6.2.7. From the UnrealIRCd directory, run
./unrealircd hot-patch bundle-20261107. No restart is needed. Our step-by-step guide covers how to hot-patch UnrealIRCd and verify the fix on each server. - Verify. On 6.0.2 and later,
./unrealircd module-status|grep labeled-responseshould show the hot-patch bundle or version 6.2.7.1. As an operator,MODULE -all remote.server.namechecks a remote server. - Upgrade if the hot-patch fails. On Unix systems, run
./unrealircd upgradeand restart. Windows administrators download 6.2.7.1 from unrealircd.org. - UnrealIRCd 5 servers. Add
blacklist-module "labeled-response";to the configuration on every server, then restart (a rehash is not enough). Plan the move to version 6. - Review logs for misuse. Look for KILL, GLINE and other operator actions since November 7 that no operator remembers issuing, and for bans or kills attributed to servers rather than people. Treat unexplained ones as a compromise of network integrity and review your services and operator accounts.
Federal agencies under CISA's directive have until November 16. Everyone else should treat that date as the target too.
What to watch next
The project released UnrealIRCd 6.2.8-rc1 for testing on November 14 and pushed a separate security update for its web panel the same day. Watch for:
- Indicators of compromise or a description of what attackers did after gaining server authority. None has been published yet.
- The EPEL 9 and Fedora package updates closing Red Hat's tracking bugs.
- Any patch bypass or follow-up advisory. The release was the product of an AI-assisted audit, and similar tooling is available to attackers.
IRC software is often run by volunteers and sits outside formal patch management. Teams that link chat servers, as some voice platforms link SIP servers, saw the same lesson in the FreeSWITCH CVE-2026-116779 exploitation earlier this week: protocol messages trusted by a peer are an attack path.