CISA added an UnrealIRCd flaw, CVE-2026-114713, to its Known Exploited Vulnerabilities (KEV) catalog on November 13, 2026. The bug sits in how UnrealIRCd, a widely used IRC server, handles the IRCv3 “label” message tag, and it lets an ordinary user on a multi-server network run commands with server authority. UnrealIRCd released a fix on November 7: version 6.2.7.1 and a hot-patch that needs no restart. If you run an IRC network, here are the affected versions, the exact patch steps and what is still unknown.
What is the UnrealIRCd flaw CVE-2026-114713?
According to the vendor advisory posted by maintainer Bram Matthys on the oss-security mailing list, the critical issue is an escaping bug in UnrealIRCd’s implementation of the IRCv3 “label” message tag. Any user can inject newlines and other characters into server-to-server traffic. Because IRC is a text protocol, that lets the injected text act as commands. The advisory says this lets ordinary users act with server or IRC operator authority, for example running KILL or GLINE. The NVD description, as quoted by The Hacker News, says the attack needs a network with two or more linked servers. The flaw is rated CVSS 8.6 (high).
Which UnrealIRCd versions are affected?
- UnrealIRCd 6.0.0 through 6.2.7: affected. The fix ships in 6.2.7.1, and the hot-patch works on this range.
- UnrealIRCd 5: the advisory says it is also affected by the critical issue. It has been end of life since July 1, 2023, so there is no patch; the advice is to move to version 6.
- Older end-of-life branches (3.2.x and 4): not checked, but the author says several of the bugs likely go back to 3.2.x.
How do you patch it?
The advisory gives these steps for supported 6.x servers:
- On every server in the network, as the user that runs UnrealIRCd, run
./unrealircd hot-patch bundle-20261107. No restart is needed. - Check it worked with
./unrealircd module-status | grep labeled-response. A secondary write-up (DEV Community) says the output should show the 20261107 hot-patch bundle or version 6.2.7.1; a bare “labeled-response 5.0” means the patch is not installed. - If the hot-patch is not possible or fails, including on Windows, upgrade to 6.2.7.1 and restart the server.
The same release fixes other bugs too, according to the advisory: two ways to reveal a user’s IP address, a hang in blacklist rechecks, a crash tied to Services’ CHGIDENT command, a counting error that can block new connections with a “server is full” message until restart, a possible TLS renegotiation flood issue and a possible crash in whowasdb.
Is there a workaround if you cannot patch yet?
Yes. For version 6, an IRC operator can add a SPAMFILTER rule that blocks the malicious label pattern. The advisory says this protects the network against the critical issue only if all servers run 6.0.4 or newer, and the exact rule text is in the advisory. For UnrealIRCd 5, add blacklist-module "labeled-response"; to the configuration on every server and restart them (a rehash is not enough). Treat these as stopgaps, not a replacement for patching.
Is it being exploited, and what is the CISA deadline?
CISA’s November 13 alert adds CVE-2026-114713 (UnrealIRCd, improper neutralization of delimiters) and a Check Point flaw, based on evidence of active exploitation. The Hacker News reports that exploitation attempts began a day after the November 7 hotfix, quotes Matthys saying “We are seeing bad guys exploiting this issue on the internet right now,” and says federal civilian agencies must apply the fix by November 16, 2026 under Binding Operational Directive 26-04. Note that the original advisory itself does not describe in-the-wild exploitation; the exploitation claims come from the developer’s later statements as reported and from the CISA listing. For the Check Point entry, see our Check Point write-up, and for the wider list, Exploited This Week.
What is still unknown
- What attackers do after getting server-level access, and who they are. The Hacker News says the activity and goals are unknown.
- How many networks were hit. No figure has been published in the sources checked.
- Whether the 20261107 hot-patch needs anything extra on heavily customized networks; check the advisory for your version.
The author says the bugs were found during an internal audit with AI assistance, and argues that servers without recent security fixes may not have been examined the same way, a reason to avoid end-of-life software.
Sources: UnrealIRCd 6.2.7.1 Security Release and Hot-Patch, oss-security (Nov 2026); CISA, Nov 13, 2026; The Hacker News, Nov 14, 2026.
Like our coverage? Add stepphase.com as a preferred source on Google to see more of our stories in Top Stories.
