<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deserialization on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/deserialization/</link><description>Recent content in Deserialization on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 25 Apr 2026 11:10:39 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/deserialization/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Bing CVSS 10.0: CVE-2026-33819 Remote Code Execution Explained</title><link>https://hackingpassion.com/bing-rce-cve-2026-33819/</link><pubDate>Sat, 25 Apr 2026 11:10:39 +0200</pubDate><guid>https://hackingpassion.com/bing-rce-cve-2026-33819/</guid><description>&lt;p>&lt;strong>Bing had a CVSS 10.0 vulnerability&lt;/strong> in its backend infrastructure, the same infrastructure that powers Edge, Windows Search, and Copilot integrations across Microsoft&amp;rsquo;s ecosystem. Microsoft fixed it on March 10 without saying a word publicly. The CVE showed up six weeks later, on April 23. Nobody outside the company knew this had been sitting in the infrastructure that hundreds of millions of people use every day.&lt;/p>
&lt;p>The CVE number is &lt;strong>2026-33819&lt;/strong>. The vulnerability class is &lt;strong>deserialization of untrusted data&lt;/strong>, and the idea behind it is simpler than it sounds.&lt;/p></description></item></channel></rss>