<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cve-2026-109346 - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-109346/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 12 Oct 2026 18:37:28 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-109346/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>UI Misrepresentation Vulnerability in better-auth Device Authorization</title><link>https://feed.craftedsignal.io/briefs/2026-10-better-auth-ui-misrepresentation/</link><pubDate>Mon, 12 Oct 2026 18:37:28 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-better-auth-ui-misrepresentation/</guid><description>The better-auth library's deviceAuthorization plugin fails to display client_id and scope information, enabling attackers to deceive authenticated users into authorizing malicious device codes.</description><content:encoded><![CDATA[<p>The better-auth library, specifically versions 1.3.8-beta.3 through 1.6.x (prior to 1.7.0-rc.3), contains a UI misrepresentation vulnerability within its deviceAuthorization plugin. This flaw stems from the plugin's failure to include the requesting client_id and scope when rendering the device authorization prompt to the user. Consequently, a user is presented with an ambiguous request that lacks the context necessary to verify the legitimacy of the authorization attempt. An attacker can exploit this lack of transparency by initiating a malicious device code flow and tricking an already signed-in user into granting authorization. Once the user approves the request, the attacker can leverage the authorized code to obtain a valid session token via the /device/token endpoint, leading to unauthorized account access.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in unauthorized account access and potential session hijacking. Because the attack relies on misleading an authenticated user, it can bypass standard security expectations regarding authorization prompts. The scope of impact is limited to applications using the vulnerable deviceAuthorization plugin within the identified version range of better-auth.</p>
<h2 id="recommendation">Recommendation</h2>
<ol>
<li>Upgrade the better-auth dependency to version 1.7.0-rc.3 or later to remediate CVE-2026-109346.</li>
<li>Review application logs for anomalous spikes in authorization requests to the /device/code endpoint that do not correlate with legitimate user-driven workflows.</li>
<li>Audit device authorization workflows to ensure all relevant metadata, including client identification and requested scopes, is explicitly displayed to users prior to approval.</li>
</ol>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-application-security</category><category>authentication-bypass</category><category>cve-2026-109346</category></item></channel></rss>