https://vulnerability.circl.lu/sightings/feed 2026-09-01T09:26:50.333362+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/68cbd222-e74b-461f-bb69-f403a048bd90/export 2026-09-01T09:26:50.363359+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "68cbd222-e74b-461f-bb69-f403a048bd90", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-55874", "type": "seen", "source": "https://gist.github.com/alon710/f39d221628c93e95f65b186b807e9a92", "content": "# CVE-2026-55874: CVE-2026-55874: Cross-Bucket Path Traversal in SeaweedFS S3 API Gateway\n\n> **CVSS Score:** 7.7\n> **Published:** 2026-08-28\n> **Full Report:** https://cvereports.com/reports/CVE-2026-55874\n\n## Summary\nA critical path traversal vulnerability (CVE-2026-55874) in the SeaweedFS S3 API Gateway prior to version 4.34 allows authenticated remote attackers with write access to at least one bucket to bypass isolation. By supplying crafted directory traversal sequences in the X-Amz-Copy-Source header, an attacker can read objects from arbitrary buckets on the same deployment.\n\n## TL;DR\nSeaweedFS S3 API Gateway allows cross-bucket reads via path traversal in the X-Amz-Copy-Source header prior to version 4.34.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-22\n- **Attack Vector**: Network\n- **CVSS Score**: 7.7\n- **EPSS Score**: 0.00606\n- **Exploit Status**: poc\n- **CISA KEV Status**: Not Listed\n\n## Affected Systems\n\n- SeaweedFS\n- **SeaweedFS**: < 4.34 (Fixed in: `4.34`)\n\n## Mitigation\n\n- Upgrade SeaweedFS to version 4.34 or later to address the vulnerability in the codebase.\n- Deploy Web Application Firewall (WAF) rules targeting the X-Amz-Copy-Source header to filter and block path traversal sequences.\n- Audit historic S3 access logs and reverse proxy logs for requests involving parent directory segments in copy handlers.\n\n**Remediation Steps:**\n1. Identify all deployed SeaweedFS S3 API Gateway instances.\n2. Schedule maintenance windows to deploy SeaweedFS version 4.34 or higher.\n3. If immediate upgrade is impossible, write a custom WAF signature or Nginx rule to check the X-Amz-Copy-Source header for path-traversal strings.\n4. Verify blocking efficacy with standard S3 testing utilities.\n\n## References\n\n- [SeaweedFS Fix Commit](https://github.com/seaweedfs/seaweedfs/commit/b44cf51fe931bd75aa4d37ae766bea90d7f85ccd)\n- [SeaweedFS Pull Request #9929](https://github.com/seaweedfs/seaweedfs/pull/9929)\n- [SeaweedFS Release 4.34](https://github.com/seaweedfs/seaweedfs/releases/tag/4.34)\n- [GitHub Security Advisory GHSA-56wq-x3wv-3ff4](https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-56wq-x3wv-3ff4)\n- [NVD CVE-2026-55874 Details](https://nvd.nist.gov/vuln/detail/CVE-2026-55874)\n- [CVE.org Record](https://www.cve.org/CVERecord?id=CVE-2026-55874)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-55874) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-08-29T11:31:50.433163Z"} 2026-08-29T11:31:50.433163+00:00