# CVE-2026-48133: Identity Awareness Captive Portal - Unauthenticated Local File Inclusion

> An unauthenticated attacker can read internal files on the Security Gateway when the Identity Awareness blade is enabled with Browser-Based Authentication.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-fc4q-p6gg-r9rr

## What is CVE-2026-48133?

CVE-2026-48133 is a high-severity path traversal vulnerability in checkpoint Quantum Security Gateway, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When the Identity Awareness blade is enabled with Browser-Based Authentication, an unauthenticated user may be able to read certain internal files on the Security Gateway.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2026-48133 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48133 is a high-severity path traversal vulnerability in checkpoint Quantum Security Gateway, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48133 in the wild and no public exploit code.

Affected product: checkpoint Quantum Security Gateway. 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-48133/ (Markdown: https://insights.sbomify.com/CVE-2026-48133/index.md)
```

## Sources

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

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