CVE-2026-55874

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SeaweedFS is a distributed storage system. Prior to 4.34, the S3 API gateway does not reject dot-dot path segments in the X-Amz-Copy-Source header used by CopyObject and UploadPartCopy, allowing an authenticated identity scoped to one bucket to read objects from other buckets through server-side copy. This issue is fixed in version 4.34.

CVSS v3
7.7
EG Score
7.7(medium)
EPSS
24.8%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Path traversal in the S3 gateway X-Amz-Copy-Source header allows cross-bucket object read · Advisory · seaweedfs/seaweedfs · GitHub

https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-56wq-x3wv-3ff4
github_release Patch Available

4.34

Patch available: seaweedfs/seaweedfs 4.34

https://github.com/seaweedfs/seaweedfs/releases/tag/4.34
github_pr

s3: validate copy source path segments

Fix merged in seaweedfs/seaweedfs PR #9929 on 2026-06-12 — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/pull/9929
github_commit

commit b44cf51fe931 (seaweedfs/seaweedfs)

Fix landed in seaweedfs/seaweedfs commit b44cf51fe931 — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/commit/b44cf51fe931bd75aa4d37ae766bea90d7f85ccd

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 15:48 UTCEG score recompute
  4. 2026-07-15 02:48 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 13:49 UTCEG score recompute
  8. 2026-07-14 00:50 UTCEG score recompute
  9. 2026-07-13 22:31 UTCEPSS rescore
  10. 2026-07-13 11:51 UTCEG score recompute
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-12 22:52 UTCEG score recompute
  14. 2026-07-12 09:53 UTCEG score recompute
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 20:54 UTCEG score recompute
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 07:55 UTCEG score recompute
  20. 2026-07-10 18:56 UTCEG score recompute
  21. 2026-07-10 05:57 UTCEG score recompute
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 16:57 UTCEG score recompute
  25. 2026-07-09 03:57 UTCEG score recompute
Show 2 more
  1. 2026-07-08 14:58 UTCEG score recompute
  2. 2026-07-08 14:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55874?
CVE-2026-55874 is a high vulnerability published on July 8, 2026. SeaweedFS is a distributed storage system. Prior to 4.34, the S3 API gateway does not reject dot-dot path segments in the X-Amz-Copy-Source header used by CopyObject and UploadPartCopy, allowing an authenticated identity scoped to one bucket to read objects from other buckets through server-side…
When was CVE-2026-55874 disclosed?
CVE-2026-55874 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55874 actively exploited?
CVE-2026-55874 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55874?
CVE-2026-55874 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-55874?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55874, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55874

Explore →

Is Your Infrastructure Affected by CVE-2026-55874?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs