<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CVE 2026 40372 on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/cve-2026-40372/</link><description>Recent content in CVE 2026 40372 on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 22 Apr 2026 13:17:50 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/cve-2026-40372/index.xml" rel="self" type="application/rss+xml"/><item><title>How CVE 2026 40372 Breaks ASP.NET Core Authentication</title><link>https://hackingpassion.com/aspnet-core-dataprotection-hmac-cve-2026-40372/</link><pubDate>Wed, 22 Apr 2026 13:17:50 +0200</pubDate><guid>https://hackingpassion.com/aspnet-core-dataprotection-hmac-cve-2026-40372/</guid><description>&lt;p>The security fix Microsoft shipped in 2010 to stop attackers from decrypting ASP.NET traffic and forging authentication cookies just got quietly broken by a regression in .NET 10. &lt;code>Microsoft.AspNetCore.DataProtection 10.0.6&lt;/code> shipped on &lt;strong>April 14, 2026&lt;/strong>. One week later, on &lt;strong>April 21&lt;/strong>, Microsoft released &lt;strong>10.0.7&lt;/strong> out of band with the fix. In those seven days, any Linux or macOS server running 10.0.6 may have handed out real, signed login tokens to attackers, and &lt;strong>those tokens still work after the patch unless the key ring is rotated.&lt;/strong> 😏&lt;/p></description></item></channel></rss>