<?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://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T15:58:16.272108+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" 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://127.0.0.1:10001/vuln/cve-2026-94439</id>
    <title>CVE-2026-94439 — HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http</title>
    <updated>2026-11-21T15:58:16.274007+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go standard library net/http</p>
<p>When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2026-94439"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-8935-1</id>
    <title>USN-8935-1 — golang-1.22 vulnerabilities</title>
    <updated>2026-11-21T15:58:16.274078+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:20.04:LTS: golang-1.22, Ubuntu:22.04:LTS: golang-1.22, Ubuntu:24.04:LTS: golang-1.22</p>
<p>It was discovered that Go did not enforce a maximum recursion depth when
parsing deeply nested ASN.1 structures. An attacker could possibly use this
issue to cause Go to crash, resulting in a denial of service.
(CVE-2026-33818)</p>
<p>It was discovered that Go incorrectly reset the depth counter when decoding
XML elements. An attacker could possibly use this issue to cause Go to
crash via deeply nested XML input, resulting in a denial of service.
(CVE-2026-56859)</p>
<p>It was discovered that Go incorrectly handled TLS KeyUpdate messages after
the handshake was completed. A remote attacker could possibly use this
issue to cause Go to use excessive resources, leading to a denial of
service. (CVE-2026-56862)</p>
<p>It was discovered that Go did not correctly verify checksum database tiles
against their parents. An attacker in control of a malicious module proxy
could possibly use this issue to bypass checksum database verification and
serve malicious module content. (CVE-2026-56865)</p>
<p>It was discovered that the Go HTTP client incorrectly returned connections
to the idle pool after a rejected HTTP/1 CONNECT request with a request
body. A remote attacker could possibly use this issue to perform HTTP
response poisoning attacks against reverse proxies. (CVE-2026-56866)</p>
<p>It was discovered that the Go HTTP/2 server did not apply header limits to
Trailer headers. A remote attacker could possibly use this issue to cause
Go to use excessive resources, leading to a denial of service.
(CVE-2026-78659)</p>
<p>It…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-8935-1"/>
  </entry>
</feed>
