CVE-2026-114713: UnrealIRCd Flaw Now Exploited

UnrealIRCd CVE-2026-114713 is in CISA's exploited list with a 16 November 2026 deadline. Patch, verify the running build, watch your logs.

Maysan Engineering Team · · 6 min read

Xin

On 13 November 2026, CISA added CVE-2026-114713 to its Known Exploited Vulnerabilities catalog: an improper neutralization of delimiters flaw in UnrealIRCd, the open-source IRC daemon that still carries internal chat and alerting traffic for plenty of teams. Per CISA's short description, any user on a network with two or more linked servers can inject server-to-server commands that are executed with server authority. The fix is not a config toggle — it is the vendor's mitigation, applied by 16 November 2026, or discontinuing the product. If UnrealIRCd exists anywhere in your stack, today is the day you find out which instances exist and which of them are linked to another server.

What the CVE-2026-114713 entry actually says

The entry is short, and every line of it matters. CISA catalogued it on 2026-11-13 under catalog version 2026.11.13, which tells you this was an emergency addition rather than a routine monthly sweep. What the record lists:

  • Vulnerability: UnrealIRCd Improper Neutralization of Delimiters.
  • Impact: any user on a network with two or more linked servers can inject server-to-server commands that are executed with server authority.
  • Known ransomware campaign use: unknown.
  • Required action: apply mitigations in accordance with vendor instructions, or discontinue use if mitigations are unavailable.
  • Due date: 2026-11-16.

Note what is absent. The entry does not name an affected version range, does not identify the exact delimiter involved, and does not say how the flaw was found. For version and patch detail you have to go to the vendor's own advisory.

Am I affected? The two-linked-servers test

The condition CISA states is narrow and specific: a network with two or more linked servers. So the first job is inventory, not patching. Walk your estate and list every UnrealIRCd process — production, staging, the testnet someone stood up for a migration and never tore down, the instance a team uses for build alerts, anything baked into a container image you inherited. Then ask, for each one, whether it links to another server. A leaf that connects to a hub is still a link, and the hub that accepts links is the more exposed end. A single, standalone instance falls outside the description CISA gives, which is not the same as "safe" — it means the stated attack path does not apply to it. If you cannot answer the linking question quickly, that itself is the finding.

The exact patch action for the next 24 hours

Upgrade to the fixed build named in UnrealIRCd's own advisory and restart — do not sit on it for a maintenance window, because the KEV due date is 2026-11-16. The KEV entry does not name a version, so the version string has to come from the vendor, never from a summary post. In order:

  • Pull the advisory from the project's official channels and note the build it names as fixed.
  • Rebuild containers from a fresh base rather than patching a running layer; cached layers are where stale binaries hide.
  • Restart the daemon and check the process start time, not just the package manager's record.
  • If you cannot patch by the deadline, CISA's instruction is to apply the vendor's mitigations or discontinue use, and the cloud services path in BOD 26-04 covers hosted instances.

Then verify what is actually serving traffic: ask the running process for its version and compare it against the fixed build from the advisory. A patched binary on disk with an old process still bound to the port is the quiet failure mode here. Confirm the unit file or container entrypoint points at the binary you replaced, and that the server re-linked to its peers with the configuration you expect.

What to watch in the logs afterwards

Assume the vulnerable window was open and look for what a server-to-server command injection would leave behind. CISA's entry does not describe how exploitation manifests in this case, so watch the categories that matter for the class: server links you did not create or approve, operator privileges nobody granted, configuration changes nobody scheduled, and restarts you cannot attribute to a deploy. Compare the current link set against a known-good baseline if one exists. Preserve logs before rotation — the required action references CISA's Forensics Triage Requirements, and "we rotated them" is not a defensible answer if the instance turns out to have been internet-facing.

What AI changes about finding delimiter bugs

Delimiter bugs are a parser-trust problem: a protocol that separates fields with spaces and colons will mis-parse input if the code assembling a line treats user data as trusted. AI-assisted review is genuinely useful here because the pattern is repetitive and greppable — untrusted strings concatenated into a protocol line, missing escapes, hand-rolled parsers that quietly disagree with the spec. Modern assistants flag those shapes across a large codebase faster than a human skimming a diff, and cheaply enough to run on every change rather than once a quarter. What they will not do is tell you whether a given flag is a real positive; that still needs someone who knows the protocol. CISA's entry does not say how this bug was found, so treat AI review as one more net, not the answer.

Who BOD 26-04 binds, and why Indian teams should care

BOD 26-04 is CISA's risk-based patching directive for US federal civilian agencies, but it reaches further than that. If you build or host software for a US federal customer, or subcontract to a prime that does, the same expectations usually arrive in your contract as flow-down requirements — and a three-day KEV deadline becomes your delivery schedule whether or not the directive names you. For Indian SMBs and mid-market firms the practical move is to keep KEV tracking on a standing watch: a weekly check of the catalog, a named owner for every internet-facing asset, and a written list of what you would switch off if a patch is not available. That last item is the one most teams skip, and it is exactly what CISA's "discontinue use" instruction demands.

Where to start

If UnrealIRCd is somewhere in your stack and you are not certain how it links, start with the inventory today — you have until 2026-11-16 to know. Pull the vendor advisory, patch to the build it names, verify the running daemon's version string on every host, and keep the logs. Teams running this on hosted infra usually find the asset tracking and patching discipline is the harder half of the job. If you would rather have someone walk the estate with you, our server and infrastructure work covers exactly this kind of audit-and-remediate sprint — that is what Maysan Labs does for teams who would prefer not to discover a forgotten linked server during an incident.

Buying software or a website?

Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.

Get the free checklist

Written by Maysan Engineering Team at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn