On Saturday, Nov. 7, the UnrealIRCd project shipped version 6.2.7.1 along with a hot-patch for nine security issues. One of them, CVE-2026-114713, was rated critical. The Hacker News reported that exploitation attempts began a day later, and the maintainer says attackers are now exploiting it. Six days later, on Nov. 13, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the flaw to its Known Exploited Vulnerabilities (KEV) catalog. Federal civilian agencies have until Monday, Nov. 16 to deal with it.

UnrealIRCd is an open-source IRC server that its project describes as the most widely deployed IRCd, with a self-reported 38% market share. Maintainer Bram Matthys, who posts as Syzop, called this bug the "most critical issue" found in UnrealIRCd in 15 years, The Hacker News reported. Below is what is known so far.

What is the bug?

The National Vulnerability Database entry puts the problem in UnrealIRCd's labeled-response module. That module supports an IRCv3 feature. IRCv3 is the set of modern extensions to the IRC protocol, and it lets clients attach small pieces of metadata, called message tags, to what they send. One of these is a "label" tag. A client puts a label on a command, and the server copies that label into its reply so the client can tell which reply goes with which request.

According to NVD, UnrealIRCd 6.0.0 through versions before 6.2.7.1 does not escape that label when it echoes it back. Escaping means neutralizing characters that have special meaning in the protocol. Because the label is copied as-is, a user can shape it so that part of it is read as a separate protocol message rather than as data. CISA's KEV entry files the bug under CWE-140, "Improper Neutralization of Delimiters." That is the textbook name for this class of flaw: input that should have been inert data ends up acting as structure.

The flaw matters because of where that injected text ends up. On a network of two or more linked UnrealIRCd servers, the servers trust each other's server-to-server commands. NVD says that on such a network, any user can inject server-to-server commands that are then executed with server authority. The project's own release announcement says it plainly: the critical issue allows normal users to execute commands with server or IRCOp (IRC operator) authority.

How severe is it?

The CVSS 3.1 score from the CVE.org/MITRE source, as shown on NVD, is 8.6, which falls in the "High" band. The vector shows network attack, low complexity, no privileges required, no user interaction, a changed scope and high integrity impact. "Changed scope" means the damage reaches beyond the component that has the bug. Here, a client-facing feature lets someone act as a trusted server.

The number may undersell the practical risk. CISA's SSVC assessment on the NVD record lists exploitation as "active," the attack as automatable, and the technical impact as "total." The maintainer's own "CRITICAL" label and his 15-year comparison point the same way. On an IRC network, server and operator authority is the top of the trust chain.

Is it really being exploited?

Yes, according to the maintainer and CISA. "We are seeing bad guys exploiting this issue on the internet right now," Matthys said, as quoted by The Hacker News. The publication reported that exploitation attempts started a day after the Nov. 7 hotfix. Attackers often study a public fix to find the underlying bug, though no source says that is what happened here.

What the attackers are actually doing is less clear. The Hacker News reported that the specific malicious activity and the attackers' goals are unknown. No source attributes the activity to any named group. CISA's KEV entry lists known ransomware campaign use as "Unknown."

The KEV entry does carry one unusual detail. It marks forensic triage as "Yes," and its required action tells agencies to apply vendor mitigations in line with BOD 26-04 (Prioritizing Security Updates Based on Risk) and CISA's forensics-triage requirements, or to stop using the product if no mitigation is available. Put simply, CISA wants agencies to check whether they were already hit, not just to patch.

Why such a short deadline?

CISA added the bug on Nov. 13 and set a due date of Nov. 16, three days later. The agency's catalog JSON record shows those dates, and The Hacker News reported the same Nov. 16 deadline for Federal Civilian Executive Branch agencies under BOD 26-04. A window that short is consistent with confirmed, ongoing exploitation of a bug that, per NVD's CVSS vector, needs no privileges or user interaction.

The directive only binds federal civilian agencies. KEV is still a widely used public signal that a bug is being exploited, and private-sector operators of UnrealIRCd should read the deadline as a strong hint about urgency.

What It Means for Defenders

Who is affected. NVD lists affected versions as everything before 6.2.7.1. The description names the UnrealIRCd 6 line starting at 6.0.0. Per NVD, the critical injection path needs a network with two or more linked servers. Operators of a single standalone server should still update, because the same release fixed eight other security issues.

The fix. Upgrade to UnrealIRCd 6.2.7.1 or later. The project said that on almost all UnrealIRCd 6 networks, the nine issues can be hot-patched without a restart. Matthys urged operators to hot-patch, update, or deploy the project's spamfilter workaround, according to The Hacker News. Use the workaround only as a stopgap if you cannot patch right away, and take its details from the project's own announcement and forum thread. Do not rely on third-party summaries.

Patch every linked server. The attack abuses trust between linked servers, so an unpatched server may leave the rest of the network exposed. Treat the network as a single patch unit, and confirm the running version on each server instead of assuming.

Look back as well as forward. Exploitation attempts reportedly began around Nov. 8, so any network that was unpatched after that date should be reviewed, as CISA's forensic-triage flag suggests. Check for operator actions, bans, configuration changes or server-level events that no staff member remembers doing. Review who currently holds operator privileges. If anything looks wrong, rotate operator and link credentials once the servers are patched.

Keep an eye on the follow-ups. On Nov. 14 the project posted a 6.2.8 release candidate for testing, along with a security update for the UnrealIRCd webpanel. If you run the webpanel, apply that update as well. The 6.2.8 build is a release candidate for testing, so for now the fixed production baseline is 6.2.7.1.

For CMMC and federal contractors. IRC servers can sit outside formal asset inventories. If you run one in or near a covered environment, add this CVE to your vulnerability tracking with the Nov. 16 date. Record both the patch and any triage you do.

Sources