CVE-2026-129852: SeaweedFS before 4.42 File Existence Disclosure via VolumeServer.FetchAndWriteNeedle
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- No fixed version is recorded, but the references include a patch (commit or PR) link.
Low priority for now. See the fix and affected versions sections below.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
SeaweedFS before 4.42 contains an information disclosure vulnerability that allows unauthenticated attackers to probe local files by supplying a filesystem path in gcs_google_application_credentials. Attackers can send crafted gRPC FetchAndWriteNeedle requests and use differing error messages to learn file existence, readability, and partial content shape on the host.
- Published
- Nov 16, 2026
- Updated
- Nov 16, 2026
- EPSS
- —
- CWE
- CWE-73
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
seaweedfs seaweedfs
- before 4.42affected
Same product
seaweedfs: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-72920SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control39Monitor
- CVE-2026-73080SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle37Monitor
- CVE-2026-77298SeaweedFS S3 OIDC Bearer authentication bypasses IAM role trust policy34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-77611Aug 26, 2026 · SeaweedFS: Authenticated S3 object-scope bypass in PutObjectAcl allows overwriting a different object with the same basename28Monitor
- ← EarlierCVE-2026-100413Oct 14, 2026 · SeaweedFS: Hard-coded SSH host key can be presented by certain standalone SFTP Helm deployments28Monitor
- ← EarlierCVE-2026-129851Nov 16, 2026 · SeaweedFS before 4.42 SSRF via VolumeServer.FetchAndWriteNeedle Replica URLs27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- JeongAhn Jangfinder
- Chris Luremediation developer
Not on record for this CVE: EPSS history · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-73 · External Control of File Name or PathCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- URL EncodingCAPEC-72likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
- Using UTF-8 Encoding to Bypass Validation LogicCAPEC-80likelihood: High · High
Change log (1)
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
- github.com/seaweedfs/seaweedfs/commit/d713ab49f9c18f2188cdce2350f4ab95d19e2f17
- github.com/seaweedfs/seaweedfs/releases/tag/4.42
- github.com/seaweedfs/seaweedfs/security/advisories/GHSA-939f-xh28-2q48
- www.vulncheck.com/advisories/seaweedfs-before-4.42-file-existence-disclosure-via-volumeserver-fetchandwriteneedle
Vendor advisories and official records. Exploit/PoC links are deliberately left out.