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

High 8.2 Published 20 Mar 2026 Updated 20 Mar 2026

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

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

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, CWE-1188

Which versions are affected by CVE-2026-33072?

It affects 1 product.

Products include 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.

Sources

Also known as GHSA-f4xx-57cv-mg3x.