# CVE-2026-25684: File Type Control rule bypass

> Attackers can bypass File Type Control policies in Zscaler Internet Access due to improper file type attribution evaluation.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-4j5q-5jhc-9378

## What is CVE-2026-25684?

CVE-2026-25684 is a medium-severity vulnerability in Zscaler ZIA File Type Control, published on 18 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A file type attribution issue in Zscaler Internet Access File Type Control evaluation rules may allow improper evaluation of File Type Control policies in rare circumstances.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-25684 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25684 is a medium-severity vulnerability in Zscaler ZIA File Type Control, published on 18 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-25684 in the wild and no public exploit code.

Affected product: Zscaler ZIA File Type Control. 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-25684/ (Markdown: https://insights.sbomify.com/CVE-2026-25684/index.md)
```

## Sources

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

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