<?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-16T14:14:17.201616+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/bit-parse-2026-30229</id>
    <title>BIT-parse-2026-30229 — Parse Server: Endpoint `/loginAs` allows `readOnlyMasterKey` to gain full read and write access as any user</title>
    <updated>2026-10-16T14:14:17.249522+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: parse</p>
<p>Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.6 and 9.5.0, the readOnlyMasterKey can call POST /loginAs to obtain a valid session token for any user. This allows a read-only credential to impersonate arbitrary users with full read and write access to their data. Any Parse Server deployment that uses readOnlyMasterKey is affected. This issue has been patched in versions 8.6.6 and 9.5.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-parse-2026-30229"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-275099</id>
    <title>EUVD-2026-275099</title>
    <updated>2026-10-16T14:14:17.249577+00:00</updated>
    <content>EUVD-2026-275099</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-275099"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-30229</id>
    <title>fkie_cve-2026-30229</title>
    <updated>2026-10-16T14:14:17.249593+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.6 and 9.5.0-alpha.4, the readOnlyMasterKey can call POST /loginAs to obtain a valid session token for any user. This allows a read-only credential to impersonate arbitrary users with full read and write access to their data. Any Parse Server deployment that uses readOnlyMasterKey is affected. This issue has been patched in versions 8.6.6 and 9.5.0-alpha.4.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-30229"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-79wj-8rqv-jvp5</id>
    <title>GHSA-79wj-8rqv-jvp5 — parse-server's endpoint `/loginAs` allows `readOnlyMasterKey` to gain full read and write access as any user</title>
    <updated>2026-10-16T14:14:17.249618+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: parse-server</p>
<p>### Impact</p>
<p>The `readOnlyMasterKey` can call `POST /loginAs` to obtain a valid session token for any user. This allows a read-only credential to impersonate arbitrary users with full read and write access to their data. Any Parse Server deployment that uses `readOnlyMasterKey` is affected.</p>
<p>### Patches</p>
<p>The fix adds a check to the `/logInAs` handler.</p>
<p>### Workarounds</p>
<p>There is no workaround other than not using `readOnlyMasterKey`.</p>
<p>### References</p>
<p>- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-79wj-8rqv-jvp5
- Fix for Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.4
- Fix for Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.6</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-79wj-8rqv-jvp5"/>
  </entry>
</feed>
