<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T05:33:52.463881+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-273683</id>
    <title>EUVD-2026-273683</title>
    <updated>2026-10-07T05:33:52.512479+00:00</updated>
    <content>EUVD-2026-273683</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-273683"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27610</id>
    <title>fkie_cve-2026-27610</title>
    <updated>2026-10-07T05:33:52.512523+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Parse Dashboard is a standalone dashboard for managing Parse Server apps. In versions 7.3.0-alpha.42 through 9.0.0-alpha.7, the `ConfigKeyCache` uses the same cache key for both master key and read-only master key when resolving function-typed keys. Under specific timing conditions, a read-only user can receive the cached full master key, or a regular user can receive the cached read-only master key. The fix in version 9.0.0-alpha.8 uses distinct cache keys for master key and read-only master key. As a workaround, avoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-27610"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-jhp4-jvq3-w5xr</id>
    <title>GHSA-jhp4-jvq3-w5xr — Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions</title>
    <updated>2026-10-07T05:33:52.512560+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: parse-dashboard</p>
<p>### Impact</p>
<p>The `ConfigKeyCache` uses the same cache key for both master key and read-only master key when resolving function-typed keys. Under specific timing conditions, a read-only user can receive the cached full master key, or a regular user can receive the cached read-only master key.</p>
<p>### Patches</p>
<p>The fix uses distinct cache keys for master key and read-only master key.</p>
<p>### Workarounds</p>
<p>Avoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration.</p>
<p>### Resources</p>
<p>- GitHub advisory: https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-jhp4-jvq3-w5xr
- Fixed in: https://github.com/parse-community/parse-dashboard/releases/tag/9.0.0-alpha.8</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-jhp4-jvq3-w5xr"/>
  </entry>
</feed>
