<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[I confirmed this Edge behavior.]]></title><description><![CDATA[<p>I confirmed this Edge behavior. It stores passwords in cleartext in its memory in ways Chrome and other browsers do not. </p><p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://isc.sans.edu/diary/rss/32954" title="Cleartext Passwords in MS Edge? In 2026? - SANS ISC">
<img src="https://isc.sans.edu/diaryimages/images/dump_mem_from_process.png" class="card-img-top not-responsive" style="max-height: 15rem;" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a href="https://isc.sans.edu/diary/rss/32954">
Cleartext Passwords in MS Edge? In 2026? - SANS ISC
</a>
</h5>
<p class="card-text line-clamp-3">Cleartext Passwords in MS Edge? In 2026?, Author: Rob VandenBrink</p>
</div>
<a href="https://isc.sans.edu/diary/rss/32954" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://isc.sans.edu/favicon-32x32.png" alt="favicon" class="not-responsive overflow-hiddden" style="max-width: 21px; max-height: 21px;" />









<p class="d-inline-block text-truncate mb-0">SANS Internet Storm Center <span class="text-secondary">(isc.sans.edu)</span></p>
</a>
</div></p>

<div class="row mt-3"><img class="img-thumbnail" src="https://media.infosec.exchange/infosec.exchange/media_attachments/files/116/523/730/841/972/463/original/0abba5ad0e2e72db.png" alt="Link Preview Image" /></div>]]></description><link>https://board.circlewithadot.net/topic/f3046d3d-0118-45e8-bfea-736c8490dcb9/i-confirmed-this-edge-behavior.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 04:10:51 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/f3046d3d-0118-45e8-bfea-736c8490dcb9.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 05 May 2026 19:57:09 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to I confirmed this Edge behavior. on Tue, 05 May 2026 23:02:18 GMT]]></title><description><![CDATA[<p><span><a href="/user/mttaggart%40infosec.exchange">@<span>mttaggart</span></a></span> </p><p>A good reason to not submit crash reports.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/SpaceLifeForm/statuses/116524458866076983</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/SpaceLifeForm/statuses/116524458866076983</guid><dc:creator><![CDATA[spacelifeform@infosec.exchange]]></dc:creator><pubDate>Tue, 05 May 2026 23:02:18 GMT</pubDate></item><item><title><![CDATA[Reply to I confirmed this Edge behavior. on Tue, 05 May 2026 22:53:15 GMT]]></title><description><![CDATA[<p><span><a href="/user/infosecstuc%40infosec.exchange">@<span>InfosecStuC</span></a></span> It's a dump of the memory of the browser process, not a password vault.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.space/users/stiiin/statuses/116524423260419645</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.space/users/stiiin/statuses/116524423260419645</guid><dc:creator><![CDATA[stiiin@infosec.space]]></dc:creator><pubDate>Tue, 05 May 2026 22:53:15 GMT</pubDate></item><item><title><![CDATA[Reply to I confirmed this Edge behavior. on Tue, 05 May 2026 22:06:42 GMT]]></title><description><![CDATA[<p><span><a href="/user/mttaggart%40infosec.exchange">@<span>mttaggart</span></a></span> 1995 called, it wants its cleartext browser password file back. I thought edge was based on Chrome? Obviously with the secure bits taken out....sheesh.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/InfosecStuC/statuses/116524240245383625</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/InfosecStuC/statuses/116524240245383625</guid><dc:creator><![CDATA[infosecstuc@infosec.exchange]]></dc:creator><pubDate>Tue, 05 May 2026 22:06:42 GMT</pubDate></item><item><title><![CDATA[Reply to I confirmed this Edge behavior. on Tue, 05 May 2026 20:24:09 GMT]]></title><description><![CDATA[<p><span><a href="/user/mttaggart%40infosec.exchange">@<span>mttaggart</span></a></span> well, that’ll be helpful. This is dumb.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/winterknight1337/statuses/116523836969036691</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/winterknight1337/statuses/116523836969036691</guid><dc:creator><![CDATA[winterknight1337@infosec.exchange]]></dc:creator><pubDate>Tue, 05 May 2026 20:24:09 GMT</pubDate></item><item><title><![CDATA[Reply to I confirmed this Edge behavior. on Tue, 05 May 2026 20:08:25 GMT]]></title><description><![CDATA[<p><span><a href="/user/leon_p_smith%40ioc.exchange" rel="nofollow noopener">@<span>leon_p_smith</span></a></span> As I understand it, that's not exactly how Chrome does it anymore though. The keying material is not stored in the same process as the encrypted passwords. The process containing the key is owned by SYSTEM, even for user-launched browsers. Please keep me honest about that if I'm misremembering.</p><p>It is a limitation that this requires memory dumping, meaning an admin token. Nevertheless, the ease of capturing browser credentials without locating the key is meaningful for attackers.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/mttaggart/statuses/116523773666904387</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/mttaggart/statuses/116523773666904387</guid><dc:creator><![CDATA[mttaggart@infosec.exchange]]></dc:creator><pubDate>Tue, 05 May 2026 20:08:25 GMT</pubDate></item><item><title><![CDATA[Reply to I confirmed this Edge behavior. on Tue, 05 May 2026 20:03:36 GMT]]></title><description><![CDATA[<p><span><a href="/user/mttaggart%40infosec.exchange">@<span>mttaggart</span></a></span> Unless you are unlocking your password manager every time you want to use a password, or you have a dongle-assisted password manager, at least in theory there's not much difference between storing passwords in cleartext in memory or storing encrypted passwords with the unlock key in memory.</p><p>Admittedly keeping passwords encrypted with the key in memory does make confirmation much harder, and exploitation a teensy bit harder, but an highly skilled attacker with access to your password manager's working memory shouldn't find much difference.</p><p>Virtual memory does throw a monkey wrench into this analysis, though.  Virtual memory is one reason I am very interested in dongle-assisted password managers.</p>]]></description><link>https://board.circlewithadot.net/post/https://ioc.exchange/users/leon_p_smith/statuses/116523756217298366</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://ioc.exchange/users/leon_p_smith/statuses/116523756217298366</guid><dc:creator><![CDATA[leon_p_smith@ioc.exchange]]></dc:creator><pubDate>Tue, 05 May 2026 20:03:36 GMT</pubDate></item></channel></rss>