<?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>Thu, 19 Nov 2026 18:30:28 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1580 — De multiples vulnérabilités ont été découvertes dans PHP. Certaines d'entre elles permettent à un attaquant de provoque…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1580</link>
      <description>certfr-2026-avi-1580</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1580</guid>
    </item>
    <item>
      <title>fkie_cve-2026-129438</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-129438</link>
      <description>&lt;p&gt;Incorrect RFC 3986 URI serialization for oversized input.&lt;/p&gt;
&lt;p&gt;The Uri\Rfc3986\Uri class does not correctly handle the output-size limit and errors of the uriparser library when converting a URI back to a string. For a URI whose string representation reaches approximately 2 GiB, toString(), toRawString() and other serializing operations can return a truncated or invalid string instead of an error. An application that accepts attacker-controlled URI data of that size, has enough memory to process it and trusts the result may make incorrect validation or routing decisions, and the large allocations can exhaust memory. parse_url() and Uri\WhatWg\Url are not affected.&lt;/p&gt;
&lt;p&gt;This issue affects PHP versions 8.5.* before 8.5.13.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect RFC 3986 URI serialization for oversized input.&lt;/p&gt;
&lt;p&gt;The Uri\Rfc3986\Uri class does not correctly handle the output-size limit and errors of the uriparser library when converting a URI back to a string. For a URI whose string representation reaches approximately 2 GiB, toString(), toRawString() and other serializing operations can return a truncated or invalid string instead of an error. An application that accepts attacker-controlled URI data of that size, has enough memory to process it and trusts the result may make incorrect validation or routing decisions, and the large allocations can exhaust memory. parse_url() and Uri\WhatWg\Url are not affected.&lt;/p&gt;
&lt;p&gt;This issue affects PHP versions 8.5.* before 8.5.13.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-129438</guid>
    </item>
  </channel>
</rss>
