<?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-27T15:36:43.614108+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-37595</id>
    <title>EUVD-2026-37595</title>
    <updated>2026-10-27T15:36:43.617513+00:00</updated>
    <content>EUVD-2026-37595</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-37595"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2020-6858</id>
    <title>fkie_cve-2020-6858</title>
    <updated>2026-10-27T15:36:43.617554+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Hotels Styx through 1.0.0.beta8 allows HTTP response splitting due to CRLF Injection. This is exploitable if untrusted user input can appear in a response header.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2020-6858"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6v7p-v754-j89v</id>
    <title>GHSA-6v7p-v754-j89v — HTTP Response Splitting in Styx</title>
    <updated>2026-10-27T15:36:43.617593+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: com.hotels.styx:styx-api</p>
<p># Vulnerability
Styx is vulnerable to CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers (&amp;#39;HTTP Response Splitting&amp;#39;).</p>
<p># Vulnerable Component
The vulnerable component is the `com.hotels.styx.api.HttpHeaders.Builder` due to disabling the HTTP Header validation built into Netty in these locations:</p>
<p>https://github.com/HotelsDotCom/styx/blob/e1d578e9b9c38df9cd19c21dc2eb9b949d85b558/components/api/src/main/java/com/hotels/styx/api/HttpHeaders.java#L145</p>
<p>https://github.com/HotelsDotCom/styx/blob/e1d578e9b9c38df9cd19c21dc2eb9b949d85b558/components/api/src/main/java/com/hotels/styx/api/HttpHeaders.java#L145</p>
<p>`new DefaultHttpHeaders(false)` disables the built-in validation in Netty. Either use the default constructor or `new DefaultHttpHeaders(true`  instead.</p>
<p>Additionally, another vulnerable component is the StyxToNettyResponseTranslator due to also disabling the HTTP Header validation built into netty in this location.</p>
<p>https://github.com/HotelsDotCom/styx/blob/8d60e5493e65d0d536afc0b350dcb02d24e0f7a7/components/server/src/main/java/com/hotels/styx/server/netty/connectors/StyxToNettyResponseTranslator.java#L30</p>
<p>`DefaultHttpResponse nettyResponse = new DefaultHttpResponse(version, httpResponseStatus, false); `
`new DefaultHttpResponse(version, httpResponseStatus, false);` disables the built-in validation in Netty. Please use the constructor `new DefaultHttpResponse(version, httpResponseStatus, true);`</p>
<p># Proof of Concept
The following test plugin proves that…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6v7p-v754-j89v"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2020-6858</id>
    <title>gsd-2020-6858</title>
    <updated>2026-10-27T15:36:43.617674+00:00</updated>
    <content>gsd-2020-6858</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2020-6858"/>
  </entry>
</feed>
