<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://127.0.0.1:10001</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 15:49:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-56865 — Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog</title>
      <link>https://127.0.0.1:10001/vuln/cve-2026-56865</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go toolchain cmd/go, golang.org/x/mod/sumdb/tlog&lt;/p&gt;
&lt;p&gt;A malicious GOPROXY was previously capable of forging up to two sumdb tiles that allow for a requested module to bypass the GOSUMDB check and persist attacker-controlled module content to a local Go module cache. This attack allows for a malicious GOPROXY to serve malicious module content that cannot be detected by evaluating the transparency log. All tiles are now correctly verified against their parents. In order to determine if you have been affected:   rm -r go.sum go.work.sum vendor/ &amp;amp;&amp;amp; go mod tidy&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go toolchain cmd/go, golang.org/x/mod/sumdb/tlog&lt;/p&gt;
&lt;p&gt;A malicious GOPROXY was previously capable of forging up to two sumdb tiles that allow for a requested module to bypass the GOSUMDB check and persist attacker-controlled module content to a local Go module cache. This attack allows for a malicious GOPROXY to serve malicious module content that cannot be detected by evaluating the transparency log. All tiles are now correctly verified against their parents. In order to determine if you have been affected:   rm -r go.sum go.work.sum vendor/ &amp;amp;&amp;amp; go mod tidy&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cve-2026-56865</guid>
    </item>
    <item>
      <title>USN-8935-1 — golang-1.22 vulnerabilities</title>
      <link>https://127.0.0.1:10001/vuln/usn-8935-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: golang-1.22, Ubuntu:22.04:LTS: golang-1.22, Ubuntu:24.04:LTS: golang-1.22&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;It…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: golang-1.22, Ubuntu:22.04:LTS: golang-1.22, Ubuntu:24.04:LTS: golang-1.22&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;It…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/usn-8935-1</guid>
    </item>
  </channel>
</rss>
