<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vulnerability Research on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/vulnerability-research/</link><description>Recent content in Vulnerability Research on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 29 Jan 2026 14:18:28 +0100</lastBuildDate><atom:link href="https://hackingpassion.com/tags/vulnerability-research/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Finds 12 OpenSSL Vulnerabilities Including a 27-Year-Old Bug</title><link>https://hackingpassion.com/openssl-12-cves-ai-january-2026/</link><pubDate>Thu, 29 Jan 2026 14:18:28 +0100</pubDate><guid>https://hackingpassion.com/openssl-12-cves-ai-january-2026/</guid><description>&lt;p>An AI just found 12 zero-day vulnerabilities in OpenSSL. All 12. In a single release. One of those bugs is older than OpenSSL itself, sitting in the code since 1998. 🧐&lt;/p>
&lt;p>OpenSSL is the cryptographic library that encrypts roughly two-thirds of all internet traffic. It runs on 95% of IT organizations worldwide. Banks use it. Hospitals use it. Governments use it. Cloud platforms, enterprise applications, operating systems, critical infrastructure. When OpenSSL has a vulnerability, the entire internet has a problem.&lt;/p></description></item><item><title>Pixel 9 Zero-Click Exploit: How a Single Audio Message Can Compromise Your Phone</title><link>https://hackingpassion.com/pixel-9-zero-click-exploit/</link><pubDate>Fri, 16 Jan 2026 10:25:26 +0100</pubDate><guid>https://hackingpassion.com/pixel-9-zero-click-exploit/</guid><description>&lt;p>Someone sends you an audio message. You don&amp;rsquo;t open it, you don&amp;rsquo;t play it, you don&amp;rsquo;t even look at your phone. And you&amp;rsquo;re already hacked. 😏 Google Project Zero just published a three-part series this week showing exactly how they built a working exploit chain for the Pixel 9. No clicks required and no interaction at all. Just receive a message and your phone is compromised.&lt;/p>
&lt;p>&lt;strong>CVE-2025-54957&lt;/strong>&lt;/p>
&lt;p>The vulnerability sits in Dolby&amp;rsquo;s audio decoder, a component that ships on almost every Android phone sold today. Pixel, Samsung, and dozens of other brands all use it. When someone sends you an audio message through SMS or RCS (the default messaging on most Android phones), your phone automatically decodes it for transcription. Before you even see the notification, the malicious code is already running.&lt;/p></description></item><item><title>16-Year-Old's AI Finds Heap Buffer Overflow in FFmpeg EXIF Parser</title><link>https://hackingpassion.com/ffmpeg-heap-overflow-ai-vulnerability-hunter/</link><pubDate>Sat, 03 Jan 2026 14:47:00 +0100</pubDate><guid>https://hackingpassion.com/ffmpeg-heap-overflow-ai-vulnerability-hunter/</guid><description>&lt;p>A 16-year-old built an AI that mass-hunts memory bugs. It found 6 vulnerabilities in FFmpeg in December. One was a heap buffer overflow in the EXIF parser. The code that reads your photo metadata. 😎&lt;/p>
&lt;p>FFmpeg processes media on billions of devices. VLC. Chrome. Firefox. YouTube. Blender. OBS Studio. Plex. Even NASA&amp;rsquo;s Perseverance rover uses FFmpeg.&lt;/p>
&lt;p>The vulnerability: CVE is still pending.&lt;/p>
&lt;p>Important nuance: this bug was in FFmpeg&amp;rsquo;s development branch, not in a public release. It existed for three days before it was caught. Three days. FFmpeg called the researcher &amp;ldquo;a model security researcher&amp;rdquo; for catching it before it shipped.&lt;/p></description></item><item><title>Exploit Eye - CVE and Vulnerability Search Tool for Ethical Hackers</title><link>https://hackingpassion.com/exploit-eye-cve-vulnerability-search-tool/</link><pubDate>Tue, 18 Nov 2025 15:43:40 +0100</pubDate><guid>https://hackingpassion.com/exploit-eye-cve-vulnerability-search-tool/</guid><description>&lt;p>When you&amp;rsquo;re hunting for vulnerabilities, you jump between three different websites. NVD for CVE data. Exploit-DB for working exploits. GitHub for proof-of-concept code.&lt;/p>
&lt;p>That&amp;rsquo;s annoying. You lose time. You miss things.&lt;/p>
&lt;p>I built Exploit Eye to fix that.&lt;/p>
&lt;h2 id="the-problem">The Problem&lt;/h2>
&lt;p>Here&amp;rsquo;s what happens when you research a vulnerability. You find a CVE number somewhere. CVE-2025-1234, for example.&lt;/p>
&lt;p>First, you check the National Vulnerability Database. You find details there. Severity scores. Affected versions. The description tells you what&amp;rsquo;s vulnerable.&lt;/p></description></item></channel></rss>