<?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>Mon, 12 Oct 2026 21:58:26 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-266846</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-266846</link>
      <description>EUVD-2026-266846</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-266846</guid>
    </item>
    <item>
      <title>fkie_cve-2026-24772</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-24772</link>
      <description>&lt;p&gt;OpenProject is an open-source, web-based project management software. To enable the real time collaboration on documents, OpenProject 17.0 introduced a synchronization server. The OpenPrioject backend generates an authentication token that is currently valid for 24 hours, encrypts it with a shared secret only known to the synchronization server. The frontend hands this encrypted token and the backend URL over to the synchronization server to check user&amp;#39;s ability to work on the document and perform intermittent saves while editing. The synchronization server does not properly validate the backend URL and sends a request with the decrypted authentication token to the endpoint that was given to the server. An attacker could use this vulnerability to decrypt a token that he intercepted by other means to gain an access token to interact with OpenProject on the victim&amp;#39;s behalf. This vulnerability was introduced with OpenProject 17.0.0 and was fixed in 17.0.2. As a workaround, disable the collaboration feature via Settings -&amp;gt; Documents -&amp;gt; Real time collaboration -&amp;gt; Disable. Additionally the `hocuspocus` container should also be disabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenProject is an open-source, web-based project management software. To enable the real time collaboration on documents, OpenProject 17.0 introduced a synchronization server. The OpenPrioject backend generates an authentication token that is currently valid for 24 hours, encrypts it with a shared secret only known to the synchronization server. The frontend hands this encrypted token and the backend URL over to the synchronization server to check user&amp;#39;s ability to work on the document and perform intermittent saves while editing. The synchronization server does not properly validate the backend URL and sends a request with the decrypted authentication token to the endpoint that was given to the server. An attacker could use this vulnerability to decrypt a token that he intercepted by other means to gain an access token to interact with OpenProject on the victim&amp;#39;s behalf. This vulnerability was introduced with OpenProject 17.0.0 and was fixed in 17.0.2. As a workaround, disable the collaboration feature via Settings -&amp;gt; Documents -&amp;gt; Real time collaboration -&amp;gt; Disable. Additionally the `hocuspocus` container should also be disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-24772</guid>
    </item>
  </channel>
</rss>
