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…
Affects UnrealIRCd 6.0.0 before 6.2.7.1 when the labeled-response module is loaded. Fixed in 6.2.7.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.2.7.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.2.7.1.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.29% · 21st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The labeled-response module in UnrealIRCd 6.0.0 (before the 6.2.7.1 fix) fails to escape the IRCv3 "label" message tag, so any user on a network with two or more linked servers can, remotely and without logging in, inject server-to-server commands that run with server authority. Because the bug requires a network with at least two linked servers, it is not limited to a single standalone server.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.2.7.1.
Workaround: Add blacklist-module "labeled-response"; to the configuration file of all servers until the patch or upgrade is applied.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- UnrealIRCd UnrealIRCd
fixed in 6.2.7.1
Evidence 4
- Link
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-114713
Is CVE-2026-114713 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The labeled-response module does not escape the IRCv3 "label" message tag when it echoes the tag into replies, so a user can inject newlines. The advisory says an ordinary user can then execute commands with server or IRCOp authority, such as KILL and GLINE.Source: cve.org, openwall.com
Which versions are affected by CVE-2026-114713?
UnrealIRCd: before 6.2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
UnrealIRCd 6.0.0 before 6.2.7.1 is affected when the labeled-response module is loaded. To check, look at the installed version and at the configuration file for a blacklist-module "labeled-response"; line, which disables the module.Source: cve.org, openwall.com
How do I fix CVE-2026-114713?
Upgrade to UnrealIRCd 6.2.7.1 or later.Source: cve.org, openwall.com