<?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-10T03:09:33.802050+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-53388</id>
    <title>EUVD-2026-53388</title>
    <updated>2026-10-10T03:09:33.805345+00:00</updated>
    <content>EUVD-2026-53388</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-53388"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2019-10145</id>
    <title>fkie_cve-2019-10145</title>
    <updated>2026-10-10T03:09:33.805377+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` do not have seccomp filtering during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2019-10145"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-x384-w54q-v324</id>
    <title>GHSA-x384-w54q-v324</title>
    <updated>2026-10-10T03:09:33.805408+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` do not have seccomp filtering during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-x384-w54q-v324"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2019-10145</id>
    <title>gsd-2019-10145</title>
    <updated>2026-10-10T03:09:33.805425+00:00</updated>
    <content>gsd-2019-10145</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2019-10145"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-10145</id>
    <title>UBUNTU-CVE-2019-10145</title>
    <updated>2026-10-10T03:09:33.805437+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:18.04:LTS: rkt, Ubuntu:20.04:LTS: rkt</p>
<p>rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` do not have seccomp filtering during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-10145"/>
  </entry>
</feed>
