<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 13 Nov 2026 01:22:53 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1525 — De multiples vulnérabilités ont été découvertes dans Google Pixel. Certaines d'entre elles permettent à un attaquant de…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1525</link>
      <description>certfr-2026-avi-1525</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1525</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55319</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-55319</link>
      <description>&lt;p&gt;In thread_free of thread.c, there is a possible way to corrupt kernel heap metadata on thread creation failure due to memory corruption. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In thread_free of thread.c, there is a possible way to corrupt kernel heap metadata on thread creation failure due to memory corruption. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-55319</guid>
    </item>
    <item>
      <title>GHSA-gjxw-2gx5-fg55</title>
      <link>https://db.gcve.eu/vuln/ghsa-gjxw-2gx5-fg55</link>
      <description>&lt;p&gt;In thread_free of thread.c, there is a possible way to corrupt kernel heap metadata on thread creation failure due to memory corruption. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In thread_free of thread.c, there is a possible way to corrupt kernel heap metadata on thread creation failure due to memory corruption. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-gjxw-2gx5-fg55</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4457 — Google Android Pixel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4457</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Google Android Pixel ausnutzen, um Code auszuführen, höhere Berechtigungen zu erlangen, Informationen offenzulegen oder die Verfügbarkeit von Gerätefunktionen zu beeinträchtigen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Google Android Pixel ausnutzen, um Code auszuführen, höhere Berechtigungen zu erlangen, Informationen offenzulegen oder die Verfügbarkeit von Gerätefunktionen zu beeinträchtigen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4457</guid>
    </item>
  </channel>
</rss>
