CVE-2026-114713
Unrealircd ≤ 6.2.7.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-114713 is a high-severity Improper Neutralization of Delimiters (CWE-140) vulnerability in Unrealircd. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Create Account (T1136); ranked at the 41th percentile by exploit likelihood (below the median); CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Advisories
- CISA KEV: PHP2Shell Exploited in Destructive Check Point Gateway Attacks (Nov 13)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-119377
Vulnerability Data
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…
more
executed with server authority.
- CWE(s)
- KEV Date Added
- 13 November 2026
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Developer testing and evaluation can discover missing or incorrect delimiter neutralization through targeted test cases.
Secure engineering principles include explicit requirements for proper delimiter handling and sanitization.
Input validation directly enforces neutralization of delimiters before they reach parsers or interpreters.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require proper delimiter neutralization during input handling and output encoding.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing in development and acceptance can detect delimiter-related weaknesses before deployment.
Training developers about input handling and delimiter neutralization reduces a minority of instances, but the defect is a specific implementation detail that requires careful coding; training is fallible and the stronger controls (secure coding, code review, testing) carry most of the load, mirroring A.8.28 vs CWE-79 and A.6.3 vs CWE-598.
Secure coding explicitly requires proper neutralization of delimiters to prevent injection and parsing flaws.
A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary input-neutralization weaknesses in delivered code the way those practices do; the clause's ceiling on this verb is `partial` and the remainder is the fallibility of the mandated practice.
A.8.8's reach is DISCLOSURE — it finds delimiter-neutralization flaws only where they have been published as advisories in third-party components, and most CWE-140 instances live in first-party code that no advisory names, mirroring the A.8.8 -> CWE-89 anchor at the same rung.