<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Authentication-Bypass on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/authentication-bypass/</link><description>Recent content in Authentication-Bypass on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 17 Jun 2026 12:55:58 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/authentication-bypass/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenBSD Let Attackers Log In With an Empty Password for 27 Years</title><link>https://hackingpassion.com/openbsd-pap-empty-password-bypass/</link><pubDate>Wed, 17 Jun 2026 12:55:58 +0200</pubDate><guid>https://hackingpassion.com/openbsd-pap-empty-password-bypass/</guid><description>&lt;p>A 27-year-old flaw in &lt;strong>OpenBSD&lt;/strong> let attackers bypass its &lt;strong>PPP&lt;/strong> login with nothing more than an empty username and an empty password.
Hand a vulnerable system a blank name and a blank password, and its own login check treated that as a perfect match and let the connection in.&lt;/p>
&lt;p>The problem sits in the part of OpenBSD that handles &lt;strong>PPP&lt;/strong>, the protocol behind many DSL and fiber connections, usually carried through &lt;strong>PPPoE&lt;/strong>. When two machines set up that kind of link, one side can ask the other to prove who it is. One of the older ways to do that is &lt;strong>PAP&lt;/strong>, the Password Authentication Protocol. One machine sends a name and a password, the other checks them against what it has stored, and if they match the link comes up.&lt;/p></description></item><item><title>BadHost Breaks Into FastAPI and vLLM With a Single Character</title><link>https://hackingpassion.com/badhost-starlette-cve-2026-48710/</link><pubDate>Wed, 27 May 2026 11:32:55 +0200</pubDate><guid>https://hackingpassion.com/badhost-starlette-cve-2026-48710/</guid><description>&lt;p>&lt;strong>BadHost&lt;/strong> is one character in an HTTP header that bypasses authentication on &lt;strong>FastAPI&lt;/strong>, &lt;strong>vLLM&lt;/strong>, &lt;strong>LiteLLM&lt;/strong>, and the &lt;strong>Python MCP SDK&lt;/strong>. They all run on &lt;strong>Starlette&lt;/strong>. Starlette has more than &lt;strong>400,000 dependent projects&lt;/strong> on GitHub. The bug is in Starlette.&lt;/p>
&lt;p>It is tracked as &lt;strong>CVE-2026-48710&lt;/strong>, disclosed on May 22. Starlette is the framework that sits underneath FastAPI and handles the basic plumbing of web requests: routing, middleware, everything that happens before your code runs. Through FastAPI it reaches vLLM, LiteLLM, Text Generation Inference, most OpenAI-compatible proxy servers, MCP servers, agent frameworks, and model management dashboards.&lt;/p></description></item><item><title>cPanel Authentication Bypass CVE-2026-41940 Gave Attackers 64 Days of Root Access</title><link>https://hackingpassion.com/cpanel-authentication-bypass-cve-2026-41940/</link><pubDate>Fri, 01 May 2026 12:49:42 +0200</pubDate><guid>https://hackingpassion.com/cpanel-authentication-bypass-cve-2026-41940/</guid><description>&lt;p>For &lt;strong>64 days&lt;/strong>, attackers had root access to cPanel servers managing over &lt;strong>70 million websites&lt;/strong>, and nobody had to know a single password to get in. A crafted HTTP request was enough, and two-factor authentication made no difference. The company behind the software was told about it two weeks before the patch dropped. Their first response was that nothing was wrong.&lt;/p>
&lt;p>Whoever gets in walks away with &lt;strong>root access to the entire server&lt;/strong> through WHM: the hosted sites, the databases behind them, the email accounts, the certificates, and every credential stored on that machine. With that level of access, someone can read every hosted account, modify files and databases, create permanent backdoor accounts, install malware, steal credentials, and potentially pivot from there into customer networks. Compromising one cPanel server does not mean compromising one website. It means compromising everyone sharing that machine.&lt;/p></description></item><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><item><title>Nginx-UI MCPwn (CVE-2026-33032): Full Server Takeover With One Unauthenticated Request</title><link>https://hackingpassion.com/nginx-ui-mcpwn-cve-2026-33032/</link><pubDate>Thu, 16 Apr 2026 11:11:43 +0200</pubDate><guid>https://hackingpassion.com/nginx-ui-mcpwn-cve-2026-33032/</guid><description>&lt;p>A critical vulnerability in nginx-ui has been actively exploited since March 2026, and it gives any attacker on the network full control over the nginx server behind it without a single credential. &lt;strong>CVE-2026-33032&lt;/strong> scores &lt;strong>9.8 on the CVSS scale&lt;/strong>, sits inside an AI integration that was added to the tool in late 2025, and the entire root cause turned out to be 27 characters of missing code. Recorded Future assigned it a risk score of &lt;strong>94 out of 100&lt;/strong>. The researchers who found it named it &lt;strong>MCPwn&lt;/strong>. 😏&lt;/p></description></item><item><title>CVE-2026-24061. One Command, Root Access: The 11-Year Telnet Bug</title><link>https://hackingpassion.com/telnetd-root-exploit-cve-2026-24061/</link><pubDate>Sat, 24 Jan 2026 14:00:10 +0100</pubDate><guid>https://hackingpassion.com/telnetd-root-exploit-cve-2026-24061/</guid><description>&lt;p>It&amp;rsquo;s 2026 and attackers are still getting root shells via Telnet with a single command that requires no password whatsoever. 😏&lt;/p>
&lt;p>SSH has existed for 31 years. Yet 221,000 telnet servers are still running online, and a bug hidden in the code since 2015 just handed attackers the keys to the kingdom.
&lt;strong>CVE-2026-24061. CVSS 9.8. Critical.&lt;/strong>&lt;/p>
&lt;p>The vulnerability sat in GNU InetUtils telnetd for almost 11 years before anyone noticed. Security researcher Kyu Neushwaistein found it on January 20, 2026, and by January 21, attackers were already exploiting it in the wild.&lt;/p></description></item><item><title>Fortinet Authentication Bypass: A 5-Year-Old Bug Returns While a New One Gets Exploited in 3 Days</title><link>https://hackingpassion.com/fortinet-authentication-bypass-cve-2020-12812-cve-2025-59718/</link><pubDate>Sat, 27 Dec 2025 12:39:00 +0100</pubDate><guid>https://hackingpassion.com/fortinet-authentication-bypass-cve-2020-12812-cve-2025-59718/</guid><description>&lt;p>You buy a firewall to protect your network. In one month, two different authentication bypasses are being actively exploited. One is five years old. One is brand new. 😏&lt;/p>
&lt;p>December 2025. Fortinet has a problem.&lt;/p>
&lt;p>On December 24th, Fortinet published an advisory about CVE-2020-12812. A vulnerability from July 2020. Five years old. Now being actively exploited again. Bypass two-factor authentication by typing the username in different case letters. Instead of &amp;ldquo;admin&amp;rdquo; type &amp;ldquo;Admin&amp;rdquo; or &amp;ldquo;ADMIN&amp;rdquo; and skip 2FA completely.&lt;/p></description></item><item><title>Your Router Just Failed: ASUS &amp; TP-Link Critical Vulnerabilities (CVE-2025-59367)</title><link>https://hackingpassion.com/asus-tplink-authentication-bypass-cve-2025/</link><pubDate>Sun, 16 Nov 2025 13:11:54 +0100</pubDate><guid>https://hackingpassion.com/asus-tplink-authentication-bypass-cve-2025/</guid><description>&lt;p>Your router protects your home network from the internet. Or it&amp;rsquo;s supposed to. Two major vendors just proved it doesn&amp;rsquo;t. 😅&lt;/p>
&lt;p>ASUS: CVE-2025-59367 (CVSS 9.3)
TP-Link: CVE-2025-7850 + CVE-2025-7851 (CVSS 9.3 + 8.7)&lt;/p>
&lt;p>Both disclosed November 2025. Both critical. Both letting attackers walk right in.&lt;/p>
&lt;h2 id="asus-routers-no-password-required">ASUS routers: No password required.&lt;/h2>
&lt;p>The vulnerability affects ASUS DSL-AC51, DSL-N16, and DSL-AC750 routers. Authentication bypass.&lt;/p>
&lt;p>If your router&amp;rsquo;s management interface is exposed to the internet, an attacker can connect remotely without any credentials. No username. No password. Direct admin access.&lt;/p></description></item></channel></rss>