# Update on public sharing of Access Grants

**URL:** <https://forum.storj.io/t/update-on-public-sharing-of-access-grants/24051>\
**Category:** DCS\
**Created:** [October 17, 2023, 4:41pm UTC](https://forum.storj.io/t/update-on-public-sharing-of-access-grants/24051 "2023-10-17T16:41:16Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Yukon](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/yukon/32/1139_2.png) [@Yukon](https://forum.storj.io/u/Yukon)\
**Post date:** [October 20, 2023, 5:40pm UTC](https://forum.storj.io/t/update-on-public-sharing-of-access-grants/24051/9 "2023-10-20T17:40:24Z")

</div>

Thanks.

Reading the jtolio answer in [Sharing ML Dataset via read-only access grant - #3 by jtolio](https://forum.storj.io/t/sharing-ml-dataset-via-read-only-access-grant/14833/3), a question come to my mind: in case the shared Access Grant is **read** and **list** only, is the described flaw still valid? Or this malicious behaviour is only possible if the Access Grant has **write** permissions?

Thanks!

---

_[View the full topic](https://forum.storj.io/t/update-on-public-sharing-of-access-grants/24051)._