I would suggest to publish it in your private market place. And on every update, inform project teams to directlly update it from marketplace.
One complelty different solution would be to pulish common module as API. Considering you have 60 application using it, so making it as api is not a bad choice. Could you share some details of what is included in the common module and how do you maintain compatibility between versions?
I would still suggest to use private marketplace what issue are you facing in publishing?
Its an interesting and very practical issue. One approach that works for me is to minimize common jars. Like when you import module, it shows you list of jar, try to choose none or very minimum jar to avoid any possible conflict with latest version of common jar files.
Also try to move any custom code as single repository /project like "Common Modules" for better maintenance and version control.