VulnerabilityPublished 20 Mar 2026

CVE-2026-33072: error311 FileRise · Use of Hard-coded Credentials

Affects error311 FileRiseSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 3.9.0 soon.

Data as of 1 Nov 2026, 11:02 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.9.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade FileRise and error311/FileRise to 3.9.0.

Affected software

Product	Affected	Fixed in
error311FileRise	Affected <3.9.0	Fixed in 3.9.0
GitHuberror311/FileRise`pkg:github/error311/FileRise`Other threats	Affected <3.9.0	Fixed in 3.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade FileRise to version 3.9.0 or later, where the hardcoded key issue is resolved. If upgrading is not immediately possible, administrators must ensure that the PERSISTENT_TOKENS_KEY environment variable is explicitly set to a strong, unique cryptographic key, replacing the default hardcoded value. Regularly audit configuration files and environment variables to verify that no default keys remain in use. Implement network-level access controls to restrict exposure of the FileRise service to trusted networks and users only. Monitor logs for suspicious upload token usage or unauthorized file uploads. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block anomalous token generation or upload attempts. Finally, rotate any potentially compromised secrets such as OIDC client credentials and SMTP passwords to prevent further misuse.

Description

CVE-2026-33072 is a high-severity vulnerability in FileRise versions prior to 3.9.0 caused by the use of a hardcoded default encryption key. This key, 'default_please_change_this_key', is used for all cryptographic operations including HMAC token generation, AES configuration encryption, and session tokens. Because the key is hardcoded and widely known, unauthenticated attackers can forge upload tokens to upload arbitrary files to shared folders and decrypt sensitive admin configuration secrets such as OIDC client secrets and SMTP passwords. The vulnerability arises from the failure to override the default key via environment variables. This issue is fixed in version 3.9.0. The CVSS score is 8.

Impact

The impact of this vulnerability is significant for organizations using vulnerable versions of FileRise. Attackers can gain unauthorized access to upload arbitrary files, potentially leading to malware deployment, defacement, or data exfiltration. The ability to decrypt administrative secrets such as OIDC client secrets and SMTP passwords can facilitate further attacks including privilege escalation, lateral movement, and interception or manipulation of email communications. Confidentiality is severely compromised, while integrity is moderately affected due to unauthorized file uploads. Availability impact is low as the vulnerability does not directly enable denial of service. Since exploitation requires no authentication or user interaction and can be performed remotely over the network, the threat is highly accessible to attackers. Organizations relying on FileRise for sensitive file management or integration with identity providers and email systems are at elevated risk, especially if they have not updated to version 3.9.0 or have not overridden the default encryption key.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1188Initialization of a Resource with an Insecure Default (opens in a new tab)
Base weakness
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 19:42 UTC

WeaknessesCWE-798, CWE-1188

Technical details

References

Community reviews

Related threats