Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as CMA admin with read-write on Domain A
-
DeliveryAccess Compliance Best Practices metadata interface
-
ExploitCraft SQL injection payload targeting cross-domain table rows
-
ExecutionSubmit malicious metadata to vulnerable endpoint
-
PersistInjected SQL bypasses domain query isolation
-
ImpactModify or read Compliance metadata in Domain B without authorization
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The Compliance feature must be explicitly enabled on Check Point Multi-Domain Management - this is a non-default or separately licensed module, not active in all deployments. The attacker must be an authenticated administrator (PR:H) holding read-write access to at least one Management Domain CMA; read-only CMA administrators or lower-privileged accounts are not confirmed as viable vectors based on the description. High attack complexity (AC:H) indicates the SQL injection likely requires precise payload construction, possibly with knowledge of the target domain's metadata table structure. The impact is limited to the Compliance Best Practices metadata store - it does not affect firewall policy, gateway configurations, or authentication systems. Limiting factors include: mandatory pre-authentication as a high-privilege CMA admin, enabled Compliance feature, high exploit complexity, and unchanged scope preventing lateral movement beyond the metadata store. |
| Impact | The CVSS 4.1 (Medium) score reflects a meaningfully constrained threat profile: PR:H (High privileges required) means an attacker must already possess authenticated administrator credentials with read-write access to at least one CMA - a significant pre-requisite that eliminates external, unauthenticated threat actors. AC:H (High complexity) further indicates exploitation is non-trivial, likely requiring precise crafting of the SQL payload and specific knowledge of the target domain's metadata schema. S:U (Unchanged scope) and C:L/I:L/A:L indicate the blast radius is limited to low-level confidentiality, integrity, and availability impact within the system boundary. EPSS at 0.04% (13th percentile) corroborates that active, widespread exploitation is not observed. The vulnerability is not listed in CISA KEV. The primary real-world risk is an insider threat or a compromised CMA administrator account pivoting to tamper with compliance posture reporting in domains they should not control - a governance and audit integrity concern rather than a remote compromise risk. No conflicting signals between CVSS vector and description are noted. |
| Exploit ScenarioDerived | An authenticated Check Point CMA administrator with legitimate read-write access to Domain A - such as an insider or an attacker who has compromised a domain-scoped admin account - accesses the Compliance Best Practices metadata interface and submits a crafted SQL injection payload within a metadata field. The injected SQL escapes the Domain A query context, crosses the domain isolation boundary in the backend database, and modifies Compliance Best Practices metadata records belonging to Domain B, where the administrator holds no assigned permissions. This could be used to falsify compliance status, suppress Best Practice violations, or corrupt audit trail data for a domain outside the attacker's authorized scope. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 08, 2026
Cross-domain RBAC bypass in Check Point Quantum Security Management allows an authenticated administrator with read-write access to one Management Domain (CMA) to modify Compliance Best Practices metadata stored in a separate Management Domain where they hold no permissions. The underlying root cause is SQL injection (CWE-89, corroborated by the 'SQLi' intelligence tag), suggesting the Compliance feature's metadata storage does not enforce domain-level query isolation. Affected releases span R81.10 and below, R81.20 up to Jumbo Hotfix Take 127, R82 up to Jumbo Hotfix Take 91, and R82.10 up to Jumbo Hotfix Take 19. No public exploit identified at time of analysis, and EPSS of 0.04% reflects low observed exploitation probability.
RemediationAI
The primary fix is to upgrade to a patched Jumbo Hotfix Take for the relevant release train, per Check Point advisory sk184992 (https://support.checkpoint.com/results/sk/sk184992): for R82, apply Jumbo Hotfix Take 92 or later; for R81.20, apply Jumbo Hotfix Take 128 or later; for R82.10, apply Jumbo Hotfix Take 20 or later; R81.10 and below should be treated as end-of-supported-fix-path and upgraded to a current release. Exact hotfix take numbers for R81.10 and below are not independently confirmed from available data - consult the vendor advisory directly. As a compensating control if immediate patching is not possible, disable the Compliance feature within Multi-Domain Management to remove the vulnerable code path entirely; note this will suspend compliance reporting and Best Practices evaluation across all CMAs. Additionally, audit and restrict CMA administrator accounts to the minimum necessary domains, reducing the population of principals who could abuse this bypass. Patched version numbers are sourced from EUVD-2026-31823 and should be verified against the vendor advisory before deployment.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the Compliance module of Check Point Quantum Security Management (CPE: cpe:2.3:a:checkpoint:quantum_security_management:*:*:*:*:*:*:*:*), which is deployed in Multi-Domain Management (MDM) environments where multiple independent Management Domains (CMAs) are administered from a shared infrastructure. CWE-89 (SQL Injection) indicates that the Compliance Best Practices metadata - likely stored in a relational database backend shared across or insufficiently partitioned between CMAs - is vulnerable to SQL injection. An attacker-controlled metadata field submitted within one CMA context is not properly sanitized before being incorporated into a SQL query, enabling the injected payload to escape the domain boundary and reach rows belonging to another CMA. This breaks the foundational RBAC guarantee of MDM, where domain isolation is the primary security control preventing one CMA administrator from affecting another's environment.
Know when Checkpoint gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
Primary rating from Vendor (checkpoint) · only source for this CVE.
CVSS VectorVendor: checkpoint
DescriptionCVE.org
When Compliance is enabled on Check Point Multi-Domain Management, an authenticated administrator with read-write access to one Management Domain (CMA) can modify stored metadata associated with Compliance Best Practices in another Management Domain, where the administrator has no access permissions, bypassing Role-Based Access Control (RBAC).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Checkpoint
View allGNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which
Potentially allowing an attacker to read certain information on Check Point Security Gateways once connected to the inte
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of
backend/comics/comics-document.c (aka the comic book backend) in GNOME Evince before 3.24.1 allows remote attackers to e
Remote code execution in Check Point Quantum Security Gateway arises from improper certificate trust validation during V
Authentication bypass in the Check Point SmartConsole login process lets an unauthenticated remote attacker mint a valid
Authentication bypass in Check Point Quantum Security Gateway and Spark Firewalls allows unauthenticated remote attacker
Unauthenticated attackers who can reach the file-upload interface of Check Point Management Server can combine directory
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. Rated med
Remote code execution in Check Point Quantum Security Gateway and Quantum Security Management stems from a heap-based bu
Unauthenticated remote code execution affects Check Point Quantum Security Management, where a stack-based buffer overfl
The huggingface/transformers library is vulnerable to arbitrary code execution through deserialization of untrusted data
EUVD-2026-31823
GHSA-729m-hm3g-pgc3
NVD
CVE.org
EPSS
VulDB
Exploit-DB