Thank you for your response tbint.
I actually found out that it has something to do with the ADODB reference that we are using to enable us to connect to our databases from within excel.
The exact reference we use is "Microsft ActiveX Data Objects 2.5 Library" and apparently, MS has not yet released a viable patch for this.
I was hoping some of the other users have found a work around for this.