<?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>Home Assistant Core (2026.11.0) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/home-assistant-core-2026.11.0/</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, 09 Nov 2026 01:11:02 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/home-assistant-core-2026.11.0/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>Home Assistant Core: Authentication and session management vulnerabilities</title><link>https://feed.craftedsignal.io/briefs/2026-11-home-assistant-auth/</link><pubDate>Mon, 09 Nov 2026 01:11:02 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-home-assistant-auth/</guid><description>Home Assistant Core 2026.11.0 contains authentication and authorization flaws, including cleartext token storage, non-expiring token classes, and failure to revoke existing sessions upon password reset, facilitating unauthorized long-term access.</description><content:encoded><![CDATA[<p>Home Assistant Core 2026.11.0 exhibits critical security deficiencies regarding authentication lifecycle management. The vendor documentation emphasizes the strength of passwords; however, technical analysis confirms that the internal implementation fails to treat the password as a primary security boundary. Specifically, token secrets are stored in cleartext, certain token classes do not implement expiration logic, and password change events do not trigger the revocation of active sessions or tokens. These issues allow an attacker who has compromised a token to maintain persistent access even after the user changes their account password.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for long-term unauthorized access to the Home Assistant instance, potentially granting control over integrated smart home hardware, including locks, alarm systems, garage doors, and surveillance cameras, as well as access to presence history.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor Home Assistant release notes for security patches addressing session management and token storage.</li>
<li>Audit active long-lived access tokens and sessions within the Home Assistant interface for unauthorized or stale entries.</li>
<li>Implement network-level restrictions to limit exposure of the Home Assistant interface to untrusted networks until updates are applied.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category></item></channel></rss>