CISA added two actively exploited flaws to its Known Exploited Vulnerabilities (KEV) catalog on 13 November: a command-injection bug in the UnrealIRCd chat server and a root-level local escalation in Check Point’s Gaia operating system, which underpins the company’s firewalls and management servers. Both entries carry a federal due date of 16 November, three days after listing, and both are flagged for forensic triage, meaning federal agencies are expected to look for signs of compromise rather than simply patch and move on.
The pairing is odd at first glance. One is an open-source IRC server; the other sits inside enterprise security gateways. What they share is that a foothold of fairly modest privilege turns into full authority over the system or network involved.
Two bugs, two different routes to full control
UnrealIRCd, CVE-2026-114713 (CVSS 8.6, High). According to the CVE record, UnrealIRCd’s labeled-response module echoes the IRCv3 “label” message tag back into its replies without escaping it. On a network where two or more servers are linked, any connected user can therefore smuggle text that the peer server reads as server-to-server traffic, and those injected commands run with the authority of a server rather than an ordinary user. The record classes it as CWE-140, a failure to neutralise delimiters. No login or user interaction is needed, and the scope is marked as changed because the impact lands on other servers in the network, not just the one the attacker talks to. Releases from 6.0.0 up to but not including 6.2.7.1 are affected; 6.2.7.1 is the fixed build.
Check Point Gaia, CVE-2026-123039 (CVSS 7.8, High). Gaia includes a DynamicCLI service that runs as root. The CVE record explains that it accepts instructions over a local socket that every user on the box can write to, and it never checks who is connecting. Anyone holding a low-privilege local account can hand it a command and have that command executed as root. The record maps this to CWE-862 (missing authorisation) and CWE-732 (incorrect permissions on a critical resource). The CVE record names Quantum Security Gateway and Quantum Security Management as affected, and the KEV listing names a wider set: Check Point Firewall, Security Gateway, Security Management Server, Multi-Domain Security Management Server and Scalable Platforms.
The affected Gaia builds, per the CVE record:
| Gaia release | Affected when running |
|---|---|
| R82.20 | Jumbo Hotfix Take 10 or earlier |
| R82.10 | Jumbo Hotfix Take 50 or earlier |
| R82 | Jumbo Hotfix Take 130 or earlier |
| R81.20 | Jumbo Hotfix Take 173 or earlier |
Check Point’s remediation details are in its support article sk1000362, which the KEV entry cites as the vendor reference.
What has been confirmed, and what has not
- Exploitation. CISA listed both flaws on evidence of active exploitation. Its SSVC assessments in each CVE record agree: exploitation active and technical impact total for both.
- Automation differs. CISA’s SSVC assessment marks the UnrealIRCd bug as automatable and the Check Point flaw as not automatable, which fits a local bug that needs an existing account first.
- Deadline. Federal civilian agencies must remediate both by 16 November under Binding Operational Directive 26-04. Under BOD 26-04, CISA sets KEV due dates from its Vulnerability Response Timeline using available risk data, and both entries carry a “total” technical-impact rating.
- Compromise checks. Both KEV entries are marked for forensic triage, so agencies are expected to establish whether a system was breached before the fix went on, not just to apply it.
- Ransomware. CISA lists ransomware use as unknown for both.
The sources do not say who is exploiting either flaw, how many systems are affected, or which sectors or regions have been hit. No threat group has been attributed. For Check Point in particular, the open question is how attackers are getting the initial local account; the root escalation is presumably one link in a longer chain, but nothing published so far describes that chain.
Where to start
- Check Point owners first. A root shell on a perimeter firewall or the management server that pushes its policy is a far bigger prize than an IRC network. Identify every Gaia appliance and management server, compare its Jumbo Hotfix take against the table above, and apply the remediation Check Point gives in sk1000362.
- Review who has local access. Because the bug needs an existing account, audit local and expert-mode users on each gateway and management server, remove stale accounts, and confirm administrative access is limited to known hosts.
- Look for a breach before trusting the patch. Preserve logs and, where practical, volatile state on any exposed Gaia system before upgrading, then look for unexpected root-owned processes, new accounts and policy or configuration changes nobody made.
- Upgrade UnrealIRCd to 6.2.7.1. Operators of linked networks should bring every server to the fixed build. The CVE record also lists a hot-patch that applies without a restart, and an interim workaround of disabling the labeled-response module on all servers until the upgrade is in place.
- Audit IRC network state. After upgrading, review server links, operator privileges, bans and services changes for anything that could have been forced through as server traffic.
Organisations outside the US federal government are not bound by the 16 November date, though CISA’s alert urges all organisations to prioritise KEV-listed flaws, and the evidence of exploitation applies to any operator. Both CVEs can be looked up alongside other KEV-listed flaws in the CVE search.
Frequently Asked Questions
Is Check Point CVE-2026-123039 being exploited? Yes. CISA added it to the KEV catalog on 13 November 2026 based on evidence of active exploitation and set a federal remediation date of 16 November.
Which Check Point Gaia versions are affected by the DynamicCLI flaw? The CVE record lists R81.20, R82, R82.10 and R82.20 when running Jumbo Hotfix takes at or below 173, 130, 50 and 10 respectively. Check Point’s sk1000362 carries the remediation details.
What does the UnrealIRCd labeled-response vulnerability allow? It lets an ordinary user on a multi-server UnrealIRCd network pass commands to linked servers, which then treat them as if a fellow server had sent them. Versions 6.0.0 to before 6.2.7.1 are affected, and 6.2.7.1 fixes it.
Do non-federal organisations have to meet the 16 November deadline? No. The deadline binds only US federal civilian agencies, but CISA encourages every organisation to prioritise KEV-listed flaws, and both are confirmed as exploited.
Source: Cybersecurity and Infrastructure Security Agency (CISA)