UnrealIRCd: Exploited Flaw CVE-2026-114713
Published November 13, 2026 · Last updated November 13, 2026
What happened: On November 13, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-114713, a flaw in UnrealIRCd, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "UnrealIRCd Improper Neutralization of Delimiters Vulnerability."
CISA's summary: "UnrealIRCd UnrealIRCd contains an improper neutralization of delimiters vulnerability that allows any user on a network with two or more linked servers to inject server-to-server commands that are executed with server authority."
CVE-2026-114713 is a flaw in UnrealIRCd, a widely deployed open-source server for Internet Relay Chat (IRC) networks. It lets any ordinary user on a network of linked servers slip commands into the traffic between those servers, where they run with full server authority. UnrealIRCd's maintainer calls it "the most critical issue found in UnrealIRCd in the past 15 years."
The maintainer released a fix on November 7, 2026, and the CVE record was published on November 8, 2026 (UTC). On November 13, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the flaw to its Known Exploited Vulnerabilities (KEV) catalog, with a due date of November 16, 2026. CISA lists known ransomware campaign use as "Unknown."
What goes wrong
IRCv3, a set of modern extensions to IRC, includes a "label" tag. A client can attach a label to a command so it can match the server's reply to the request. UnrealIRCd supports this through its labeled-response module.
According to the CVE record, that module "does not escape the IRCv3 'label' message tag when echoing it into replies." In the maintainer's announcement to the oss-security mailing list, Bram Matthys explains why that matters. Any user can inject newlines and other content into server-to-server traffic, he writes, and "in a text protocol like IRC this means one can issue arbitrary commands, in this case with server authority."
IRC treats each line of text as a separate command. If a user can sneak a line break into a value that one server forwards to another, the receiving server reads the rest as a new instruction from a trusted peer. CISA describes the weakness as improper neutralization of delimiters (CWE-140). Its catalog summary says the flaw "allows any user on a network with two or more linked servers to inject server-to-server commands that are executed with server authority."
The maintainer says the problem turned up "during an internal audit, with the help of AI," along with the other issues fixed in the same release.
What an attacker can do
The maintainer's advisory says the bug "allows normal users to execute commands with server/IRCOp authority," and that "any ordinary user can KILL, GLINE, and do many more bad things." IRCOps are network operators. KILL disconnects a user, and GLINE bans users or addresses across the whole network. In the wrong hands, those powers could be used to throw people off a network or lock out legitimate users and staff.
According to the CVE record, the attack needs "a network with two or more linked servers." A single standalone server is not described as exposed to this particular issue. No account beyond a normal connection is required.
Affected and fixed versions
The CVE record lists UnrealIRCd 6.0.0 up to, but not including, 6.2.7.1 as affected. The maintainer also warns that UnrealIRCd 5, which reached end of life on July 1, 2023, "is similarly affected." Older end-of-life releases were not checked.
The fixed release is UnrealIRCd 6.2.7.1. Its release notes in the official repository call it "a security release" that fixes "a CRITICAL bug that allows any ordinary user to execute commands with server or IRCOp authority." The same release fixes eight other problems found in the same audit, including crashes, hangs, a way to reveal another user's IP address, and a flood issue with TLS renegotiation. The advisory's full list also covers a second IP address leak, a server hang during blacklist rechecks, a crash on a CHGIDENT command from Services that a normal user can trigger, a counting error that can make the server reject every new connection as full until it is restarted, a new cap on how many bans Services can set, and a possible crash in the whowas database. Those issues do not have CVE numbers in the material we reviewed. The project's development branch, which will become 6.2.8, already includes the same fixes.
How to fix it
The maintainer's advisory lays out the steps in order. Run them on every server in the network.
- Apply the network workaround first. As an IRCOp, add the spamfilter rule the advisory gives, which blocks labels containing line breaks, semicolons or spaces. It protects all linked servers, but only if every server runs 6.0.4 or newer. It does not cover the other eight issues.
- Hot-patch without a restart. On Unix-like systems running 6.0.0 through 6.2.7, run
./unrealircd hot-patch bundle-20261107. This is not available on Windows. The maintainer says that on almost all UnrealIRCd 6 networks, a single hot-patch bundle covers all nine issues without downtime. If it fails, the project's FAQ entry on failed hot-patching covers common causes, including an operating system upgrade that breaks the build. - Or upgrade. Run
./unrealircd upgradeand restart, or download 6.2.7.1 from the UnrealIRCd website. Windows servers must use this route.
To confirm the result on 6.0.2 or later, run ./unrealircd module-status and look at the labeled-response line, or use MODULE -all on IRC as an IRCOp. A version ending in "hot-patch-bundle-20261107," or showing 6.2.7.1, means the server is safe. A plain "5.0" with no patch bundle means the hot-patch did not apply. IRCOps can also check other servers from IRC with MODULE -all followed by the remote server's name, which helps confirm that every linked server is covered.
For UnrealIRCd 5, the maintainer's stopgap is to add blacklist-module "labeled-response"; to the configuration on every server and restart it, not just rehash. The real answer is to move to UnrealIRCd 6.
Severity and who scored it
MITRE, which assigned the CVE, scored it CVSS 3.1 8.6 (High), vector AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N. NVD shows that same MITRE score as a Secondary source; NVD had not added its own score when we checked, and its analysis was still in progress. The score reflects an attack over the network, by anyone, with no user interaction, that reaches beyond the server the attacker first touches.
CISA's own decision data marks exploitation of this flaw as "active," automation as "yes," and technical impact as "total." Neither CISA nor the maintainer has published details of who was attacked or how.
Who should act
- IRC network operators and server administrators: apply the workaround now, then hot-patch or upgrade every linked server and verify the module version.
- Anyone still running UnrealIRCd 5 or older: apply the stopgap and plan a move to UnrealIRCd 6. These versions get no fixes.
- U.S. federal agencies: the KEV entry says to apply mitigations according to the vendor's instructions by November 16, 2026, following CISA's BOD 26-04 guidance and its forensics triage requirements, or to stop using the product if no mitigation is available.
Sources: the UnrealIRCd maintainer's advisory as posted to oss-security on November 8, 2026; UnrealIRCd 6.2.7.1 release notes in the official repository; the CVE record; the CISA Known Exploited Vulnerabilities catalog; NVD.
What the National Vulnerability Database says
NVD first published CVE-2026-114713 on November 8, 2026. Its description, from the record's source ([email removed]), reads: "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, which allows any user on a network with two or more linked servers to inject server-to-server commands that are executed with server authority."
How serious is CVE-2026-114713?
The CVSS 3.1 base score is 8.6 out of 10 (High), scored by mitre.org. In plain terms: an attacker can reach the UnrealIRCd weakness over a network, including the internet; the attacker does not need an account; no one has to click or open anything. The listed impact on UnrealIRCd data secrecy is none, on data integrity high, and on availability none. The full vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N.
Which UnrealIRCd versions are affected?
The CVE record lists these affected ranges:
- versions before 6.2.7.1
If your UnrealIRCd version falls in one of these ranges, check UnrealIRCd's advisory for the fixed release that applies to you.
What kind of weakness is it?
CISA and NVD map CVE-2026-114713 to the following weakness type in MITRE's Common Weakness Enumeration (CWE):
- CWE-140: Improper Neutralization of Delimiters. MITRE's definition: "The product does not neutralize or incorrectly neutralizes delimiters."
CISA required action for CVE-2026-114713
CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines."
Timeline for CVE-2026-114713
- November 13, 2026: CISA adds CVE-2026-114713 to the KEV catalog.
- November 13, 2026: latest change to the NVD record (status: Undergoing Analysis).
- November 16, 2026: due date for U.S. federal civilian agencies to act on CVE-2026-114713.
- November 8, 2026: NVD publishes CVE-2026-114713.
Advisories and technical references
The NVD record for CVE-2026-114713 links to these references; tags in brackets are NVD's labels:
- forums.unrealircd.org/viewtopic.php?t=9487
- www.unrealircd.org
- www.unrealircd.org/index/news
- www.openwall.com/lists/oss-security/2026/11/08/1
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-114713
What to do
- Run UnrealIRCd? Follow UnrealIRCd's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
- Federal civilian agencies must act by November 16, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for UnrealIRCd too.
- Ransomware use: CISA lists known ransomware campaign use for CVE-2026-114713 as "Unknown".
- Don't run UnrealIRCd yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2026-114713" and asks for payment or remote access, that is a scam pattern, not a UnrealIRCd alert.
CVE-2026-114713 record details from CISA and NVD
- CISA forensic triage flag for CVE-2026-114713: Yes
- Attack complexity for CVE-2026-114713: low
- CVE-2026-114713 CVSS scope: changed
- NVD sub-scores for CVE-2026-114713: exploitability 3.9, impact 4.0.
- Who mapped the weakness type: the address listed on mitre.org (Secondary)
- References in the NVD record: 5.
- CISA SSVC decision points for CVE-2026-114713 (from NVD): exploitation=active; automatable=yes; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.