<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VulnFeed.org: Bubka 2FAuth</title><link>https://vulnfeed.org/</link><description>Every disclosure, as it lands. Critical-only feed available.</description><language>en</language><atom:link href="https://vulnfeed.org/feed/product/bubka-2fauth.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-63438: 2FAuth: Reverse Proxy Guard Auto-Creates Users With Admin Promotion From Unauthenticated Header Value</title><link>https://vulnfeed.org/cve/CVE-2026-63438/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-63438/</guid><pubDate>Fri, 06 Nov 2026 21:17:09 +0000</pubDate><description>2FAuth is a web app to manage Two-Factor Authentication (2FA) accounts and generate their security codes. Prior to 8.0.0, when AUTHENTICATION_GUARD=reverse-proxy-guard accepts authentication headers from a client that did not pass through a trusted proxy, RemoteUserProvider::retrieveById() creates an account for an unknown REMOTE_USER, promotes the first created account to administrator, and synchronizes the account email from the configured mail header. An unauthenticated remote client can therefore create an administrator on a fresh instance or impersonate and redirect email for a known account, exposing 2FA secrets and administrative functions. This issue is fixed in version 8.0.0.</description></item><item><title>CVE-2026-63439: 2FAuth: Reverse Proxy Guard Trusts Client-Supplied Headers Without Proxy Verification</title><link>https://vulnfeed.org/cve/CVE-2026-63439/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-63439/</guid><pubDate>Fri, 06 Nov 2026 21:17:09 +0000</pubDate><description>2FAuth is a web app to manage Two-Factor Authentication (2FA) accounts and generate their security codes. Prior to 8.0.0, when AUTHENTICATION_GUARD=reverse-proxy-guard is enabled, ReverseProxyGuard::user() reads the default REMOTE_USER identity header, or a custom identity header selected by the AUTH_PROXY_HEADER_FOR_USER configuration setting, without confirming that the request originated from a configured trusted proxy. A remote client that can reach the application directly can forge the selected identity header and authenticate as an existing user, including an administrator, gaining access to stored 2FA secrets and account or application management functions. This issue is fixed in version 8.0.0.</description></item></channel></rss>
