Not necessarily. If you define a public function, like foo(Random, SharedObj, ...), an attacker can exploit this by creating a function, say attack(Random, SharedObj, ...), which calls your function. The attacker can then inspect modifications to the shared object, deciding whether to abort the transaction based on its new state. This is similar to an attack described in the Sui documentation on randomness, but involves a shared state. Even if sensitive fields aren't exposed, an attacker could serialize and parse the object's state. Therefore, they could always 'win' or 'abort' but never 'lose'. If this is acceptable for your use case, you could proceed with using a public function and suppress the warning.