Daily · Article 01 · 2 min read
- Security
Check Point confirms gateway attacks. Patching and investigation answer different questions
Vendor report dated November 12 · CISA exploited-vulnerability listing checked November 14 JST
Summary
Check Point observed attacks against remote-access gateways. Here is what proves a fix is running and what helps establish whether a device was already compromised.
Key facts
Check Point, a maker of business firewalls, reported on November 12 that it had found intrusions affecting some unpatched remote-access gateways. The company observed activity from October 30 through November 4. The incidents involved a PHP flaw in a feature that accepts outside connections, then a separate flaw that raised privileges inside the device (CVE-2026-123039). CISA, the US cybersecurity agency, added that second issue to its catalog of vulnerabilities exploited in the wild. Vendor report · Canadian Cyber Centre

1. What happens when the device taking connections is compromised?
When an employee works from home, the company’s remote-access gateway receives the connection before the employee reaches internal documents. Handling a connection and administering the gateway normally require different permissions. In the reported incidents, the gateway was breached first and a separate flaw allowed access with administrative privileges. Those privileges can allow changes to settings or logs, so a service that still accepts connections tells the team little about whether the device was compromised.
| Question | What the report establishes |
|---|---|
| Where were attacks observed? | Internet-facing, unpatched Check Point remote-access gateways |
| What changed after entry? | The reported cases included access with elevated device privileges |
| What about our own device? | Installation and incident records must be checked for each device |
- Question
Where were attacks observed?
- What the report establishes
- Internet-facing, unpatched Check Point remote-access gateways
- Question
What changed after entry?
- What the report establishes
- The reported cases included access with elevated device privileges
- Question
What about our own device?
- What the report establishes
- Installation and incident records must be checked for each device
The cat asks Q&A
- The researcher
If employees can still connect, is the device all right?
Pocket NotebookA successful connection shows that the service is responding. Ask the operations team whether it separately reviewed administrative activity and the device’s logs.
2. Release, installation and investigation
Check Point says an initial fix for PHP2Shell was available on October 23 and now recommends the November Jumbo Hotfix, a bundle of fixes, for management servers and security gateways. Check Point lists R81.20, R82, R82.10 and R82.20 for CVE-2026-123039 in its Gaia operating system. Verify the applicable package for your product and release. Vendor guidance
| Stage and owner | What is verified | What to ask for |
|---|---|---|
| Check Point · supplies fixes | The vendor recommends the November bundle | Guidance for the product and release |
| Operations · applies the fixes | Verify separately on each device | Application time and the update currently running |
| Security team · investigates prior compromise | Requires a separate review per device | Findings from administrative activity and logs before and after the update |
- Stage and owner
Check Point · supplies fixes
- What is verified
- The vendor recommends the November bundle
- What to ask for
- Guidance for the product and release
- Stage and owner
Operations · applies the fixes
- What is verified
- Verify separately on each device
- What to ask for
- Application time and the update currently running
- Stage and owner
Security team · investigates prior compromise
- What is verified
- Requires a separate review per device
- What to ask for
- Findings from administrative activity and logs before and after the update
The cat asks Q&A
- The researcher
If we update today, can we tell what happened last week?
Pocket NotebookUpdating reduces exposure going forward. Use earlier records to investigate previous exposure, and ask the security team or provider how far its review could go if logs are missing.
To close
Two questions for the operations team
Suppose two branches each have a gateway. Ask which fixed build is running on each device, then request the results of the separate investigation into any time it was exposed before the update.
Sources
- Check Point’s incident reportblog.checkpoint.com
- Canadian Centre for Cyber Security alertcyber.gc.ca
- CISA exploited-vulnerability catalogcisa.gov