Taiwan Information Security Association

Security alertsSat, 14 Nov 2026

UnrealIRCd vulnerability exploited on linked networks: patch every server and review operator activity

A regular IRC user can inject server-authority commands on an affected network with two or more linked servers. The UnrealIRCd project reports exploitation and CISA added CVE-2026-114713 to KEV. Upgrade or apply the official hot patch to every affected node.

01

Article

If you run UnrealIRCd across multiple linked servers for a community, support channel or operations team, patch every affected node and review operator activity. A user who can connect to the network can exploit the vulnerable labeled-response module without IRC operator privileges when at least two servers are linked.

The UnrealIRCd project released 6.2.7.1 on 7 November 2026 and subsequently reported exploitation on the internet. The CVE Program published the MITRE CNA record on 8 November with a CVSS v3.1 base score of 8.6. CISA added CVE-2026-114713 to its Known Exploited Vulnerabilities catalog on 13 November and flags it for forensic triage.

The module does not escape the IRCv3 label tag correctly when sending a reply. A crafted label can cause a linked peer to interpret injected commands as server traffic. The project cites examples such as KILL and GLINE, which can disconnect or ban users. The reported authority is at the IRC protocol layer.

Attack flowFrom ordinary IRC client access to server-authority commands
  1. 01

    Connect to a linked network

    The network has at least two linked servers and an affected labeled-response module handles the client’s traffic.

  2. 02

    Trigger a reply containing a crafted tag

    The vulnerable module reflects the IRCv3 label without adequate escaping.

  3. 03

    Inject a command to a peer

    The linked server can interpret the injected data as a server-to-server command.

  4. 04

    Exercise power across the IRC network

    An injected command may disconnect or ban users or alter operator-controlled IRC state.

Affected versions and official fixes
DeploymentVendor guidance
UnrealIRCd 6.0.0 through 6.2.7Upgrade to 6.2.7.1 or apply the official bundle-20261107 hot patch on every eligible Unix-like server.
Windows, or a failed hot patchUpgrade to 6.2.7.1 and restart the service.
End-of-life UnrealIRCd 5The project reports the same type of exposure. Its interim instructions blacklist the labeled-response module on each server and require a full restart. Migrate to a supported fixed release.
Earlier end-of-life branchesThe project has not evaluated all older versions. Migrate to a supported fixed release.

If all linked servers run 6.0.4 or later, the project’s IRCOp spamfilter is an interim measure while you apply the fix. Use the exact rule in the advisory. On 6.0.2 or later, inspect the loaded module with the local module-status command. IRC operators can also inspect the module list on each linked peer. Look for the vendor’s hot-patch marker or confirm the fixed release.

Response flowRecommended actions: from the perimeter to core systems
  1. 01

    Inventory nodes and limit unnecessary reachability

    Identify the IRC network’s client listeners, server peers, IRC Services connections, loaded modules and exact versions. Include private, managed, containerized and standby instances. Restrict server link and management access to approved systems while preserving legitimate peer traffic.

    See what to doResources: 2

    TWISA member solutions

    Inventory nodes and limit unnecessary reachability

    Exposure management can identify overlooked nodes. Network controls can limit who reaches peer or management listeners. A user can still reach the vulnerable code through an exposed client listener on an affected linked network.

  2. 02

    Apply the vendor fix to each node

    Upgrade to 6.2.7.1 or a supported later fixed release, or deploy the applicable hot patch on every eligible node. Check the loaded labeled-response module on each node. Use the vendor’s interim workaround only where its stated conditions are met.

    View guidanceResources: 1

    Response guidance

    Apply the vendor fix to each node

    Upgrade to 6.2.7.1 or a supported later fixed release, or deploy the applicable hot patch on every eligible node. Check the loaded labeled-response module on each node. Use the vendor’s interim workaround only where its stated conditions are met.

  3. 03

    Preserve records and trace unexpected IRC operations

    Preserve available client, server-link, IRC Services and operator logs before changing rules or restarting where feasible. Correlate unusual KILL, GLINE or other server-authority operations with their timestamps and apparent source. Check for unexplained bans, mass disconnects or peer changes and compare administrative state across nodes.

    See what to doResources: 2

    TWISA member solutions

    Preserve records and trace unexpected IRC operations

    Correlate records across the IRC network to distinguish an approved operator action from an unexpected command. Preserve evidence and establish which peers and services were affected.

  4. 04

    Contain affected nodes and verify recovery

    Review evidence with incident responders. If you find unauthorized changes, isolate affected paths as appropriate, restore trusted operator and network configuration, and validate peer links and moderation before restoring service. Review link and operator credentials and rotate them if the investigation finds exposure.

    See what to doResources: 2

    TWISA member solutions

    Contain affected nodes and verify recovery

    Incident response services can help restore trusted configuration. Privileged access controls support reviewing operator identities and replacing exposed credentials where needed.

Defense architectureSeparate client access, server links and operator administration

Map all IRC listeners, peer links, service connections, module versions and administrative accounts.

Allow authorized traffic and apply controls at each layer.

  1. 01

    IRC client entry

    Public or private client connections

    Limit exposureRemove unnecessary listeners and track anomalies in client traffic.

  2. 02

    Linked IRC servers

    Peer network and labeled-response module

    Patch every nodeVerify the loaded fix and restrict link access to approved peers.

  3. 03

    Operator and service controls

    IRCOp roles, bans, Services and configuration

    Protect privileged changesLimit operator access and baseline changes affecting multiple peers.

Feed logs and traffic data from each layer into monitoring and response.

  1. Correlate records across linked serversCompare privileged command activity, bans, disconnects and link events with authorization records.
  2. Contain and verify recoveryPreserve evidence and validate trusted links, rules and moderation before restoring normal service.

Proactive testing and retesting

With authorization, discover reachable IRC nodes, scan their versions and verify the loaded module. In a controlled environment, use penetration tests or attack simulation to check peer boundaries and ordinary-user permissions. Test management APIs separately where deployed. Where a web console uses a WAF, verify its request, alert, actual blocking and backend result separately from native IRC traffic. Retest client, peer and operator functions after updates. Review host privilege and internal reachability separately.

TWISA member solutions

Official sources

For further product and service details, please contact the relevant TWISA members.

Advisory updated: 2026/11/14. Check the vendor’s latest information for product support and fixes.