CISA has added CVE-2026-114713 to its Known Exploited Vulnerabilities catalog. The flaw lets an ordinary user on an affected, linked UnrealIRCd network issue commands with server authority. Operators should repair every server and review evidence of unauthorized administrative activity.
The fix predates the listing. Maintainer Bram Matthys released UnrealIRCd 6.2.7.1 and a hot-patch on November 7. His November 8 advisory on oss-security reproduces the release instructions. CISA added the vulnerability on November 13, with a November 16 due date. Those are catalog and remediation dates, not the date attacks began.
A user-supplied label crossed the server boundary
UnrealIRCd runs IRC chat networks. Its labeled-response module, which associates replies with client requests, failed to escape a user-supplied message label. On a network with two or more linked servers, that input could become additional server-to-server commands.
The CVE record describes affected UnrealIRCd 6 releases from 6.0.0 through 6.2.7. The maintainer separately confirms that the unsupported 5.x series is similarly affected. Older end-of-life branches were not fully checked.
This is authority inside the IRC network, including disconnecting users and imposing network-wide bans. The reviewed sources do not establish operating-system shell access through this flaw. The release also fixes separate crashes, hangs and weaknesses that could reveal users’ IP addresses.
Evidence status: CISA-listed exploitation in the wild. The catalog identifies no victims, attack count or first-exploitation date. It marks ransomware use unknown. The original internal audit and the later evidence of real exploitation are separate developments.
Verify the running repair across the network
The maintainer offers two repair paths:
- Upgrade to 6.2.7.1 or later and restart. Windows operators, and anyone whose hot-patch fails, should use the upgrade path.
- Apply the official
bundle-20261107hot-patch on every eligible server. The advisory supports this on Unix-like systems running 6.0.0 through 6.2.7. A successful download alone does not establish that the running server loaded it.
Check the loaded labeled-response module against the advisory’s verification instructions. Its documented hot-patched marker is 5.0-hot-patch-bundle-20261107. A bare 5.0 means that repair was not applied. The module marker differs from the daemon’s release number, so an unchanged version string alone can be misleading.
The advisory also supplies an immediate network filter, with an important condition: every linked server must run 6.0.4 or newer. That filter addresses the critical flaw, while leaving the release’s other fixes outstanding. Follow the maintainer’s exact instructions rather than treating a filter as a completed upgrade.
For end-of-life 5.x, the maintainer’s temporary workaround disables labeled-response on all servers and requires restarting, not merely rehashing the configuration. Plan migration to a supported release.
Patching does not establish a clean history
CISA marks forensic triage as required under its applicable federal guidance. Its catalog deadline should not be presented as a universal legal deadline for all operators.
For an exposed network, preserve available logs and review unexpected bans, disconnections and administrative changes alongside patching. The sources provide no universal detection rule or assurance that a quiet log proves safety. Investigate suspicious activity according to the access and changes actually observed.
Caveat: CISA confirms the exploitation signal but publishes little incident detail. Its listing cannot establish whether a particular network was compromised.