CVE-2026-114713 was published by NVD on November 8, 2026. CISA added it to the KEV catalog on November 13, with a deadline of November 16.
UnrealIRCd is one of the most widely deployed IRC servers. It runs community networks, but also internal ones, as a technical chat channel or a monitoring feed. The flaw affects networks of two or more linked servers: any connected user can get commands executed with server authority.
The Vulnerability
| Field | Value |
|---|---|
| CVE | CVE-2026-114713 |
| CVSS 3.1 (MITRE, CNA) | 8.6 (HIGH) — AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
| NVD score | none yet (status Undergoing Analysis) |
| Type | Improper neutralization of delimiters (CWE-140) |
| Component | labeled-response module |
| NVD publication | 2026-11-08 |
| Added to CISA KEV | 2026-11-13 |
| CISA deadline | 2026-11-16 |
NVD description:
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 It Works
IRCv3 lets a client attach tags to its messages. The label tag ties a reply to the request that triggered it: the server echoes it back in its response.
UnrealIRCd's labeled-response module echoes that value without escaping it. On a single-server network the damage is contained. On a network of linked servers, the reply travels over the server-to-server link, and delimiters slipped into the label let an attacker forge lines the neighbouring server reads as legitimate S2S commands.
The CVSS vector sums it up: no privileges (PR:N), no interaction (UI:N), integrity impact (I:H) and a scope change (S:C): the attacker acts beyond their own session, with the authority of a server on the network.
What that allows in practice depends on the S2S commands the network accepts. NVD doesn't spell it out; server authority typically covers mode changes, operator status and bans, which makes it a tool for taking over the IRC network. That's an inference, not a published scenario.
Affected Versions
Per the NVD description: UnrealIRCd 6.0.0 up to, but not including, 6.2.7.1. So 6.2.7.1 is the first version out of range.
NVD hasn't published a CPE configuration yet. Check the recommended release in the project announcement cited by CISA (UnrealIRCd forum, topic 9487) and in the news section of the official site. The oss-security post of November 8 is also referenced.
Check your version: the /VERSION command from an IRC client connected to the server.
Key point: update every linked server, not just the one users connect to. A single vulnerable server on the network is enough to provide the injection point.
Detection
- Messages with a
labeltag containing delimiters (line breaks, spaces, unexpected:) in the logs, if raw message logging is enabled - Mode, operator or ban changes attributed to a server with no admin action behind them
- Unusual S2S commands on server links
- New operators and configuration changes
Mitigation
1. Move to 6.2.7.1 or later on every server
The CISA deadline is November 16.
2. In the meantime, consider the affected module
If the update has to wait, one option (inferred from the NVD description, not published guidance) is to stop loading the labeled-response module, at the cost of the matching IRCv3 feature. Check the project announcement for any recommended workaround.
3. After patching
- Review the operator list and granted privileges
- Rotate link and operator passwords
- Review bans and modes set during the exposure window
Why Continuous Monitoring of Self-Hosted Software Matters
An IRC server set up years ago for an engineering team doesn't show up in any security inventory. That's exactly the kind of service that misses a KEV addition.
With cveo.tech, register your self-hosted software with its version too, and get an alert as soon as a CVE affecting it is published or enters the CISA KEV catalog.