The 13 November batch splits two ways. The urgent half is a single bug under active exploitation: a local privilege escalation in Check Point’s Gaia OS that CISA added to its exploited list on 13 November with a federal due date of 16 November 1 2 3. The other half is 36 CVEs from the 12 November NVD wave, all marked unknown for exploitation, most of them routine vendor output.
The Check Point bug comes with a deadline
CVE-2026-123039 scores 7.8 1, and the affected set reaches past Quantum. Check Point’s advisory lists Check Point Firewall, Security Gateway, Security Management Server, Multi-Domain Security Management Server and Scalable Platforms 2, and NVD files the same build rows under Quantum Security Gateway and Quantum Security Management 1. The affected builds run from R81.20 up to Jumbo Hotfix Take 173, with R82 up to Take 130, R82.10 up to Take 50 and R82.20 up to Take 10 1. Check Point also lists R81 and R81.10, both end of support, and its fix ships for the four builds that carry a take level, so those two take the mitigation only 2. The DynamicCLI daemon, dynamic_server, runs as root and listens on /tmp/dynamic_socket. It creates that socket world-writable, does not authenticate the process on the other end, and runs whatever command string arrives as root 2. An attacker who gets a local shell on the appliance writes one request to a file and has root.
Check Point Research dates the observed exploitation from 30 October to 4 November and says the incidents compromised a couple of dozen unpatched systems in a single region 4. The CISA entry requires forensic triage under BOD 26-04, so the response goes past patching 3.
I would run two checks before a maintenance window. ls -l /tmp/dynamic_socket should show srw-rw---- root config, not 0777. After the fix, the daemon writes blocked calls to /var/log/dynamicCli.log as Rejected connection from unauthorized uid, so an odd UID there marks an attempt. If the 16 November date does not fit your window, Check Point’s interim step is to stop dynamic_server with dbset, which stops the dependent Dynamic CLI commands.
I walk through the full chain in a separate post at https://calebgarber.com/posts/check-points-cve-2026-123039-carries-a-kev-due-date/, from the socket mode to the two response checks and the dbset mitigation.
I rank this above its 7.8. A local shell is a modest ask on a general-purpose server. On a firewall it is most of the way to control, because root owns the policy, the routing table and the logs, and here the distance from an authenticated local account to root is one write to a world-writable socket.
Two ManageEngine roles that end in a server shell
CVE-2026-12507 is authenticated remote code execution in the Reports module, 9.1, affecting AssetExplorer before 7860, ServiceDesk Plus before 15290, ServiceDesk Plus MSP before 15150 and SupportCenter Plus before 15150 5. It needs the Create Query Reports permission, and the injection point is the query behind a report. Anyone who can write a report can run commands on the server that executes it.
CVE-2026-12591 has the same shape in M365 Manager Plus before 4818. A technician account escalates past its delegated scope in the delegated administration interface, and ManageEngine describes the possible outcome as remote code execution during administrative processing 6.
The 12507 account is a report author, and ManageEngine’s CNA vector puts the attack at high privileges required 5. The 12591 case is the one I would put with a help desk, because a technician seat in the delegated administration interface escalates past its own scope 6. I rank a week by who can reach the bug rather than by the score alone, which is why both of these make my short list.
Payara’s admin check trusts the caller’s address
CVE-2026-90908 lets a remote, unauthenticated attacker bypass JMX and RMI administrative access restrictions by spoofing the client host address 7. The restriction exists so only approved hosts reach the MBean server; spoofing the address passes the check and hands over administrative access, then code execution. Payara Micro is exposed only when its JMX connector is enabled.
CVE-2026-110003 is a second route through Payara Server’s secure-admin REST interface. An arbitrary X-GlassFish-authToken header waives the remote-rejection check before the token is validated, and the invalid token falls through to password authentication, which succeeds on a default domain that still has an empty administrative password 8. Both Payara records list eight ranges, including 5.20.0 below 5.93.0, 6.0.0 below 6.44.0, 7.0.0 below 7.6.0 and the 7.2024.1.Alpha1 line below 7.2026.11, so a 5.x or 6.x install needs the upgrade as much as a 7.x one 7 8.
An application server with a JMX port open is a middleware box somebody stood up for one application and left alone. That is the population I would query first, because the JMX port outlives the application it was opened for.
A 10.0 in a WordPress plugin
CVE-2026-124815 is an unauthenticated SQL injection in the Clockinator Lite WordPress plugin before 1.1.0 9. Its deletion actions skip the access check, and one builds a query from a table name in the request. CISA-ADP scored it 10.0. Anyone who can reach the site can delete rows from any table or read password hashes out of the users table.
The rest of the wave repeats the pattern. Ultimate Addons for Elementor Forms before 1.0.8 accepts an unauthenticated upload of a PHP file 10. User Verification before 2.0.49 issues a one-time code that never expires and carries no rate limit 11. Descope before 1.2.0 accepts any non-empty token and opens a session for whichever account it names 12.
I treat this class as an inventory question. The list tells me what to ask site owners about, and the answers name plugins installed for one form and kept for years.
TimePictra and the password inside the installer
Three Microchip TimePictra CVEs landed in the same batch. CVE-2026-8331 is an unrestricted upload of a dangerous file type with possible code execution, in versions before 12.0 13. CVE-2026-8332 is a hard-coded root password in the installation files 14. CVE-2026-8333 is a stored XSS 15.
I keep hunting that credential after the upgrade. The fix takes it out of future installers, which answers nothing about whether somebody already read the password off a file share. So I ask who held the installer media, and I check whether an appliance still accepts the old root password, because those two answers decide the exposure and the version number does not.
The rest of the wave
CVE-2026-124699 is code injection in Telerik UI for WinForms before 2026.4.1111, 7.8, where a crafted expression runs in the context of the application 16. The published vector puts the attack at local access with user interaction, so exposure depends on which desktop applications trust outside input. CVE-2026-92379 lets an authenticated remote user read and write files through the Notification API on Synology DSM 17. Both need an inventory answer before a severity argument.
The directive fixes the 16 November date on the Check Point bug. Everything else in the batch waits on an inventory answer, and the inventory is the slower half of the work.
-
National Vulnerability Database. (2026, November 12). CVE-2026-123039 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-123039 ↩︎ ↩︎ ↩︎ ↩︎
-
Check Point Software Technologies. (2026, November 12). CVE-2026-123039: Local privilege escalation to root in the DynamicCLI process via local world-writable control socket (sk1000362). Check Point Support. https://support.checkpoint.com/results/sk/sk1000362 ↩︎ ↩︎ ↩︎ ↩︎
-
Cybersecurity and Infrastructure Security Agency. (2026, November 13). Known exploited vulnerabilities catalog. https://www.cisa.gov/known-exploited-vulnerabilities-catalog ↩︎ ↩︎
-
Check Point Software Technologies. (2026, November 12). Security advisory: Active exploitation of PHP2Shell and local privilege escalation. Check Point Blog. https://blog.checkpoint.com/security/security-advisory-active-exploitation-of-php2shell-and-local-privilege-escalation/ ↩︎
-
National Vulnerability Database. (2026, November 12). CVE-2026-12507 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-12507 ↩︎ ↩︎
-
National Vulnerability Database. (2026, November 12). CVE-2026-12591 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-12591 ↩︎ ↩︎
-
National Vulnerability Database. (2026, November 12). CVE-2026-90908 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-90908 ↩︎ ↩︎
-
National Vulnerability Database. (2026, November 12). CVE-2026-110003 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-110003 ↩︎ ↩︎
-
National Vulnerability Database. (2026, November 12). CVE-2026-124815 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-124815 ↩︎
-
Tenable. (2026, November 12). CVE-2026-124814. Tenable CVE database. https://www.tenable.com/cve/CVE-2026-124814 ↩︎
-
Tenable. (2026, November 12). CVE-2026-76792. Tenable CVE database. https://www.tenable.com/cve/CVE-2026-76792 ↩︎
-
Tenable. (2026, November 12). CVE-2026-110959. Tenable CVE database. https://www.tenable.com/cve/CVE-2026-110959 ↩︎
-
National Vulnerability Database. (2026, November 12). CVE-2026-8331 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-8331 ↩︎
-
National Vulnerability Database. (2026, November 12). CVE-2026-8332 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-8332 ↩︎
-
Tenable. (2026, November 12). CVE-2026-8333. Tenable CVE database. https://www.tenable.com/cve/CVE-2026-8333 ↩︎
-
National Vulnerability Database. (2026, November 12). CVE-2026-124699 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-124699 ↩︎
-
Tenable. (2026, November 12). CVE-2026-92379. Tenable CVE database. https://www.tenable.com/cve/CVE-2026-92379 ↩︎