<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 07:40:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-263629</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-263629</link>
      <description>EUVD-2026-263629</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-263629</guid>
    </item>
    <item>
      <title>fkie_cve-2025-66402</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-66402</link>
      <description>&lt;p&gt;Misskey is an open source, federated social media platform. Starting in version 13.0.0-beta.16 and prior to version 2025.12.0, an actor who does not have permission to view favorites or clips can can export the posts and view the contents. Version 2025.12.0 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Misskey is an open source, federated social media platform. Starting in version 13.0.0-beta.16 and prior to version 2025.12.0, an actor who does not have permission to view favorites or clips can can export the posts and view the contents. Version 2025.12.0 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-66402</guid>
    </item>
    <item>
      <title>GHSA-496g-mmpw-j9x3 — misskey.js's export data contains private post data</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-496g-mmpw-j9x3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: misskey-js&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;After adding private posts (followers, direct) that you do not have permission to view to your favorites or clips, you can export them to view the contents of the private posts.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Create an account (X) for testing and an account (Y) for private posts on the same server.
2. Send appropriate content from Y using &amp;#34;Follow&amp;#34;
3. Send appropriate content to any user using &amp;#34;Nominate&amp;#34; from Y
4. Obtain the URLs for the two posts above using Y&amp;#39;s account.
5. Query the URLs for the two posts using X and add them to your favorites or clips.
6. Export your favorites or clips using X.
7. Check the exported data.&lt;/p&gt;
&lt;p&gt;Note: Verified in v2025.11.1&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This could allow an attacker to view the contents of private posts.
If you have pinned private posts, this could be a real problem, as the ID of the private post can be obtained by viewing the user page on the original server.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: misskey-js&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;After adding private posts (followers, direct) that you do not have permission to view to your favorites or clips, you can export them to view the contents of the private posts.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Create an account (X) for testing and an account (Y) for private posts on the same server.
2. Send appropriate content from Y using &amp;#34;Follow&amp;#34;
3. Send appropriate content to any user using &amp;#34;Nominate&amp;#34; from Y
4. Obtain the URLs for the two posts above using Y&amp;#39;s account.
5. Query the URLs for the two posts using X and add them to your favorites or clips.
6. Export your favorites or clips using X.
7. Check the exported data.&lt;/p&gt;
&lt;p&gt;Note: Verified in v2025.11.1&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This could allow an attacker to view the contents of private posts.
If you have pinned private posts, this could be a real problem, as the ID of the private post can be obtained by viewing the user page on the original server.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-496g-mmpw-j9x3</guid>
    </item>
  </channel>
</rss>
