CVE-2026-114713, a vulnerability in the IRC server UnrealIRCd, was added to the KEV catalog of CISA (the US cybersecurity agency) on November 13, 2026. KEV is a catalog of vulnerabilities that have been exploited in real attacks. UnrealIRCd's "labeled-response" module does not escape the IRCv3 "label" message tag when it echoes the tag into replies. As a result, on a network with two or more linked servers, an ordinary user may be able to inject newlines and other characters into server-to-server traffic and have commands run with server authority (the NVD description).
If you run UnrealIRCd, first put in the workaround the maintainer gives, then apply the hot-patch or upgrade to 6.2.7.1 on every server. The maintainer released the fixed version 6.2.7.1 and a hot-patch (bundle-20261107) on November 7. According to the maintainer, an ordinary user can run commands such as KILL (forcibly disconnect a user) and GLINE (ban from the whole network) with server or IRCOp (operator) authority.
Where the score comes from: 7.7 (CVSS v3.1) was assigned by NIST (the NVD) and is rated HIGH. The vector reads: over the network, low attack complexity, low privileges required, no user interaction, scope changed, high impact on integrity. The score from the CVE record side (via MITRE) is 8.6 (HIGH), with the required privileges set to "none." This article uses NIST's 7.7.
What is happening (as publicly stated)
- ▸CVE-2026-114713: the "labeled-response" module in UnrealIRCd 6.0.0 before 6.2.7.1 does not escape the IRCv3 "label" message tag when echoing it into replies. On a network with two or more linked servers, any user can inject newlines and other characters into server-to-server traffic, and the commands run with server authority (the NVD description). The maintainer explains that, because IRC is a text protocol, being able to inject newlines means being able to send arbitrary commands. The weakness type is CWE-140 (improper neutralization of delimiters)
- ▸The maintainer's assessment: the maintainer calls this "the most critical issue found in UnrealIRCd in the past 15 years." The same release also fixes 8 other security issues (two that leak IP addresses, issues that hang or crash the server, and others). The maintainer writes that the issues were found during an internal audit done with the help of AI
- ▸CISA KEV: added on November 13, with a CISA due date of November 16. Use in ransomware campaigns is listed as "Unknown," and CISA marks the entry as requiring forensic triage (Forensic Triage: Yes). The NVD lists a CISA coordinator assessment that exploitation is "active" and that it is automatable ("yes")
- ▸Affected versions: in the NVD description, 6.0.0 up to but not including 6.2.7.1. However, the maintainer writes that UnrealIRCd 5, which reached end of life on July 1, 2023, is also affected by the same critical issue. Older versions (3.2.x and 4) have not been checked by the maintainer
- ▸Timeline: the maintainer released the fix on Saturday, November 7; the NVD entry was published on November 8, and it was added to KEV on November 13
What to do today (if you run UnrealIRCd)
- ✓★Step 1: put in the workaround right now. The maintainer tells you to add this spamfilter as an IRCOp: SPAMFILTER add -regex T block - Invalid_label ^label=(?![^\r\n;\x20]*\z). It protects you only if all servers on the network are on 6.0.4 or newer. It does not cover the other 8 issues, so you must also do the next step
- ✓★Step 2a: install the hot-patch (no restart). On each server running 6.0.0 to 6.2.7, run ./unrealircd hot-patch bundle-20261107. If the last line says "Patch installed and server rehashed correctly. All should be good now!", it worked. On Windows, or on a UNIX-like system where the hot-patch fails, go to step 2b
- ✓★Step 2b: upgrade to 6.2.7.1 (with a restart). On a UNIX-like system run ./unrealircd upgrade and then restart. On Windows, get 6.2.7.1 from the official site
- ✓Check that you are fixed. On 6.0.2 and later, run ./unrealircd module-status|grep labeled-response. If it shows "labeled-response 5.0-hot-patch-bundle-20261107," the hot-patch is installed. If it shows "6.2.7.1," you are running the fixed version. If it shows only "5.0," the hot-patch was not applied. If there is no output, run MODULE -all as an IRCOp and look for the labeled-response line. For other servers, use MODULE -all <server name>
- ✓If you run UnrealIRCd 5, move to 6 now. The maintainer says 5 is end of life and nobody should run it. Until you move, add blacklist-module "labeled-response"; to the configuration of every server and restart (do not just rehash)
- ✓Check for signs of a break-in. CISA marks this KEV entry as requiring forensic triage. Review logs for users with IRCOp authority, unexpected KILLs and GLINEs, and configuration changes (our own note). If you are not sure how, ask your security team or the provider that maintains your servers
What we could not confirm
- ▸The latest body of the maintainer's original announcement (forums.unrealircd.org, t=9487). When we wrote this, the site showed a browser check page and we could not read it. The steps above come from the text version of the announcement that the maintainer posted to the oss-security mailing list on November 8. The original announcement may be updated after publication. Read the original directly to check for additions or changed steps. We could not confirm whether anything was added after this article was published
- ▸Details of the exploitation. We confirmed that CISA lists it in KEV and that the NVD carries a CISA coordinator assessment of "active." But the nature of the attacks, their number and the organizations targeted did not appear in the sources we could read. The November 8 text version does not mention any report of exploitation. Whether the maintainer wrote about exploitation afterward we could not confirm, because we could not read the original announcement
- ▸A network with only one server. The NVD says "two or more linked servers." We could not confirm whether a single-server network is affected. Do not assume you are safe; update
- ▸UnrealIRCd 3.2.x and 4. The maintainer has not checked them, so we do not know whether they have the same issue
- ▸Damage in Japan, or how widely it is used in Japan. We cannot show this
If you share this, share these three lines
- ▸CVE-2026-114713 in the IRC server UnrealIRCd was added to CISA's KEV (known exploited) catalog on November 13. On networks with two or more linked servers, an ordinary user may be able to run commands with server authority
- ▸★On every server, apply the hot-patch (./unrealircd hot-patch bundle-20261107) or upgrade to 6.2.7.1. First put in the maintainer's spamfilter workaround
- ▸UnrealIRCd 5 is end of life and is affected by the same issue. Move to 6, and check for signs of a break-in.
