BoletimSecSeptember 11, 2026🇵🇹Translated from Portuguese

Check Point Patches Two Critical VPN Vulnerabilities Allowing Unauthenticated Remote Code Execution

Check Point has addressed two critical vulnerabilities impacting its Security Gateway, Security Management Server, and locally managed Spark Firewall. Both issues carry a CVSS score of 9.8 and permit unauthenticated remote code execution.

The first flaw, CVE-2026-85102, lies in the certificate trust validation process during VPN negotiation. An attacker can force the negotiation and run arbitrary code on the Security Gateway.

The second vulnerability, CVE-2026-85103, is a heap-based buffer overflow that occurs when parsing the ASN.1 structure of certificates used in VPN connections. Exploitation requires sending a specially crafted certificate.

Affected releases include R81.20, R82, and R82.10 prior to the respective hotfixes, along with the unsupported R80.40 and R81 lines. Version R82.20 is not impacted. Patches are available in R82.10 Take 44, R82 Take 126, R81.20 Take 166, and dedicated builds for Spark Firewall.

Environments with Live Patch enabled received automatic protection starting September 9. For site-to-site VPN, administrators can temporarily disable implicit VPN rules and restrict UDP ports 500 and 4500 to known addresses. No workaround exists for remote access VPN or locally managed Spark Firewall.

The vulnerabilities were identified by Check Point’s own research team. As of the September 10 disclosure, the company reported no evidence of active exploitation or publicly available proof-of-concept code.

Related articles

SecuritylabVulnerabilities & Exploits

PKCE Becomes Mandatory for OAuth Public Clients as RFC 9700 and OAuth 2.1 Close Authorization Code Interception Risks

PKCE, or Proof Key for Code Exchange, was introduced in RFC 7636 to prevent code interception attacks in OAuth 2.0 flows used by mobile and single-page applications. The mechanism generates a code_verifier and derives a code_challenge using S256 hashing to bind the authorization code to the original client session. Without PKCE, malicious apps on the same device can hijack custom URI schemes like myapp://callback and exchange stolen codes for access tokens. RFC 9700, published in January 2025, now mandates PKCE for public clients and recommends it for confidential ones while requiring S256 over the weaker plain method. The upcoming OAuth 2.1 draft further embeds PKCE into the core authorization code flow and removes implicit and resource owner password credentials grants. Major providers including Auth0, Okta, and Microsoft Entra ID show varying default support, highlighting the need for explicit S256 implementation. The standard also protects against code injection attacks even when client secrets are present.

HispasecVulnerabilities & Exploits

Attackers Chain JFrog Artifactory CVEs for Rapid Admin Takeover and Backdoor Deployment

Real-world attacks against self-hosted JFrog Artifactory have chained multiple CVEs to escalate from unauthenticated requests to full administrative control. Attackers achieved persistence by installing malicious Groovy plugins, executing shell commands, and deploying Rust-based backdoors within minutes. The primary chain relies on CVE-2026-42018 and CVE-2026-42016, allowing anonymous token acquisition and privilege escalation without proper scope validation. A separate critical flaw, CVE-2026-82329 with CVSS 9.8, enables direct authentication bypass and admin token creation on default configurations. Patches are available across multiple 7.x branches, and defenders are urged to audit logs for anonymous admin actions and inspect for unauthorized plugins and binaries. The incidents highlight risks to software supply chains when artifact repositories are compromised.

AntiMalwareVulnerabilities & Exploits

Positive Technologies Acquires Stake in CyberOK to Advance EASM and PentOps Technologies

Positive Technologies has acquired a stake in cybersecurity developer CyberOK, with the size of the investment and deal terms remaining undisclosed. The partnership will focus on developing External Attack Surface Management (EASM) solutions and PentOps technologies that identify overlooked external assets and validate whether attackers can exploit them. Collaboration between the companies began in 2026, with CyberOK technologies already integrated into PT EASM and the PT X cloud platform. In less than six months, pilot projects for PT EASM exceeded 70, and Positive Technologies expects 80 percent of successful trials to convert into deals by late 2026 or early 2027. The Russian EASM market is projected at 2-2.5 billion rubles by the end of 2026, potentially reaching 8 billion rubles by 2031 when combined with continuous security validation solutions. PentOps will provide continuous cloud-based penetration testing that automatically verifies exploitability of discovered issues, moving beyond simple vulnerability lists. In 96 percent of pilots, unaccounted IT assets with critical vulnerabilities were identified, and CyberOK continues to develop the Vulnum knowledge base along with AI agents and Offensive SOC capabilities.

HabrVulnerabilities & Exploits

Exploiting CVE-2025-55182 React2Shell Vulnerability on Hack The Box Reactor Machine

A detailed walkthrough demonstrates remote code execution against a seasonal Hack The Box machine named Reactor by abusing the critical Next.js deserialization flaw CVE-2025-55182, also known as React2Shell. The attack begins with Nmap reconnaissance revealing an exposed Next.js service on port 3000, followed by Wappalyzer identification of an outdated framework version. Public exploit code is used to obtain an initial reverse shell as the node user without authentication. Credential access is achieved by extracting password hashes from the reactor.db SQLite database and cracking the engineer account with Hashcat against rockyou.txt. Privilege escalation leverages an exposed Node.js Inspector debug port on 9229, allowing WebSocket interaction via websocat to set the SUID bit on /bin/bash and obtain root access. The article highlights both the impact of the unauthenticated RCE vulnerability and common misconfigurations such as forgotten debug ports on production systems.