CVE-2026-77611

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-66770 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

SeaweedFS is a distributed storage system for files and blobs. In versions prior to 4.40, an authenticated S3 principal with permissions scoped to a nested object key can overwrite a different object outside that scope by calling PutObjectAcl on the key it is allowed to access. The handler authorizes the request against the requested nested key but then writes the updated entry back to the bucket root rather than the key's actual parent directory, so an ACL change on allowed/protected.txt is instead applied to protected.txt at the bucket root. Because the update carries the full entry rather than only ACL metadata, an existing target object is overwritten with the content, metadata, owner information, and ACL of the scoped object, bypassing the object-level action scoping configured through the static S3 identity file. This issue is fixed in version 4.40.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 26, 2026
Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit 311bc3a6dfbd (seaweedfs/seaweedfs)

Fix landed in seaweedfs/seaweedfs commit 311bc3a6dfbd — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/commit/311bc3a6dfbd042751692bc3de8accc516fcf8c1
GitHub advisoryMentions a patch (unverified)

Authenticated S3 object-scope bypass in PutObjectAcl allows overwriting a different object with the same basename · Advisory · seaweedfs/seaweedfs · GitHub

https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-9x53-cjpr-m682

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 116 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 17 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-28 19:31 UTCEG score recompute
  7. 2026-10-28 18:25 UTCOSV refresh
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-25 14:01 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-20 20:46 UTCEG score recompute
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-18 03:11 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 74 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-13 06:55 UTCEG score recompute
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-12 15:37 UTCEG score recompute
  5. 2026-10-11 19:23 UTCEG score recompute
  6. 2026-10-11 16:39 UTCEG score recompute
  7. 2026-10-11 13:57 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-10 06:03 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-09 03:19 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-08 01:44 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-06 21:47 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-05 20:44 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-05 08:13 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-03 16:05 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-02 22:11 UTCEG score recompute
  25. 2026-10-01 21:04 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  27. 2026-09-30 19:57 UTCEG score recompute
  28. 2026-09-30 06:00 UTCEG score recompute
  29. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  30. 2026-09-28 23:13 UTCEG score recompute
  31. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  32. 2026-09-27 21:33 UTCEG score recompute
  33. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-09-26 20:30 UTCEG score recompute
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  36. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  37. 2026-09-24 16:10 UTCEG score recompute
  38. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-09-24 03:38 UTCEG score recompute
  40. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  41. 2026-09-23 02:35 UTCEG score recompute
  42. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  43. 2026-09-22 01:31 UTCEG score recompute
  44. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  45. 2026-09-21 00:29 UTCEG score recompute
  46. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  47. 2026-09-19 23:17 UTCEG score recompute
  48. 2026-09-18 22:02 UTCEG score recompute
  49. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  50. 2026-09-17 20:57 UTCEG score recompute
  51. 2026-09-16 19:06 UTCEG score recompute
  52. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  53. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  54. 2026-09-15 15:09 UTCEG score recompute
  55. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  56. 2026-09-14 01:33 UTCEG score recompute
  57. 2026-09-13 00:30 UTCEG score recompute
  58. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  59. 2026-09-11 23:26 UTCEG score recompute
  60. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  61. 2026-09-11 10:54 UTCEG score recompute
  62. 2026-09-10 09:44 UTCEG score recompute
  63. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  64. 2026-09-09 00:47 UTCEG score recompute
  65. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  66. 2026-09-07 17:25 UTCEG score recompute
  67. 2026-09-06 16:22 UTCEG score recompute
  68. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  69. 2026-09-06 03:50 UTCEG score recompute
  70. 2026-09-04 14:10 UTCEG score recompute
  71. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  72. 2026-09-03 00:26 UTCEG score recompute
  73. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  74. 2026-09-01 23:09 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77611?
CVE-2026-77611 is a high-severity vulnerability; its CVE record was published on August 26, 2026. SeaweedFS is a distributed storage system for files and blobs. In versions prior to 4.40, an authenticated S3 principal with permissions scoped to a nested object key can overwrite a different object outside that scope by calling PutObjectAcl on the key it is allowed to access. The handler…
When was the CVE record for CVE-2026-77611 published?
The CVE record for CVE-2026-77611 was published on August 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-77611 actively exploited?
CVE-2026-77611 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77611?
CVE-2026-77611 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77611?
The CVE record for CVE-2026-77611 names the fix: "This issue is fixed in version 4.40."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-77611?

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

Book a Demo →Browse All CVEs