# CVE-2026-48136: Authenticated Administrator Role-Based Access Control Bypass in Compliance

> Authenticated administrators can bypass RBAC to modify compliance metadata in unauthorized management domains when Compliance is enabled.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-729m-hm3g-pgc3

## What is CVE-2026-48136?

CVE-2026-48136 is a medium-severity missing authorization vulnerability in checkpoint Quantum Security Management, published on 26 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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).

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-48136?


## How do I fix CVE-2026-48136?

No fix has been published for CVE-2026-48136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48136 being exploited?

There is no known exploitation of CVE-2026-48136 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48136 and fix it if it is affected.

What it is: CVE-2026-48136 is a medium-severity missing authorization vulnerability in checkpoint Quantum Security Management, published on 26 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48136 in the wild and no public exploit code.

Affected product: checkpoint Quantum Security Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48136/ (Markdown: https://insights.sbomify.com/CVE-2026-48136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48136
- OSV: https://osv.dev/vulnerability/CVE-2026-48136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48136/
Summaries are generated and may contain mistakes; the official description above is the record.