Contributors

Vulnerability Credits

Sort ↑

203 matches for “Michael”.

#Name or organizationAdvisories
91 <a href="https://www.linkedin.com/in/michaelboeynaems/">Michael Boeynaems</a> with <a href="https://www.splynter.be/">Splynter</a>1
92 <a href="https://www.linkedin.com/in/micrictor/">Michael Torres</a>1
93 <a href="https://www.linkedin.com/in/smgoreli">Michael Gorelik</a> with <a href="https://www.morphisec.com/">Morphisec</a>1
94 <a href="https://www.twitter.com/izobashi">Michael DePlante (@izobashi)</a> <a href="https://www.zerodayinitiative.com/">Trend Micro Zero Day Initiative</a>1
95 <a href="https://x.com/mgrafnetter">Michael Grafnetter</a> with <a href="https://specterops.io/">SpecterOps</a>1
96 Andrew Creskey, Andrew Osmond, Dana Keeler, Henri Sivonen, Jed Davis, John Schanck, Jon Coppeard, Justin Link, Michael Froman, Nika Layzell, Noah Lokocz, Randell Jesup, Steve Fink, Tom Schuster and the Mozilla Fuzzing Team1
97 Andy Leiserson, Jan de Mooij, Michael Froman and the Mozilla Fuzzing Team1
98 Discovered by Michael Gentile of Cisco Talos1
99 Estevam Arantes with Microsoft, Michael van Leeuwen with Microsoft, Harry Fokas with Microsoft1
100 F5 acknowledges Thomas Hendrickson and Michael Weber of Praetorian Security, Inc. for bringing this issue to our attention and following the highest standards of coordinated disclosure.1