# CVE-2026-33072: FileRise: Default Encryption Key Enables Token Forgery and Config Decryption

> Hardcoded default encryption key allows attackers to forge upload tokens for arbitrary file upload and decrypt sensitive configuration secrets.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-f4xx-57cv-mg3x

## What is CVE-2026-33072?

CVE-2026-33072 is a high-severity vulnerability in error311 FileRise, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileRise is a self-hosted web file manager / WebDAV server. In versions prior to 3.9.0, a hardcoded default encryption key (default_please_change_this_key) is used for all cryptographic operations — HMAC token generation, AES config encryption, and session tokens — allowing any unauthenticated attacker to forge upload tokens for arbitrary file upload to shared folders, and to decrypt admin configuration secrets including OIDC client secrets and SMTP passwords. FileRise uses a single key (PERSISTENT_TOKENS_KEY) for all crypto operations. The default value default_please_change_this_key is hardcoded in two places and used unless the deployer explicitly overrides the environment variable. This issue is fixed in version 3.9.0.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Filerise Filerise.

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

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

## Is CVE-2026-33072 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33072 exists.

## Other vulnerabilities in error311 FileRise

- [CVE-2025-68116](https://insights.sbomify.com/CVE-2025-68116/): FileRise vulnerable to Cross-Site Scripting (XSS) in SVG File Handling (high 8.9)
- [CVE-2026-33329](https://insights.sbomify.com/CVE-2026-33329/): Path traversal in FileRise (high 8.1)
- [CVE-2025-62509](https://insights.sbomify.com/CVE-2025-62509/): FileRise improper ownership/permission validation allowed cross-tenant file operations (high 8.1)
- [CVE-2025-62510](https://insights.sbomify.com/CVE-2025-62510/): FileRise insecure folder visibility via name-based mapping and incomplete ACL checks (high 8.1)
- [CVE-2026-25231](https://insights.sbomify.com/CVE-2026-25231/): FileRise affected by an Unauthenticated File Read Due to Insufficient Access Control (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33072 is a high-severity vulnerability in error311 FileRise, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33072 exists.

Affected product: error311 FileRise. 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-33072/ (Markdown: https://insights.sbomify.com/CVE-2026-33072/index.md)
```

## Sources

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

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