# CVE-2026-3266: Improper access control vulnerability has been discovered in OpenText™ Filr.

> Unauthenticated attackers can bypass authentication to obtain XSRF tokens and execute RPC calls in OpenText Filr.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:L/SC:L/SI:L/SA:L/S:P/AU:Y/R:I/V:D/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-7qvm-mwp7-fqc3

## What is CVE-2026-3266?

CVE-2026-3266 is a high-severity missing authorization vulnerability in OpenText™ Filr, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in OpenText™ Filr allows Authentication Bypass. The vulnerability could allow unauthenticated users to get XSRF token and do RPC with carefully crafted programs.

This issue affects Filr: through 25.1.2.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Opentext Filr.

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

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

## Is CVE-2026-3266 being exploited?

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

## Other vulnerabilities in OpenText™ Filr

- [CVE-2024-4187](https://insights.sbomify.com/CVE-2024-4187/): Cross-site scripting in Filr (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3266 is a high-severity missing authorization vulnerability in OpenText™ Filr, published on 3 Mar 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-3266 in the wild and no public exploit code.

Affected product: OpenText™ Filr. 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-3266/ (Markdown: https://insights.sbomify.com/CVE-2026-3266/index.md)
```

## Sources

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

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