<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 19:13:01 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-213845</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-213845</link>
      <description>EUVD-2026-213845</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-213845</guid>
    </item>
    <item>
      <title>fkie_cve-2023-30536</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-30536</link>
      <description>&lt;p&gt;slim/psr7 is a PSR-7 implementation for use with Slim 4. In versions prior to 1.6.1 an attacker could sneak in a newline (\n) into both the header names and values. While the specification states that \r\n\r\n is used to terminate the header list, many servers in the wild will also accept \n\n. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests. The issue has been patched in version 1.6.1. There are no known workarounds to this issue. Users are advised to upgrade.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;slim/psr7 is a PSR-7 implementation for use with Slim 4. In versions prior to 1.6.1 an attacker could sneak in a newline (\n) into both the header names and values. While the specification states that \r\n\r\n is used to terminate the header list, many servers in the wild will also accept \n\n. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests. The issue has been patched in version 1.6.1. There are no known workarounds to this issue. Users are advised to upgrade.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-30536</guid>
    </item>
    <item>
      <title>GHSA-q2qj-628g-vhfw — Insecure header validation in slim/psr7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q2qj-628g-vhfw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: slim/psr7&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker could sneak in a newline (`\n`) into both the header names and values. While the specification states that `\r\n\r\n` is used to terminate the header list, many servers in the wild will also accept `\n\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue is patched in 1.6.1, 1.5.1, and 1.4.1.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;In Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().&lt;/p&gt;
&lt;p&gt;### Acknowledgments&lt;/p&gt;
&lt;p&gt;We are very grateful to and thank &amp;lt;a href=&amp;#34;https://gjcampbell.co.uk/&amp;#34;&amp;gt;Graham Campbell&amp;lt;/a&amp;gt; for reporting and working with us on this issue.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw
* Laminas Diactoros: CVE-2023-29530, with advisory GHSA-xv3h-4844-9h36
* https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: slim/psr7&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker could sneak in a newline (`\n`) into both the header names and values. While the specification states that `\r\n\r\n` is used to terminate the header list, many servers in the wild will also accept `\n\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue is patched in 1.6.1, 1.5.1, and 1.4.1.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;In Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().&lt;/p&gt;
&lt;p&gt;### Acknowledgments&lt;/p&gt;
&lt;p&gt;We are very grateful to and thank &amp;lt;a href=&amp;#34;https://gjcampbell.co.uk/&amp;#34;&amp;gt;Graham Campbell&amp;lt;/a&amp;gt; for reporting and working with us on this issue.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw
* Laminas Diactoros: CVE-2023-29530, with advisory GHSA-xv3h-4844-9h36
* https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q2qj-628g-vhfw</guid>
    </item>
    <item>
      <title>gsd-2023-30536</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-30536</link>
      <description>gsd-2023-30536</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-30536</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:0081-1 — Security update for phpMyAdmin</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:0081-1</link>
      <description>&lt;p&gt;Security update for phpMyAdmin&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for phpMyAdmin&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:0081-1</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2023-30536</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-30536</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: php-slim-psr7&lt;/p&gt;
&lt;p&gt;slim/psr7 is a PSR-7 implementation for use with Slim 4. In versions prior to 1.6.1 an attacker could sneak in a newline (\n) into both the header names and values. While the specification states that \r\n\r\n is used to terminate the header list, many servers in the wild will also accept \n\n. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests. The issue has been patched in version 1.6.1. There are no known workarounds to this issue. Users are advised to upgrade.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: php-slim-psr7&lt;/p&gt;
&lt;p&gt;slim/psr7 is a PSR-7 implementation for use with Slim 4. In versions prior to 1.6.1 an attacker could sneak in a newline (\n) into both the header names and values. While the specification states that \r\n\r\n is used to terminate the header list, many servers in the wild will also accept \n\n. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests. The issue has been patched in version 1.6.1. There are no known workarounds to this issue. Users are advised to upgrade.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-30536</guid>
    </item>
  </channel>
</rss>
