Koffei

CVE-2026-114713

🔴 High In CISA KEV

UnrealIRCd — the labeled-response module. The flaw only bites on a network of two or more linked servers, because the injected text has to reach the server-to-server protocol. The project describes the outcome as a normal user performing operator-level actions such as KILL and GLINE, so disconnecting or network-banning any user · 6.0.0 through 6.2.7, fixed in 6.2.7.1. UnrealIRCd 5 is described by the project as similarly affected and has no fix, being end of life since 01/07/2023 ; 3.2.x and 4 were never checked, so their status is unknown rather than safe. The record contradicts itself: its description says the range starts at 6.0.0 while its structured affected entry gives a lower bound of version 0

CVSS (Koffei note)
8.6
CVSS (v3.1, CVE List)
8.6
EPSS (2026-11-18)
0.467%
41.11th percentile
CISA KEV
2026-11-13
due 2026-11-16

Exploitation

Yes — CISA KEV since 13/11/2026, with a remediation deadline of 16/11/2026, SSVC exploitation active, automatable yes, technical impact total (from the NVD record). The project itself reported live attacks, writing on its forum that it was seeing the issue exploited on the internet at that moment, with abuse attempts starting around 08/11/2026, one day after the fix. Existing PoC (not opened, no link recorded), from two entries visible in a Sploitus search result for this id. The cvelistV5 record is five days stale and badly misleading on this row: read on 14/11/2026 it still shows no SSVC values and no kev block, while NVD carries the KEV entry, the deadline and an active SSVC assessment. Anyone triaging this from cvelistV5 alone would rate it unexploited. CISA KEV itself could not be reached this run, so the KEV date and deadline come from the NVD record and the coverage

Timeline

  1. 08/11/2026CVE record published (CVE List)
  2. 13/11/2026UnrealIRCd label-injection flaw exploited, in CISA KEV with a 16/11 deadline
  3. 13/11/2026Added to the CISA KEV catalogue
  4. 16/11/2026UnrealIRCd label-injection flaw: exploited, KEV deadline today
  5. 16/11/2026CISA deadline for US federal agencies

Risk

8.6 High (v3.1, MITRE CNA, the only score in the record and the one NVD carries as secondary) — AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N, EPSS 0.508% (43.88th percentile, FIRST.org 15/11/2026; it was 0.302% on 13/11/2026) — a 0.5% EPSS on a KEV-listed flaw under active exploitation, which is what EPSS does with niche server software (CWE-140 improper neutralization of delimiters: the labeled-response module does not escape the IRCv3 label message tag when reflecting it in replies, in labeled_response_mtag_is_ok() of src/modules/labeled-response.c. The integrity-only impact with scope change is accurate: nothing is read out, but commands cross into the server-to-server protocol)

Fix

Yes — 6.2.7.1, and there are two ways to fix it without upgrading, which matters on an IRC network nobody wants to restart. The bundle-20261107 hot-patch applies to 6.0.0 through 6.2.7 and fixes all nine issues without a restart. The workaround is an IRCOp spamfilter rule, published by the project, that blocks invalid labels and protects linked servers on 6.0.4 or newer. On UnrealIRCd 5 the only route is to blacklist the labeled-response module, restart, and move to 6

Official 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.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

CWE-140