CVE-2026-77427

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.

CVSS v3 5.9 MEDIUM

5.9^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 2.2 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity HIGH

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact NONE

Scope UNCHANGED

References

Link	Resource
https://github.com/error311/FileRise/commit/b5213b66d4c668a45f1b7600aa62b79cb66ddbe6
https://github.com/error311/FileRise/releases/tag/v3.22.0
https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h
https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h

Configurations

No configuration.

History

20 Oct 2026, 03:17

Type	Values Removed	Values Added
References	~~() https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h -~~	() https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h -

14 Oct 2026, 21:17

Type	Values Removed	Values Added
New CVE

Information

Published : 2026-10-14 21:17

Updated : 2026-10-20 03:17

NVD link : CVE-2026-77427

Mitre link : CVE-2026-77427

CVE.ORG link : CVE-2026-77427

JSON object : View

Products Affected

No product.

CWE

CWE-798

Use of Hard-coded Credentials

CWE-1188

Initialization of a Resource with an Insecure Default

{"id": "CVE-2026-77427", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-77427", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-10-20T02:08:44.589886Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.2}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "error311", "product": "FileRise", "versions": [{"status": "affected", "version": ">= 3.9.0, < 3.22.0"}]}]}], "published": "2026-10-14T21:17:39.447", "references": [{"url": "https://github.com/error311/FileRise/commit/b5213b66d4c668a45f1b7600aa62b79cb66ddbe6", "source": "security-advisories@github.com"}, {"url": "https://github.com/error311/FileRise/releases/tag/v3.22.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h", "source": "security-advisories@github.com"}, {"url": "https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-798"}, {"lang": "en", "value": "CWE-1188"}]}], "descriptions": [{"lang": "en", "value": "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."}], "lastModified": "2026-10-20T03:17:16.560", "sourceIdentifier": "security-advisories@github.com"}