CVE-2026-77427

Source
https://cve.org/CVERecord?id=CVE-2026-77427
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-77427.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-77427
Aliases
  • GHSA-g6p5-9cpq-mp5h
Published
2026-10-14T20:32:55Z
Modified
2026-10-15T10:47:30Z
Severity
  • 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N CVSS Calculator
Summary
FileRise: Insecure default cryptographic key fallback in manual installs
Details

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.

Database specific
{
    "cna_assigner":  "GitHub_M",
    "cwe_ids":  [
        "CWE-1188",
        "CWE-798"
    ],
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/77xxx/CVE-2026-77427.json"
}
References

Affected packages

Git / github.com/error311/filerise

Affected ranges

Type
GIT
Repo
https://github.com/error311/filerise
Events
Database specific
Show details
{
    "extracted_events":  [
        {
            "introduced":  "3.9.0"
        },
        {
            "fixed":  "3.22.0"
        }
    ],
    "source":  "AFFECTED_FIELD"
}

Affected versions

v3.*
v3.10.0
v3.11.0
v3.11.1
v3.11.2
v3.12.0
v3.13.0
v3.14.0
v3.15.0
v3.16.0
v3.17.0
v3.18.0
v3.19.0
v3.20.0
v3.21.0
v3.9.0
v3.9.1
v3.9.2
v3.9.3
v3.9.4

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-77427.json"