CVE-2026-55873

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% 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
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 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. In versions 4.08 through 4.33, requests signed with SigV4 service s3tables are routed to the S3Tables management API where authorization collapses account-less S3 identities into the shared admin account and fails open, allowing an authenticated low-privileged S3 user to enumerate administrator-owned table bucket names and ARNs. This issue is fixed in version 4.34.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

Advisory Details (4)

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

Improper authorization in the S3Tables / Iceberg REST management API lets a low-privileged S3 user enumerate administrator-owned table buckets · Advisory · seaweedfs/seaweedfs · GitHub

https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-hgpf-8634-g44c
github_release Patch Available

4.34

Patch available: seaweedfs/seaweedfs 4.34

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

s3tables: scope management authorization to the caller's identity

Fix merged in seaweedfs/seaweedfs PR #9961 on 2026-06-14 — awaiting tagged release

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

commit b13463880c1f (seaweedfs/seaweedfs)

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

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

Vendor Advisories for CVE-2026-55873(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/seaweedfs/seaweedfs—0.0.0-20260614205536-b13463880c1f—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 48× 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-08-30 07:37 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 21:51 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-26 08:26 UTCEG score recompute
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 01:10 UTCEG score recompute
  10. 2026-08-23 01:35 UTCEG score recompute
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 01:50 UTCEG score recompute
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 02:04 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 02:00 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 20:45 UTCEG score recompute
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 13:10 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 13:24 UTCEG score recompute
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 13:39 UTCEG score recompute
Show 58 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 13:50 UTCEG score recompute
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-12 14:15 UTCEG score recompute
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-11 14:29 UTCEG score recompute
  7. 2026-08-11 00:00 UTCEPSS rescore
  8. 2026-08-09 14:59 UTCEG score recompute
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-08 15:14 UTCEG score recompute
  12. 2026-08-06 15:43 UTCEG score recompute
  13. 2026-08-06 13:47 UTCEPSS rescore
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-05 15:53 UTCEG score recompute
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 13:42 UTCEG score recompute
  18. 2026-08-04 10:39 UTCEPSS rescore
  19. 2026-08-03 12:56 UTCEG score recompute
  20. 2026-08-03 10:36 UTCEPSS rescore
  21. 2026-08-02 11:33 UTCEG score recompute
  22. 2026-08-02 02:27 UTCEPSS rescore
  23. 2026-07-31 12:01 UTCEG score recompute
  24. 2026-07-30 16:28 UTCEPSS rescore
  25. 2026-07-30 12:14 UTCEG score recompute
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-29 12:09 UTCEG score recompute
  28. 2026-07-28 15:37 UTCEPSS rescore
  29. 2026-07-28 12:23 UTCEG score recompute
  30. 2026-07-27 12:13 UTCEG score recompute
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-26 12:28 UTCEG score recompute
  33. 2026-07-25 14:18 UTCEPSS rescore
  34. 2026-07-24 14:18 UTCEPSS rescore
  35. 2026-07-23 14:18 UTCEPSS rescore
  36. 2026-07-23 03:20 UTCEG score recompute
  37. 2026-07-22 14:08 UTCEPSS rescore
  38. 2026-07-21 15:25 UTCEPSS rescore
  39. 2026-07-20 17:08 UTCEPSS rescore
  40. 2026-07-19 14:31 UTCEPSS rescore
  41. 2026-07-19 14:31 UTCEPSS rescore
  42. 2026-07-19 02:29 UTCEPSS rescore
  43. 2026-07-18 10:04 UTCEPSS rescore
  44. 2026-07-16 17:03 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 16:57 UTCEPSS rescore
  47. 2026-07-15 02:00 UTCEPSS rescore
  48. 2026-07-15 02:00 UTCEPSS rescore
  49. 2026-07-13 22:31 UTCEPSS rescore
  50. 2026-07-13 06:13 UTCEPSS rescore
  51. 2026-07-13 06:13 UTCEPSS rescore
  52. 2026-07-12 05:46 UTCEPSS rescore
  53. 2026-07-11 08:27 UTCEPSS rescore
  54. 2026-07-11 08:27 UTCEPSS rescore
  55. 2026-07-09 19:10 UTCEPSS rescore
  56. 2026-07-09 19:10 UTCEPSS rescore
  57. 2026-07-08 14:58 UTCEG score recompute
  58. 2026-07-08 14:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55873?
CVE-2026-55873 is a medium vulnerability published on July 8, 2026. SeaweedFS is a distributed storage system. In versions 4.08 through 4.33, requests signed with SigV4 service s3tables are routed to the S3Tables management API where authorization collapses account-less S3 identities into the shared admin account and fails open, allowing an authenticated…
When was CVE-2026-55873 disclosed?
CVE-2026-55873 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-55873 actively exploited?
CVE-2026-55873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.1% of all scored CVEs.
What is the CVSS score of CVE-2026-55873?
CVE-2026-55873 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-55873?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55873, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55873

Explore →

Is Your Infrastructure Affected by CVE-2026-55873?

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

Start Free Scan →Browse All CVEs