Vulnerabilities
Check Point Root Flaw and UnrealIRCd Injection Join the KEV Catalog With a November 16 Deadline
One flaw hands root on a firewall to any local user. The other lets any chat user speak with server authority. CISA gave both the shortest clock it uses.
Photo: DHSgov, Public domain, via Wikimedia Commons
CISA added two more vulnerabilities to the Known Exploited Vulnerabilities Catalog on November 13, 2026, and gave federal agencies three days, until November 16, to remediate both, with forensic triage required on each entry. The pair could hardly be less alike: a local privilege escalation in Check Point’s Gaia operating system that turns any authenticated local user into root, and a command injection in UnrealIRCd, the long running IRC server, that lets an ordinary chat user issue commands with server authority on linked networks. The catalog version published that day, 2026.11.13, carried 1,781 entries.
The Check Point flaw: a root daemon behind an open socket
CVE-2026-123039 is an incorrect permission assignment for a critical resource, scored 7.8. According to CISA’s catalog entry, a background service for the Gaia OS DynamicCLI feature holds root privileges and accepts connections over a local socket that any local account can write to, with no check on who is connecting. Any user already logged in to the box can feed the socket a command and watch it run as root. Check Point lists the exposed products as its firewalls, security gateways and management servers, the multi-domain management server, and its scalable platforms.
A local flaw on a security gateway deserves more respect than the word local suggests. Gateways are exactly where an attacker who has already landed somewhere inside a network wants a second foothold, and root on the firewall is control over the traffic the firewall exists to inspect. Reporting by BleepingComputer and Security Affairs, published the same day as the listing, describes intrusions that started at unpatched gateways and, in the worst cases, finished with a wiper turned loose on the victim’s VMware ESXi hosts. Those campaign details are the outlets’ reporting, not CISA’s: the catalog entry itself confirms exploitation but names no actor and no victims.
Check Point’s advisory, sk1000362, lists the fixed builds: the Jumbo Hotfix Accumulator for R82.20 from Take 14, R82.10 from Take 52, R82 from Take 132 and R81.20 from Take 174. Because forensic triage is flagged, installing the hotfix is only half the job: gateway administrators should review local accounts and command history for activity that predates the patch.
Photo: DHSgov, Public domain, via Wikimedia Commons
The UnrealIRCd flaw: a user who can speak as a server
CVE-2026-114713 is an improper neutralization of delimiters flaw, scored 8.6. On an IRC network with two or more linked servers, any ordinary user can inject server to server commands that then execute with the authority of a server. Server to server traffic is trusted by design in IRC linking, which is what makes the injection serious: commands that should only ever arrive from a peer server can be smuggled in from a normal user connection. CISA’s entry covers UnrealIRCd versions 6.0.0 through 6.2.7 and the 5.x series. The fix is version 6.2.7.1, or the hot patch the project published for operators who cannot upgrade immediately.
Why the three-day clock
Under Binding Operational Directive 26-04, CISA’s risk based patching directive, the shortest deadlines land on flaws that combine confirmed exploitation with a path to total control of the asset. A root escalation on perimeter gateways and a server authority injection on linked chat networks both fit that pattern, and both entries carry the forensic triage flag, which means agencies are expected to check whether the flaw was used before the patch went on, not simply to patch. CISA records ransomware campaign use as unknown for both entries. For private operators the federal deadline does not bind, but the reasoning does: if you run Check Point gateways or an UnrealIRCd network, these two fixes belong ahead of routine patching this week.
No corrections have been published for this article.