CVE-2026-114713: UnrealIRCd Improper Neutralization of Delimiters Vulnerability

Headline from UnrealIRCd — UnrealIRCd · compiled from 3 sources

Our analysis · checked against 9 sources

UnrealIRCd flaw lets ordinary users run server commands; patched, now being exploited

A bug in UnrealIRCd 6.0.0 before 6.2.7.1 lets any user on a network of two or more linked servers inject commands run with server authority; it is rated 8.6 (High), not Critical (9.0–10.0). A fix shipped on 7 November, exploitation attempts reportedly began a day later, and CISA set US federal agencies a 16 November deadline.

The framing"Critical CVEs" does fit an actively exploited flaw on CISA's KEV list that the vendor calls its worst in 15 years. But its official CVSS score is 8.6, rated High, below the 9.0 Critical band.

What the headline leaves out

  • The formal score is 8.6 High, not Critical; VulDB scores it 7.3–7.9.
  • UnrealIRCd 5, end-of-life since July 1, 2023, is also affected and unfixed; the workaround is blacklisting the labeled-response module and restarting.
  • Only networks of two or more linked servers are exposed, but the default configuration loads the module; impact is on integrity, not confidentiality or availability.
  • CISA's deadline binds only US federal civilian agencies; no penalty for private operators.

What happens next

The US federal remediation deadline under BOD 26-04 falls on 16 November 2026. Trade reporting flags that UnrealIRCd 5, end-of-life since 2023, gets no fix and needs the labeled-response module blacklisted plus a restart. Ostorlab warns a blocked attempt may leave no log trace. Security Affairs reports no attacker or motive has been identified.

Possible knock-on effects
  • Networks still on end-of-life UnrealIRCd 5 get no patch, so operators who skip the module-blacklist workaround may stay exploitable, which matters to users of those networks. (mechanism: Version 5 is outside the 6.2.7.1 fix path; only blacklisting the labeled-response module closes it.. Watch for: Reports of compromises on version 5 networks, or a vendor statement on version 5.)
  • KEV listing could prompt non-federal operators to prioritise this patch, which may narrow the exposed population. (official assessment: CISA encourages every organization to prioritize KEV entries, though the directive binds only federal agencies.. Watch for: Published scan data on patched vs unpatched UnrealIRCd servers.)

Sources: CVE-2026-114713 record (primary), Ostorlab: UnrealIRCd command injection CVE-2026-114713 (primary), The Hacker News: Attackers exploit UnrealIRCd flaw, WindowsForum: CISA KEV alert, VulDB 432779, SecurityOnline: UnrealIRCd vulnerability exploited, Security Affairs: CISA adds Check Point and UnrealIRCd flaws to KEV, UnrealIRCd official site (primary), UnrealIRCd GitHub (primary)

Written in our own words from the sources above, and checked claim by claim before it was published. The report below says only what each outlet said.

The report: what outlets said

According to SecurityOnline, the UnrealIRCd project calls this "the most critical issue found in UnrealIRCd in the past 15 years."[1]

The Hacker News reports that CISA on Friday added the high-severity UnrealIRCd flaw to its Known Exploited Vulnerabilities (KEV) catalog[2]. The outlet says the bug, tracked as CVE-2026-114713 (CVSS score: 8.6), could be used to execute arbitrary commands with server/IRCOp privileges.[2]According to the NVD description quoted by The Hacker News, the labeled-response module "does not escape the IRCv3 'label' message tag when echoing it into replies"[2].SecurityOnline quotes the project as warning that "We are seeing bad guys exploiting this issue on the internet right now."[1] It also reports that with the flaw, "any ordinary user can KILL, GLINE, and do many more bad things."[1]Ostorlab reports that every UnrealIRCd 6.0.0 to 6.2.7 server that loads the module, which the default configuration does, is exposed[3] on networks with linked servers. It adds that no indicators of compromise have been published.[3]According to Ostorlab, UnrealIRCd shipped 6.2.7.1 and a hot-patch on November 7, 2026.[3] SecurityOnline says the flaw is one of nine fixed in that release[1], and that the team found the bug during an internal audit "with the help of AI."[1]The Hacker News reports that federal civilian agencies have until November 16, 2026, to apply the fixes[2].

Listen to the songCritical CVEs — November 16, 2026

Sources

  1. [1]UnrealIRCd Vulnerability CVE-2026-114713 Exploited in the Wild, Lets Users Run IRCOp Commands
  2. [2]Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection
  3. [3]UnrealIRCd Command Injection, Exploited in the Wild (CVE-2026-114713) | Ostorlab

Every sentence here reports what a named outlet said, with a link to it. Compiled by 93 from the reporting below.

This topic, day by day

CVE-2026-114713: UnrealIRCd Improper Neutralization of Delimiters Vulnerability | 93