<?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-02T18:52:52.757374+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/cnvd-2017-04807</id>
    <title>cnvd-2017-04807</title>
    <updated>2026-10-02T18:52:52.923497+00:00</updated>
    <content>cnvd-2017-04807</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2017-04807"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-73959</id>
    <title>EUVD-2026-73959</title>
    <updated>2026-10-02T18:52:52.923530+00:00</updated>
    <content>EUVD-2026-73959</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-73959"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2017-6507</id>
    <title>fkie_cve-2017-6507</title>
    <updated>2026-10-02T18:52:52.923545+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in AppArmor before 2.12. Incorrect handling of unknown AppArmor profiles in AppArmor init scripts, upstart jobs, and/or systemd unit files allows an attacker to possibly have increased attack surfaces of processes that were intended to be confined by AppArmor. This is due to the common logic to handle 'restart' operations removing AppArmor profiles that aren't found in the typical filesystem locations, such as /etc/apparmor.d/. Userspace projects that manage their own AppArmor profiles in atypical directories, such as what's done by LXD and Docker, are affected by this flaw in the AppArmor init script logic.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2017-6507"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-44p8-9hqx-3rqg</id>
    <title>GHSA-44p8-9hqx-3rqg</title>
    <updated>2026-10-02T18:52:52.923573+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in AppArmor before 2.12. Incorrect handling of unknown AppArmor profiles in AppArmor init scripts, upstart jobs, and/or systemd unit files allows an attacker to possibly have increased attack surfaces of processes that were intended to be confined by AppArmor. This is due to the common logic to handle 'restart' operations removing AppArmor profiles that aren't found in the typical filesystem locations, such as /etc/apparmor.d/. Userspace projects that manage their own AppArmor profiles in atypical directories, such as what's done by LXD and Docker, are affected by this flaw in the AppArmor init script logic.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-44p8-9hqx-3rqg"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2017-6507</id>
    <title>gsd-2017-6507</title>
    <updated>2026-10-02T18:52:52.923593+00:00</updated>
    <content>gsd-2017-6507</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2017-6507"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2024:10627-1</id>
    <title>openSUSE-SU-2024:10627-1 — apache2-mod_apparmor-3.0.3-3.2 on GA media</title>
    <updated>2026-10-02T18:52:52.923605+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>apache2-mod_apparmor-3.0.3-3.2 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2024:10627-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2017:1151-1</id>
    <title>SUSE-SU-2017:1151-1 — Security update for apparmor</title>
    <updated>2026-10-02T18:52:52.923623+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for apparmor</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2017:1151-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-6507</id>
    <title>UBUNTU-CVE-2017-6507</title>
    <updated>2026-10-02T18:52:52.923638+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:14.04:LTS: apparmor, Ubuntu:16.04:LTS: apparmor</p>
<p>An issue was discovered in AppArmor before 2.12. Incorrect handling of unknown AppArmor profiles in AppArmor init scripts, upstart jobs, and/or systemd unit files allows an attacker to possibly have increased attack surfaces of processes that were intended to be confined by AppArmor. This is due to the common logic to handle 'restart' operations removing AppArmor profiles that aren't found in the typical filesystem locations, such as /etc/apparmor.d/. Userspace projects that manage their own AppArmor profiles in atypical directories, such as what's done by LXD and Docker, are affected by this flaw in the AppArmor init script logic.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-6507"/>
  </entry>
</feed>
