<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-11T22:55:46.196985+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-125729</id>
    <title>CVE-2026-125729 — Plack::Middleware::CSP versions before 0.03 for Perl send the Content Security Policy under the wrong header name, so b…</title>
    <updated>2026-11-11T22:55:46.198927+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Plack-Middleware-CSP</p>
<p>Plack::Middleware::CSP versions before 0.03 for Perl send the Content Security Policy under the wrong header name, so browsers never enforce it.</p>
<p>The call method sets the policy in a response header named "content-security-protocol" instead of "Content-Security-Policy". Browsers ignore that header.</p>
<p>Any cross-site scripting flaw in the wrapped application can run scripts the policy was meant to block.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-125729"/>
  </entry>
</feed>
