CVE
free-fs auth bypass in share code checks
Affects free-fs 2.0.1 through 2.3.1 where shares are protected by a share code. 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:N/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 name no workaround. They do not say what to do while no 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? →
- 30/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
Summary
Dromara free-fs contains an authorization bypass that lets a remote attacker, without logging in, access files in code-protected shares because the share code is checked only in the client. An attacker who knows a share ID can list and download its files without the code, including on preview-only shares.
Original description
Dromara free-fs 2.0.1 through 2.3.1 contains an authorization bypass vulnerability that allows attackers to access code-protected shares because share codes are enforced only client-side. Attackers knowing a share ID can call the share items and download endpoints to list and download files without the code, even on preview-only shares.
Who should check
Teams running dromara free-fs 2.0.1 through 2.3.1 that use code-protected or preview-only file shares.
“Dromara free-fs 2.0.1 through 2.3.1”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- 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
- Severity8.2/10CVSS 8.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts name no workaround. They do not say what to do while no 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-129164 (Dromara free-fs 2.0.1 through 2.3.1 Share Code and Permission Scope Bypass), 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-129164 (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):
- The target share is protected by a share code. (source: https://www.vulncheck.com/advisories/dromara-free-fs-2.0.1-through-2.3.1-share-code-and-permission-scope-bypass)
- The attacker must know the share ID. (source: https://www.vulncheck.com/advisories/dromara-free-fs-2.0.1-through-2.3.1-share-code-and-permission-scope-bypass)
- Affected versions are free-fs 2.0.1 through 2.3.1. (source: https://www.vulncheck.com/advisories/dromara-free-fs-2.0.1-through-2.3.1-share-code-and-permission-scope-bypass)
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-129164 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129164 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-file/src/main/java/com/xddcodec/fs/file/service/impl/FileShareServiceImpl.java#L330-L333
- https://github.com/dromara/free-fs/blob/f8f4ff2a0b0af8fcd5cbecbf99a4afb7d0b7c020/fs-modules/fs-file/src/main/java/com/xddcodec/fs/file/service/impl/FileShareServiceImpl.java#L390-L397
- https://github.com/dromara/free-fs/blob/f8f4ff2a0b0af8fcd5cbecbf99a4afb7d0b7c020/fs-modules/fs-file/src/main/java/com/xddcodec/fs/file/service/impl/FileShareServiceImpl.java#L252-L268
- https://www.vulncheck.com/advisories/dromara-free-fs-2.0.1-through-2.3.1-share-code-and-permission-scope-bypass
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-129164
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-129164"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- dromara free-fs
From 2.0.1 · through 2.3.1
Evidence 8
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 6
- Report
- Repository
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129164
Is CVE-2026-129164 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?
Share codes are enforced only on the client side, so someone who knows a share ID can call the share items and download endpoints and list and download files without the code. This includes preview-only shares.Source: vulncheck.com
Which versions are affected by CVE-2026-129164?
free-fs: from 2.0.1 through 2.3.1.Source: cve.now feed data
Am I affected, and how do I check?
The affected range is free-fs 2.0.1 through 2.3.1, and only shares protected by a share code are described. To check, compare the installed free-fs version with that range and see whether the share in question uses a share code.Source: vulncheck.com
How do I fix CVE-2026-129164?
The checked facts list no fixed version and no patch, so no upgrade target can be named from them.Source: vulncheck.com
What if there's no patch?
The checked facts name no workaround. They do not say what to do while no fix is available.Source: vulncheck.com