ZeroDayAlert

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

UnrealIRCd UnrealIRCd contains an improper neutralization of delimiters vulnerability that allows any user on a network with two or more linked servers to inject server-to-server commands that are executed with server authority.

UnrealIRCd UnrealIRCd Added to KEV 2026-11-13 Federal due 2026-11-16 Known ransomware use

Required action — quoted from CISA

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Where this comes from. The identifier, product, dates and required action above are copied verbatim from the CISA Known Exploited Vulnerabilities catalog. The action plan below is written by an AI agent from that record and published automatically. AssurePort has not independently tested this vulnerability and makes no claim about whether any specific system is affected.

Who is affected

UnrealIRCd, an IRC (Internet Relay Chat) server daemon, is affected by an improper neutralisation of delimiters flaw. The vulnerability allows any user connected to a network comprising two or more linked UnrealIRCd servers to inject commands that execute with server authority. The record does not specify which versions of UnrealIRCd are affected, nor does it indicate whether this affects IRC networks with specific architectural configurations beyond the requirement for multiple linked servers.

How to check whether this touches you

  • Inventory your IRC infrastructure: do you operate or depend upon UnrealIRCd servers, and if so, are they part of a network with two or more linked instances?
  • Check network topology: confirm whether your UnrealIRCd deployment is standalone or federated with other servers; the vulnerability requires at least two linked servers to be exploitable.
  • Query running processes and service configurations to establish which UnrealIRCd version is deployed; consult your package manager or service logs for version strings, bearing in mind that version numbers alone do not confirm whether a backported fix has been applied.
  • If you operate a public or semi-public IRC network, establish whether external users can connect and authenticate; networks isolated to internal or trusted users face lower reachability risk.

What to do

  1. Contact UnrealIRCd vendor support or monitor their security advisories immediately to identify whether a patch or mitigation guidance has been released; do not assume a fix is available simply because the CVE is public.
  2. If you cannot patch immediately and your network is internet-facing, restrict server-to-server link acceptance to trusted peer addresses using firewall rules or IRC daemon configuration; document the temporary exception.
  3. Enable and retain detailed server-to-server communication logs (inter-server protocol traffic) at INFO level or above for at least 90 days; ensure log aggregation captures timestamps and source addresses for any injected commands.
  4. If your network is business-critical, prepare a rollback plan and test it in a staging environment before applying any vendor patch.
  5. If the vendor provides no remediation within your patching window, escalate to your change advisory board and risk committee; CISA guidance permits discontinuation of the product if mitigations remain unavailable.

If you find you were exposed

Exploitation of this flaw likely predates public disclosure, so you should assume any linked UnrealIRCd network visible to untrusted users may have been compromised. Query server logs for anomalous inter-server commands, particularly those containing unusual syntax or delimiter sequences, going back as far as your log retention allows. Cross-check IRC operator audit trails and user authentication logs for unauthorised privilege escalation or access patterns that coincide with suspicious server-to-server activity. If you detect evidence of exploitation, treat it as a full IRC network compromise and initiate incident response procedures, including credential rotation for all operators and service accounts.

Get these the morning they land.

One email, only when a vulnerability is newly confirmed as exploited — the CISA record plus our action plan. No more than one a day, and nothing on quiet days.

Knowing it exists is not the same as knowing you are exposed.

This page can tell you that CVE-2026-114713 is being exploited. It cannot tell you whether UnrealIRCd is running somewhere of yours that is reachable. That question is what a scan answers.

Check your own surface →