On 12 November 2026, Check Point published a security advisory on active exploitation of its Security Gateways. Attackers used a pair of vulnerabilities in the Mobile Access Portal, known as PHP2Shell, to gain initial access. They then used a local privilege escalation in the Gaia operating system to obtain root and establish persistence. The security fixes had been available since 23 October, one week before the attacks. On 13 November, CISA added the underlying Gaia flaw to its Known Exploited Vulnerabilities (KEV) catalog.
On its own, this is a familiar story: a perimeter device, a critical flaw, a patch, and attackers who move faster than some customers. The context is what makes it significant. In the same weeks, CISA restated how its directive on risk-based prioritisation works. ENISA and the UK NCSC described AI as a force that compresses the attack lifecycle. ENISA and CERT-EU published an experiment in which frontier AI models supported security code review. Read together, these publications point to one conclusion.
Patching is no longer an operational chore that IT schedules around maintenance windows. It is a question of decision rights, remediation capacity and evidence. Who may approve an emergency fix on an internet-facing security gateway within hours? Which exposed assets come first when the queue is long? And how does the organisation prove it checked for compromise before it patched? These questions belong to CISOs, CIOs, risk committees and boards in every regulated organisation.
Why the Check Point case matters for security leadership
The Check Point advisory is useful precisely because nothing about it is exotic. The vendor shipped fixes and later folded them into the November Jumbo Hotfix. Check Point Research then observed exploitation in the wild of PHP2Shell, tracked as CVE-2026-109618 and CVE-2026-109619, with a CVSS score of 9.2.
The root flaw sits in Gaia OS DynamicCLI and is tracked as CVE-2026-123039, with a CVSS score of 7.8. According to Check Point, the root-owned dynamic_server process listens on a world-writable local socket without authenticating callers. That is the step that turns initial access into full control of the device.
Check Point says it observed an active exploit “against a couple of dozen customers”. Affected Gaia versions are R81.20, R82, R82.10 and R82.20. Spark Firewalls are not affected by the three new Gaia and Scalable Platform CVEs.
The vendor’s recommendations are clear:
- install the November Jumbo Hotfix;
- start with internet-facing Mobile Access gateways;
- check exposed systems for compromise.
Executive takeaway: The gap that mattered was not between disclosure and fix. It was between fix availability and fix deployment. One week was enough for attackers. That gap is governed by internal decisions, not by the vendor.
Three observations stand out.
First, the affected asset was a security control. Gateways and remote access portals are often treated as protected infrastructure that should change as little as possible. In practice, they are among the most exposed systems an organisation operates. A compromise grants an attacker a privileged position at the network boundary.
Second, the vendor’s own guidance included a sequencing decision: internet-facing Mobile Access gateways first. Sequencing assumes two things. Someone must have an accurate, current inventory of which gateways expose which services. That person must also have the authority to act on that inventory out of cycle.
Third, the guidance did not stop at patching. It asked customers to check exposed systems for compromise. A patch closes the door; it says nothing about who already came through it. Take an organisation that patched a gateway after 23 October without checking for prior access. It cannot state with confidence that the gateway is clean.
Key point: For exposed systems with a known exploited flaw, “patched” and “secure” are two separate claims. Each needs its own evidence.
How CISA has reframed prioritisation
CISA’s Binding Operational Directive 26-04, “Prioritizing Security Updates Based on Risk”, formalises this shift for federal civilian agencies. It requires agencies to set up ongoing remediation of KEV vulnerabilities within timeframes set by CISA. Shorter timelines apply to vulnerabilities newly added to the catalog. It also requires internal validation, enforcement, tracking and reporting. Implementation Guidance accompanies the directive.
On 10 November, CISA added six vulnerabilities to the KEV catalog, affecting Cisco BroadWorks, two Barracuda products, Openwave, Outlook and Chromium. In the same alert, CISA restated how the directive works in practice:
- it gives priority to KEV CVEs on publicly exposed assets that grant total control after exploitation;
- it sets basic expectations for checking whether threat actors compromised a system before the patch was applied.
CISA states that the directive binds only federal civilian agencies. It nevertheless encourages all organisations to adopt risk-based vulnerability management.
The Check Point flaw closely matches the directive’s top priority: a KEV-listed vulnerability, on publicly exposed assets, leading to root access. Two alerts in a single week added eight entries to the catalog. Organisations outside US federal scope can still use this logic as a defensible prioritisation model.
Security implication: A severity score alone no longer tells you what to fix first. Exposure, confirmed exploitation and post-exploitation impact do. A prioritisation model built only on severity scores will put the wrong items at the top of the queue.
Why AI raises the stakes on speed and volume
The pressure on remediation is not only about individual incidents. European and UK authorities describe a structural change in the pace of attack and defence.
ENISA set out its view in a July 2026 position paper on cybersecurity in the frontier AI era. It states that AI models are compressing the whole attack lifecycle, from reconnaissance to lateral movement. It tells organisations to treat this as a structural shift in the pace of attack and defence. ENISA also notes that defensive teams now face a challenge of scale, including how to audit and validate AI-generated patches.
The NCSC published its annual review on 3 November 2026. It warned that UK critical national infrastructure should be braced for a ransomware attack involving AI-powered malware by 2028. The NCSC said that “tech on the cheap” has left organisations exposed to AI uncovering and exploiting longstanding weaknesses. It called for urgent investment in resilience. The UK government announced three measures:
- £60 million for the first phase of a national Cyber Shield;
- £70 million for a National Exposure and Real-Time Vulnerability (NERV) Centre;
- an AI Cyber Security Centre of Excellence in Manchester, run by the NCSC.
Defence is also using AI to find flaws. On 12 November 2026, ENISA and CERT-EU published a joint advisory on using frontier AI models for security code review. The models supported review of open-source software maintained by EU institutions, bodies, offices and agencies. CERT-EU provided its Vigilo harness; ENISA developed the Code Auditor and Findings Browser Report skills.
The governance consequence follows from both sides. Attackers find and exploit weaknesses faster. Defenders use AI to discover more weaknesses in their own code. The bottleneck therefore shifts to the human steps in between: triage, validation, approval, deployment and verification.
Decision point: Management must decide what remediation capacity should be sized for. One option is yesterday’s discovery rate. The other is the volume that AI-assisted discovery, on both sides, will generate.
The governance weakness behind slow patching
In most organisations, the technical ability to apply a hotfix exists. What is often missing is the organisational path to do it quickly and safely on a critical asset.
Change processes are designed for stability. They require approvals, test windows and rollback plans. For an internet-facing gateway with a KEV-listed flaw, these steps can turn a one-week window into a much longer exposure. Change control itself is not the problem. The problem is that most organisations have not defined a separate, pre-authorised path for exploited vulnerabilities on exposed assets.
Three gaps recur:
- Unclear decision rights. Nobody has explicit authority to approve an emergency fix on a production security control outside the change calendar, so the decision escalates and waits.
- Incomplete exposure data. Asset inventories do not reliably show which systems are internet-facing and which services they expose, so prioritisation by exposure is guesswork.
- No compromise-check standard. Teams patch, close the ticket and move on. There is no defined procedure, and no evidence, that the system was checked for signs of prior access.
Each of these is a governance gap, not a tooling gap. Each can be closed by a decision from management.
Business, regulatory and board implications
For regulated organisations in finance, energy, health, industry and the public sector, the remediation gap is a matter of accountability. The question is not only whether a vulnerability was fixed. It is also when the organisation knew, who decided, and what evidence supports the claim that the risk was contained.
A compromised security gateway affects more than one system. It can expose three things:
- remote access for staff and suppliers;
- internal network segments;
- the credentials that pass through the device.
In operationally critical sectors, that becomes a continuity issue. For organisations providing services to others, it becomes a customer trust and supply chain issue.
Boards should be able to answer a short set of questions:
- How long, on average, does it take to deploy a fix for a known exploited vulnerability on an internet-facing asset?
- Who can approve that deployment out of cycle, and is that authority written down?
- What share of exposed assets is covered by an accurate inventory?
- What evidence is kept that exposed systems were checked for compromise?
- Is remediation capacity sized for a rising volume of findings?
What security leaders should prioritize
-
Define an emergency remediation path. The CIO and CISO should document a pre-approved procedure for KEV-listed or vendor-confirmed exploited flaws on exposed assets. It should name an approver and set a target deployment time in hours or days, not change cycles.
-
Adopt exposure-first prioritisation. The vulnerability management owner should rank remediation by exposure, confirmed exploitation and post-exploitation impact before severity scores. CISA’s logic for BOD 26-04 can serve as the reference model.
-
Maintain an inventory of internet-facing assets. The infrastructure lead should keep a current list of exposed systems and services, starting with gateways, VPNs and remote access portals. That way, sequencing guidance such as “internet-facing Mobile Access gateways first” can be applied immediately.
-
Make compromise checks a mandatory step. Any exposed system patched for an exploited flaw needs a documented check for indicators of prior access. The security operations lead should require that check and keep the result as evidence.
-
Monitor vendor advisories and the KEV catalog as triggers. A new KEV entry, or a vendor exploitation advisory for a product in the estate, should automatically open a tracked, time-bound action with an owner. The CISO should make sure this trigger is in place.
-
Size triage capacity for AI-era volumes. The CISO and finance should check whether teams can validate and deploy fixes at the rate AI-assisted discovery will produce. They should then fund capacity, automation or prioritisation rules accordingly.
-
Report remediation time to the board. The risk committee should receive time-to-remediate for exploited flaws on exposed assets as a standing indicator. Residual risk should be reported alongside it wherever fixes are delayed.
From hygiene to accountability
The Check Point case will be followed by others. The pattern is stable: a fix exists, attackers exploit the gap before deployment, and organisations that cannot act quickly carry the consequences. What is changing is the tempo. Authorities on both sides of the Channel expect AI to shorten the time attackers need and to increase the volume of flaws defenders must handle.
In that environment, a patch management tool matters less than three decisions made in advance: who can act, what comes first, and what proof is required. Never Trust, Always Verify applies here as well: a patched system is not trusted until it has been checked.
Practical takeaway: Treat emergency patching of exposed assets as a governed decision. It needs a named owner, a pre-approved fast path, an exposure-first priority order and a mandatory compromise check. Before the next KEV alert, ask management to confirm that each of these exists in writing and that remediation time is reported to the board.