<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: hoholala888</title>
    <description>The latest articles on DEV Community by hoholala888 (@hoholala888).</description>
    <link>https://dev.to/hoholala888</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4148046%2Ffce7f8d0-0459-4927-8cb1-65745def6b29.png</url>
      <title>DEV Community: hoholala888</title>
      <link>https://dev.to/hoholala888</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hoholala888"/>
    <language>en</language>
    <item>
      <title>KDE Vul bug</title>
      <dc:creator>hoholala888</dc:creator>
      <pubDate>Mon, 28 Sep 2026 20:50:01 +0000</pubDate>
      <link>https://dev.to/hoholala888/kde-vul-bug-5eal</link>
      <guid>https://dev.to/hoholala888/kde-vul-bug-5eal</guid>
      <description>&lt;p&gt;After reading the comments, it is hard to believe this is just a Chromium/Chrome bug.  Any application running under user permission could intentionally corrupt fontcache and crash Plamas. This could potentially expose to Local Code Execution.  Someone from Plasma should have  Vul bug opened and fix the issue, so Plasma can handle corrupted font cache file gracefully.&lt;/p&gt;

</description>
      <category>security</category>
    </item>
  </channel>
</rss>
