<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows-Exploit on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/windows-exploit/</link><description>Recent content in Windows-Exploit on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 28 Apr 2026 10:21:13 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/windows-exploit/index.xml" rel="self" type="application/rss+xml"/><item><title>PhantomRPC: Windows Has a Privilege Escalation Problem Microsoft Won't Fix</title><link>https://hackingpassion.com/phantomrpc-windows-privilege-escalation/</link><pubDate>Tue, 28 Apr 2026 10:21:13 +0200</pubDate><guid>https://hackingpassion.com/phantomrpc-windows-privilege-escalation/</guid><description>&lt;p>Last week at Black Hat Asia in Singapore, a Kaspersky researcher publicly demonstrated &lt;strong>PhantomRPC&lt;/strong>: five separate ways to take any standard Windows service account straight to full &lt;strong>SYSTEM&lt;/strong> access, confirmed working on fully patched Windows Server 2022 and Windows Server 2025. Microsoft already knew. They received the ten-page technical report months ago, called it &lt;strong>moderate severity&lt;/strong>, assigned no CVE, and closed the case. There is no patch.&lt;/p>
&lt;p>&lt;strong>RPC&lt;/strong> stands for Remote Procedure Call, and it is the system that Windows services use to send requests to each other directly in the background. When one service needs something from another, it sends a request through RPC. This happens constantly, hundreds of times per minute, completely invisible to whoever is sitting at the machine.&lt;/p></description></item></channel></rss>