UnrealIRCd: exploited label tag flaw (CVE-2026-114713)
CISA adds UnrealIRCd CVE-2026-114713 to the KEV catalog: the unescaped IRCv3 label tag lets users inject server-to-server commands. What to do now.

On 13 November 2026 CISA, the US cybersecurity agency, added CVE-2026-114713 in UnrealIRCd, an IRC server software, to its Known Exploited Vulnerabilities (KEV) catalog. Inclusion in the catalog means CISA has evidence of real-world exploitation. The vulnerability affects the labeled-response module and, according to the description published in the National Vulnerability Database (NVD), allows injecting server-to-server commands that are executed with server authority.
This article is based on a single institutional source, the KEV catalog entry with NVD data: every detail below comes from there.
What happened
The CVE was published in the NVD on 8 November 2026; on the same day a message appeared on the oss-security list, which the entry cites as a reference together with the vendor’s forum and news page. On 13 November CISA added the vulnerability to the KEV catalog as “UnrealIRCd Improper Neutralization of Delimiters Vulnerability” and set 16 November 2026 as the deadline for US federal agencies to act.
The catalog does not say who is exploiting the flaw or against which targets; use in ransomware campaigns is marked as “unknown”. At the date of the entry, NVD analysis was still under way.
Technical details
- CVE: CVE-2026-114713
- Product: UnrealIRCd, labeled-response module
- Affected versions: from 6.0.0 to versions before 6.2.7.1
- Weakness: CWE-140, improper neutralization of delimiters
- CVSS 3.1: 8.6 (high), vector
AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N, score assigned by MITRE as CNA
To understand the issue, a step back on the protocol helps. IRCv3 extends IRC with message tags, metadata attached to messages. With the labeled-response extension a client can attach a label tag to a command, and the server repeats it in its replies: this way the client knows which request each reply belongs to.
According to the CVE description, the UnrealIRCd module does not escape the value of the label tag when echoing it into replies. This is the typical CWE-140 case: characters the protocol uses as separators come from the user and are not neutralized, so the recipient interprets them as message structure rather than data.
The described consequences are precise:
- the precondition is a network with two or more linked servers (server links are how IRC networks spread users and channels across several machines);
- the attack is within reach of any user on the network, with no privileges and no interaction from others (
PR:N,UI:N); - the injected commands are server-to-server commands, executed with server authority.
The CVSS vector rates a high impact on integrity and no impact on confidentiality and availability, with scope changed (S:C): the effect goes beyond the vulnerable component and reaches the rest of the network. In MITRE ATT&CK terms the scenario corresponds to T1190 – Exploit Public-Facing Application. The source does not publish indicators of compromise or details of the observed attack chain.
Impact for European and Italian companies
The KEV catalog was created for US federal agencies, but it is one of the most widely used references for deciding what to update first: a vulnerability that enters it is exploited, not just theoretical.
The scope covers anyone running an IRC network based on UnrealIRCd, for example for internal technical chat, product communities or support channels. When these are side services with little oversight, the first step is to find them in the inventory. For entities within the scope of NIS2, vulnerability management and the security of exposed systems are part of the required risk-management measures, and a forgotten service is still an asset of the organization.
What to do now
- Inventory. Identify every UnrealIRCd server, including test servers and those run by suppliers, and record the version of each one.
- Update. The description lists versions from 6.0.0 up to before 6.2.7.1 as vulnerable: bring every server in the network to that version or a later one, following the vendor announcement cited in the entry.
- Vendor measures. CISA asks to apply mitigations according to the vendor’s instructions and, if none are available, to discontinue use of the product. If you cannot update right away, check the vendor announcement for any temporary measures.
- After-the-fact checks. CISA’s required action also refers to its forensic triage requirements: besides updating, review the logs of the linked servers for server-to-server activity that cannot be traced back to administrators.
- Exposure. Assess whether the IRC network really needs to be reachable from the Internet, or whether access from the internal network or a VPN is enough.
How ARXDOME can help
ARX Expose shows what can be seen of your company from outside, including exposed and vulnerable services, while ARX Scout, with your authorization, checks the ports and services of your public addresses and alerts you when a previously closed one opens. For monitored machines, ARX Shield reports open vulnerabilities, so an IRC server that has fallen behind on updates does not go unnoticed.
Last updated:


