CVERadar
HIGH · CVSS 3.1 8.6CISA KEV · added 2026-11-13Public PoCEPSS 0.51% (p44)Threat level 58

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

UnrealIRCd · UnrealIRCd · NVD published 2026-11-08 · posted 2026-11-13 · last modified 2026-11-14

CVE-2026-114713 at a glance

CVE-2026-114713 is a high-severity vulnerability in UnrealIRCd, with a CVSS 3.1 base score of 8.6. NVD published it on 2026-11-08 and classifies the weakness as CWE-140. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-13; the federal remediation due date is 2026-11-16. Public exploit code: 3 public GitHub proof-of-concept repositories from 3 accounts, with the earliest exploit evidence dated 2026-11-13. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.51% (percentile 43.8, scored 2026-11-14). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 58/100.

What it is

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.

WeaknessCWE-140 definition
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N (source: MITRE)
CISA due date2026-11-16 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsn/a

CVERadar report: CVE-2026-114713: UnrealIRCd flaw exploited in the wild, what we know

What this means for a small business

CISA added CVE-2026-114713 to its Known Exploited Vulnerabilities catalog on 2026-11-13. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs UnrealIRCd, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-16 to deal with it, and that is a sensible deadline for a small business too.

  • Patch. Install the latest update from UnrealIRCd. NVD does not list a fixed version, so the vendor advisory linked on this page is the reference for which release closes it.
  • If you cannot patch yet. Follow CISA's required action: 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.
  • Check your exposure. Find out whether UnrealIRCd can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
  • When to call IT support. Call your IT support provider now if you run UnrealIRCd and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

Built from the CISA KEV entry and the NVD record for CVE-2026-114713; nothing here goes beyond those sources.

Exploitation evidence

First exploit evidence seen: 2026-11-13 (earliest date across the sources below).

Exploited in the wild

Public exploit code

GitHub proof-of-concept repositories

3 public repositories from 3 accounts, first seen 2026-11-14. Most starred: foxcornlab/unrealircd-scanner (0 stars), view the foxcornlab/unrealircd-scanner repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

No ATT&CK techniques could be mapped or inferred for this CVE yet.

Patches, mitigations and detection

CISA required action

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. (source: CISA KEV)

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources