<?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://db.gcve.eu</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>Thu, 29 Oct 2026 00:25:14 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-117468</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-117468</link>
      <description>&lt;p&gt;Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code. An authenticated remote attacker holding a restricted API key-derived session could claim an attacker-controlled device code and obtain a full read-write session valid for up to 365 days, bypassing the original token&amp;#39;s scope and lifetime restrictions. This did not bypass two-factor authentication or directly disclose plaintext secrets.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code. An authenticated remote attacker holding a restricted API key-derived session could claim an attacker-controlled device code and obtain a full read-write session valid for up to 365 days, bypassing the original token&amp;#39;s scope and lifetime restrictions. This did not bypass two-factor authentication or directly disclose plaintext secrets.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-117468</guid>
    </item>
    <item>
      <title>GHSA-897w-6p63-7p9g</title>
      <link>https://db.gcve.eu/vuln/ghsa-897w-6p63-7p9g</link>
      <description>&lt;p&gt;Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code. An authenticated remote attacker holding a restricted API key-derived session could claim an attacker-controlled device code and obtain a full read-write session valid for up to 365 days, bypassing the original token&amp;#39;s scope and lifetime restrictions. This did not bypass two-factor authentication or directly disclose plaintext secrets.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code. An authenticated remote attacker holding a restricted API key-derived session could claim an attacker-controlled device code and obtain a full read-write session valid for up to 365 days, bypassing the original token&amp;#39;s scope and lifetime restrictions. This did not bypass two-factor authentication or directly disclose plaintext secrets.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-897w-6p63-7p9g</guid>
    </item>
  </channel>
</rss>
