<?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-06T21:47:55.635352+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-244515</id>
    <title>EUVD-2026-244515</title>
    <updated>2026-10-06T21:47:55.638733+00:00</updated>
    <content>EUVD-2026-244515</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-244515"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-24753</id>
    <title>fkie_cve-2024-24753</title>
    <updated>2026-10-06T21:47:55.638765+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Bref enable serverless PHP on AWS Lambda. When Bref is used in combination with an API Gateway with the v2 format, it does not handle multiple values headers. If PHP generates a response with two headers having the same key but different values only the latest one is kept. If an application relies on multiple headers with the same key being set for security reasons, then Bref would lower the application security. For example, if an application sets multiple `Content-Security-Policy` headers, then Bref would just reflect the latest one. This vulnerability is patched in 2.1.13.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-24753"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-99f9-gv72-fw9r</id>
    <title>GHSA-99f9-gv72-fw9r — Bref Doesn't Support Multiple Value Headers in ApiGatewayFormatV2</title>
    <updated>2026-10-06T21:47:55.638796+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: bref/bref</p>
<p>## Impacted Resources</p>
<p>bref/src/Event/Http/HttpResponse.php:61-90</p>
<p>## Description</p>
<p>When Bref is used in combination with an API Gateway with the v2 format, it does not handle multiple values headers.</p>
<p>Precisely, if PHP generates a response with two headers having the same key but different values only the latest one is kept.</p>
<p>## Impact</p>
<p>If an application relies on multiple headers with the same key being set for security reasons, then Bref would lower the application security.</p>
<p>For example, if an application sets multiple `Content-Security-Policy` headers, then Bref would just reflect the latest one.</p>
<p>## PoC</p>
<p>1. Create a new Bref project.
2. Create an `index.php` file with the following content:
```php
&lt;?php
header("Content-Security-Policy: script-src 'none'", false);
header("Content-Security-Policy: img-src 'self'", false);
?&gt;
&lt;script&gt;alert(document.domain)&lt;/script&gt;
&lt;img src="https://bref.sh/favicon-32x32.png"&gt;
```
3. Use the following `serverless.yml` to deploy the Lambda:
```yaml
service: app</p>
<p>provider:
    name: aws
    region: eu-central-1</p>
<p>plugins:
    - ./vendor/bref/bref</p>
<p>functions:
    api:
        handler: index.php
        description: ''
        runtime: php-81-fpm
        timeout: 28 # in seconds (API Gateway has a timeout of 29 seconds)
        events:
            -   httpApi: '*'</p>
<p># Exclude files from deployment
package:
    patterns:
        - '!node_modules/**'
        - '!tests/**'
```
4. Browse the Lambda URL.
5. Notice that the JavaScript code is executed…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-99f9-gv72-fw9r"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2024-24753</id>
    <title>gsd-2024-24753</title>
    <updated>2026-10-06T21:47:55.638848+00:00</updated>
    <content>gsd-2024-24753</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2024-24753"/>
  </entry>
</feed>
