# CVE-2026-77427: FileRise: Insecure default cryptographic key fallback in manual installs

> Attackers with access to ciphertext files can decrypt TOTP secrets or credentials using a known fallback key in manual FileRise installations.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-g6p5-9cpq-mp5h

## What is CVE-2026-77427?

CVE-2026-77427 is a medium-severity vulnerability in error311 FileRise, published on 14 Oct 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-based file manager with multi-file upload, editing, and batch operations. From 3.9.0 until 3.22.0, pristine manual FileRise installations without PERSISTENT_TOKENS_KEY or metadata/persistent_tokens.key can activate a published legacy compatibility key. If an attacker separately obtains ciphertext-bearing account or configuration files, the known fallback key can enable decryption of TOTP secrets or credentials. Docker installations already generated a unique persistent key, and existing installations are not automatically rotated because doing so could make encrypted state unreadable. This issue is fixed in version 3.22.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-77427?


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

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

## Is CVE-2026-77427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77427 is a medium-severity vulnerability in error311 FileRise, published on 14 Oct 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-77427 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-77427/ (Markdown: https://insights.sbomify.com/CVE-2026-77427/index.md)
```

## Sources

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

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