<?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-19T19:57:51.500498+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-2025-68150</id>
    <title>BIT-parse-2025-68150 — Parse Server has Server-Side Request Forgery (SSRF) in Instagram OAuth Adapter</title>
    <updated>2026-10-19T19:57:51.503236+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.2 and 9.1.1, the Instagram authentication adapter allows clients to specify a custom API URL via the `apiURL` parameter in `authData`. This enables SSRF attacks and possibly authentication bypass if malicious endpoints return fake responses to validate unauthorized users. This is fixed in versions 8.6.2 and 9.1.1 by hardcoding the Instagram Graph API URL `https://graph.instagram.com` and ignoring client-provided `apiURL` values. No known workarounds are available.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-parse-2025-68150"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-263886</id>
    <title>EUVD-2026-263886</title>
    <updated>2026-10-19T19:57:51.503284+00:00</updated>
    <content>EUVD-2026-263886</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-263886"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68150</id>
    <title>fkie_cve-2025-68150</title>
    <updated>2026-10-19T19:57:51.503300+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.2 and 9.1.1-alpha.1, the Instagram authentication adapter allows clients to specify a custom API URL via the `apiURL` parameter in `authData`. This enables SSRF attacks and possibly authentication bypass if malicious endpoints return fake responses to validate unauthorized users. This is fixed in versions 8.6.2 and 9.1.1-alpha.1 by hardcoding the Instagram Graph API URL `https://graph.instagram.com` and ignoring client-provided `apiURL` values. No known workarounds are available.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-68150"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3f5f-xgrj-97pf</id>
    <title>GHSA-3f5f-xgrj-97pf — Parse Server is vulnerable to Server-Side Request Forgery (SSRF) via Instagram OAuth Adapter</title>
    <updated>2026-10-19T19:57:51.503324+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 Instagram authentication adapter allows clients to specify a custom API URL via the `apiURL` parameter in `authData`. This enables SSRF attacks and possibly authentication bypass if malicious endpoints return fake responses to validate unauthorized users.</p>
<p>## Patches</p>
<p>Fixed by hardcoding the Instagram Graph API URL `https://graph.instagram.com` and ignoring client-provided `apiURL` values.</p>
<p>## Workarounds</p>
<p>None.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3f5f-xgrj-97pf"/>
  </entry>
</feed>
