Password spraying via username-keyed login throttling
Published Oct 14, 2026 · Updated Oct 14, 2026
Login throttling in error311 FileRise before 3.21.0 allows remote attackers to exceed password-guessing limits by rotating usernames. AuthModel::getFailedLoginKey() combines the source IP address with the supplied username, giving each name an independent attempt budget without a source-wide limit. No credentials are required; per-user throttling remains effective, and the flaw does not itself bypass authentication or disclose stored files.
Summary
What happened
Login throttling in error311 FileRise before 3.21.0 allows remote attackers to exceed password-guessing limits by rotating usernames. AuthModel::getFailedLoginKey() combines the source IP address with the supplied username, giving each name an independent attempt budget without a source-wide limit. No credentials are required; per-user throttling remains effective, and the flaw does not itself bypass authentication or disclose stored files.
The record
- CVE
- CVE-2026-69193
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- error311
- Product
- FileRise
- Classifications
- CWE-307, T1110.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.21.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Upstream advisory username-rotation proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started