CVE-2026-55189

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.2%, top 90% 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
Elevated
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.

RustFS is a distributed object storage system built in Rust. From 1.0.0-alpha.1 until 1.0.0-beta.9, when the FTP frontend is enabled, the FTP read and probe handlers dispatch directly to the storage backend without ever calling the IAM authorization function that the FTP write/list handlers (and the entire HTTP S3 path) use. As a result, any user who can authenticate to the FTP listener — including a user whose IAM policy contains an explicit Deny on s3:GetObject — can read (RETR) and stat (SIZE/MDTM) any object in any bucket, and probe any bucket (CWD), completely regardless of their IAM policy. This vulnerability is fixed in 1.0.0-beta.9.

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

Published

June 26, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

FTP frontend skips IAM authorization on object reads · Advisory · rustfs/rustfs · GitHub

https://github.com/rustfs/rustfs/security/advisories/GHSA-3g29-xff2-92vp

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55189?
CVE-2026-55189 is a high vulnerability published on June 26, 2026. RustFS is a distributed object storage system built in Rust. From 1.0.0-alpha.1 until 1.0.0-beta.9, when the FTP frontend is enabled, the FTP read and probe handlers dispatch directly to the storage backend without ever calling the IAM authorization function that the FTP write/list handlers (and…
When was CVE-2026-55189 disclosed?
CVE-2026-55189 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55189 actively exploited?
CVE-2026-55189 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55189?
CVE-2026-55189 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-55189?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55189, 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-55189

Explore →

Is Your Infrastructure Affected by CVE-2026-55189?

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

Start Free Scan →Browse All CVEs