<?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>Mssql-Bypass - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/mssql-bypass/</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>Tue, 01 Sep 2026 17:07:20 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/mssql-bypass/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>Memos Refresh Token Revocation Failure</title><link>https://feed.craftedsignal.io/briefs/2026-09-memos-token-revocation/</link><pubDate>Tue, 01 Sep 2026 17:07:20 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-memos-token-revocation/</guid><description>Memos versions 0.26.0 through 0.30.0 fail to invalidate refresh tokens after a password change, enabling persistent unauthorized access via the RefreshToken RPC.</description><content:encoded><![CDATA[<p>Memos versions 0.26.0 through 0.30.0 contain a critical session management vulnerability where the application fails to revoke existing refresh tokens upon a user password change. This security flaw means that if an attacker has already obtained a valid refresh token through previous compromise or session hijacking, they can continue to use that token to authenticate against the RefreshToken RPC endpoint. By repeatedly calling this RPC, the attacker can generate new access tokens and rotate the refresh token indefinitely, effectively bypassing the security intent of a password reset. This persistence mechanism allows an unauthorized actor to maintain account access long after the legitimate user believes they have secured their account by changing their credentials. Defenders should identify any anomalous RefreshToken RPC activity originating from sessions that predate recent password changes.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an attacker to maintain persistent unauthorized access to affected Memos instances, bypassing account password changes. This impact spans all Memos deployments within the 0.26.0 to 0.30.0 range, affecting data integrity and confidentiality for all users within the environment. If compromised, attackers may gain continuous access to sensitive notes and stored information within the Memos platform without needing the current user password.</p>
<h2 id="recommendation">Recommendation</h2>
<ol>
<li>Upgrade all Memos instances to a version later than 0.30.0 immediately to address the session management defect identified in CVE-2026-84203.</li>
<li>Perform a global session revocation if suspicious activity is detected, as simple password resets will not invalidate existing sessions in affected versions.</li>
<li>Audit webserver access logs for anomalous, high-frequency calls to the RefreshToken RPC endpoint that may indicate automated token rotation by an unauthorized actor.</li>
</ol>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>session-management</category><category>vulnerability</category><category>mssql-bypass</category></item></channel></rss>