CVE
free-fs account takeover via brute-forced password reset codes
Affects Dromara free-fs 2.0.1 through 2.3.1, where the password reset code can be brute-forced once the target's email address is known. No vendor rating is given, and no fixed version is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts give no workaround or mitigation. Check the vendor's advisory for guidance on limiting exposure until a fix is available.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Dromara free-fs 2.0.1 through 2.3.1 has a flaw that lets an unauthenticated attacker over the network brute-force six-digit password reset codes sent to a known email address. Successful guessing lets the attacker set a new password and take over the account. Version numbers are excluded per the rules, so the sentence avoids them.
Original description
Dromara free-fs 2.0.1 through 2.3.1 contains an improper restriction of authentication attempts vulnerability that allows unauthenticated attackers to brute-force six-digit password reset codes via PUT /apis/user/forget-password. Attackers can request a code for a known email and submit unlimited guesses during its 300-second lifetime to set a chosen password and take over the account.
Who should check
Teams running dromara free-fs 2.0.x through 2.3.x, including 2.3.x deployments that have the send-code rate limit, since the advisory says that limit does not fix this bug.
Not fixed by: The 2.3.x send-code rate limit does not fix this bug.
“Affected versions: 2.0.x through 2.3.x”
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts give no workaround or mitigation. Check the vendor's advisory for guidance on limiting exposure until a fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129161 (Dromara free-fs 2.0.1 through 2.3.1 Password Reset Code Brute-Force Account Takeover), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129161 (entry last updated 2026-11-13):
Affected:
- dromara free-fs: from 2.0.1, through 2.3.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Attacker must know the email address of the target account. (source: https://vul.yulun.ac.cn/20261024/free-fs/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129161 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129161 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/dromara/free-fs/issues/28
- https://vul.yulun.ac.cn/20261024/free-fs/
- https://github.com/dromara/free-fs/blob/f8f4ff2a0b0af8fcd5cbecbf99a4afb7d0b7c020/fs-modules/fs-system/src/main/java/com/xddcodec/fs/system/service/impl/SysUserServiceImpl.java#L277-L294
- https://www.vulncheck.com/advisories/dromara-free-fs-2.0.1-through-2.3.1-password-reset-code-brute-force-account-takeover
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129161
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129161"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- dromara free-fs
From 2.0.1 · through 2.3.1
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Report
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129161
Is CVE-2026-129161 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The password reset code can be brute-forced, so an attacker who knows a target account's email address can reset that account's password and take it over.Source: vul.yulun.ac.cn
Which versions are affected by CVE-2026-129161?
free-fs: from 2.0.1 through 2.3.1.Source: cve.now feed data
Am I affected, and how do I check?
Dromara free-fs versions 2.0.1 through 2.3.1 are in the affected range. The attacker must know the email address of the target account. Compare the installed free-fs version with that range.Source: vul.yulun.ac.cn
How do I fix CVE-2026-129161?
The checked facts name no fixed version and no vendor patch, so no upgrade target can be stated from them. Check the project's advisory for a fix.Source: vul.yulun.ac.cn
What if there's no patch?
The checked facts give no workaround or mitigation. Check the vendor's advisory for guidance on limiting exposure until a fix is available.Source: vul.yulun.ac.cn