<?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-11-18T02:52:19.759683+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-218859</id>
    <title>EUVD-2026-218859</title>
    <updated>2026-11-18T02:52:19.762373+00:00</updated>
    <content>EUVD-2026-218859</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-218859"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-28109</id>
    <title>fkie_cve-2023-28109</title>
    <updated>2026-11-18T02:52:19.762403+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Play With Docker is a browser-based Docker playground. Versions 0.0.2 and prior are vulnerable to domain hijacking.
Because CORS configuration was not correct, an attacker could use `play-with-docker.com` as an example and set the origin header in an http request as `evil-play-with-docker.com`. The domain would echo in response header, which successfully bypassed the CORS policy and retrieved basic user information. This issue has been fixed in commit ed82247c9ab7990ad76ec2bf1498c2b2830b6f1a. There are no known workarounds.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-28109"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vq59-5x26-h639</id>
    <title>GHSA-vq59-5x26-h639 — Authorization Bypass Through User-Controlled Key play-with-docker</title>
    <updated>2026-11-18T02:52:19.762435+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/play-with-docker/play-with-docker</p>
<p>Impact
Give that CORS configuration was not correct, an attacker could use [play-with-docker.com](http://play-with-docker.com/) as an example, set origin header in http request as  [evil-play-with-docker.com](http://evil-play-with-docker.com/), it will be echo in response header, which successfully bypass the CORS policy and retrieves basic user information.</p>
<p>Patches
It has been fixed in lastest version, Please upgrade to latest version</p>
<p>Workarounds
No, users have to upgrade version.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vq59-5x26-h639"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-28109</id>
    <title>gsd-2023-28109</title>
    <updated>2026-11-18T02:52:19.762463+00:00</updated>
    <content>gsd-2023-28109</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-28109"/>
  </entry>
</feed>
