<?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-07T02:10:51.472697+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-225673</id>
    <title>EUVD-2026-225673</title>
    <updated>2026-10-07T02:10:51.475297+00:00</updated>
    <content>EUVD-2026-225673</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-225673"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-30221</id>
    <title>fkie_cve-2025-30221</title>
    <updated>2026-10-07T02:10:51.475331+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Pitchfork is a preforking HTTP server for Rack applications. Versions prior to 0.11.0 are vulnerable to HTTP Response Header Injection when used in conjunction with Rack 3. The issue was fixed in Pitchfork release 0.11.0. No known workarounds are available.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-30221"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pfqj-w6r6-g86v</id>
    <title>GHSA-pfqj-w6r6-g86v — Pitchfork HTTP Request/Response Splitting vulnerability</title>
    <updated>2026-10-07T02:10:51.475363+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> RubyGems: pitchfork</p>
<p>### Impact
HTTP Response Header Injection in Pitchfork Versions &lt; 0.11.0 when used in conjunction with Rack 3</p>
<p>### Patches
The issue was fixed in Pitchfork release 0.11.0</p>
<p>### Workarounds
There are no known work arounds. Users must upgrade.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pfqj-w6r6-g86v"/>
  </entry>
</feed>
