<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Go Project — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/go" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by Go Project (go).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/go.png</url>
      <title>Go Project — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:07 GMT</lastBuildDate>
    <item>
      <title>CVE-2026-111943 — Distrust compromised intermediate certificates in crypto/x509</title>
      <link>https://vulnogram.org/CVE-2026-111943</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-111943</guid>
      <description>On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was ad…</description>
      <pubDate>Wed, 21 Oct 2026 00:52:18 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-97032 · 7.5 HIGH 🌩️ — HTTP/2 server crash due to HPACK encoder race in net/http</title>
      <link>https://vulnogram.org/CVE-2026-97032</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-97032</guid>
      <description>HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:54:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94439 · 7.5 HIGH 🌩️ — HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http</title>
      <link>https://vulnogram.org/CVE-2026-94439</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94439</guid>
      <description>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 conv…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78663 · 9.1 CRITICAL 🌩️ — Double flow control refund on HTTP/2 server streams in net/http</title>
      <link>https://vulnogram.org/CVE-2026-78663</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78663</guid>
      <description>The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicio…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78669 · 7.5 HIGH 🌩️ — Excessive CPU consumption from repeated initial window changes in net/http</title>
      <link>https://vulnogram.org/CVE-2026-78669</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78669</guid>
      <description>A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78660 · 7.5 HIGH 🌩️ — HTTP/2 transport accepts malformed framing-related headers in net/http</title>
      <link>https://vulnogram.org/CVE-2026-78660</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78660</guid>
      <description>Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing su…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78667 · 7.5 HIGH 🌩️ — Lack of limit on size of parsed Range headers in net/http</title>
      <link>https://vulnogram.org/CVE-2026-78667</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78667</guid>
      <description>When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94440 · 7.5 HIGH 🌩️ — Memory limit bypass when parsing MIME headers in net/textproto, mime/multipart</title>
      <link>https://vulnogram.org/CVE-2026-94440</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94440</guid>
      <description>Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:58 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-97031 · 7.5 HIGH 🌩️ — Reject malformed ECH outer extension references in crypto/tls</title>
      <link>https://vulnogram.org/CVE-2026-97031</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-97031</guid>
      <description>Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malfo…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:58 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56866 · 7.5 HIGH 🌩️ — HTTP/1 client connection desynchronization after CONNECT rejection in net/http</title>
      <link>https://vulnogram.org/CVE-2026-56866</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56866</guid>
      <description>When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response,…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:58 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56857 · 9.8 CRITICAL 🌩️ — Root.Mkdir(All) can follow junctions out of the root on Windows in os</title>
      <link>https://vulnogram.org/CVE-2026-56857</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56857</guid>
      <description>On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations whe…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:58 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78659 · 7.5 HIGH 🌩️ — HTTP/2 server memory exhaustion due to Trailer headers in net/http</title>
      <link>https://vulnogram.org/CVE-2026-78659</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78659</guid>
      <description>When &quot;Trailer&quot; headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers,…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:58 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94447 · 7.8 HIGH — Checksum database bypass for golang.org/toolchain in cmd/go</title>
      <link>https://vulnogram.org/CVE-2026-94447</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94447</guid>
      <description>Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY the user chooses to use can bypass the intended checksum. We now ensure that golang.org/toolchain…</description>
      <category>High</category>
      <pubDate>Thu, 08 Oct 2026 22:53:57 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94444 · 7.8 HIGH — Checksum bypass for golang.org/fips140 in cmd/go</title>
      <link>https://vulnogram.org/CVE-2026-94444</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94444</guid>
      <description>Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for…</description>
      <category>High</category>
      <pubDate>Thu, 08 Oct 2026 22:53:57 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-97030 · 6.1 MEDIUM 🌩️ — Recognize yield as regexp preceder keyword in html/template</title>
      <link>https://vulnogram.org/CVE-2026-97030</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-97030</guid>
      <description>A trusted template author may have previously written a valid template wherein the use of the &apos;yield&apos; keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:57 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94448 · 6.1 MEDIUM 🌩️ — Reset context tracking on consecutive template expressions in html/template</title>
      <link>https://vulnogram.org/CVE-2026-94448</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94448</guid>
      <description>When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all sub…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 08 Oct 2026 22:53:57 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56851 · 7.5 HIGH 🌩️ — Panic parsing crafted input in x/text/secure/precis in golang.org/x/text</title>
      <link>https://vulnogram.org/CVE-2026-56851</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56851</guid>
      <description>The Nickname profile can panic with an out-of-bounds slice error when transforming crafted input into a short destination buffer.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 07 Oct 2026 17:46:35 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-94445 · 8.8 HIGH 🌩️ — Malicious user input may lead to RCE in golang.org/x/playground</title>
      <link>https://vulnogram.org/CVE-2026-94445</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-94445</guid>
      <description>A malicious txtar could escape the intended execution context and force arbitrary writes to the playground host&apos;s trusted filesystem. Disjointly, one of the three possible paths to invoke go vet on the playground host did not correctly restrict the e…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 25 Sep 2026 16:43:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56855 · 7.5 HIGH 🌩️ — Prevent DoS on deadlocked established channel in golang.org/x/crypto/ssh</title>
      <link>https://vulnogram.org/CVE-2026-56855</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56855</guid>
      <description>Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other mess…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 02 Sep 2026 19:37:05 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-78662 · 7.5 HIGH 🌩️ — Prevent DoS on deadlocked undecided channel in golang.org/x/crypto/ssh</title>
      <link>https://vulnogram.org/CVE-2026-78662</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-78662</guid>
      <description>Previously, a channel registered in the mux&apos;s chanList is not usable until it is established. A malicious peer was able flood the channel&apos;s incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a chann…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 02 Sep 2026 19:37:05 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56854 · 7.5 HIGH 🌩️ — Source-address critical option not enforced for non-public-key auth callbacks in golang.org/x/crypto/ssh</title>
      <link>https://vulnogram.org/CVE-2026-56854</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56854</guid>
      <description>The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. Permissions returned by the PasswordCa…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 28 Aug 2026 15:14:26 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-46603 · 7.5 HIGH 🌩️ — Excessive memory allocation during VP8L decoding in golang.org/x/image</title>
      <link>https://vulnogram.org/CVE-2026-46603</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-46603</guid>
      <description>VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 14 Aug 2026 16:38:16 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56860 · 5.9 MEDIUM 🌩️ — Avoid quadratic complexity in resolvePath in net/url</title>
      <link>https://vulnogram.org/CVE-2026-56860</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56860</guid>
      <description>Previously, resolving relative paths containing parent directory (&apos;..&apos;) segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 13 Aug 2026 21:58:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56864 · 7.5 HIGH 🌩️ — Ignore unrelated, unauthenticated hashes in Lookup in golang.org/x/mod/sumdb</title>
      <link>https://vulnogram.org/CVE-2026-56864</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56864</guid>
      <description>A malicious GOSUMDB was capable of serving arbitrary module content not contained within the transparency log. This attack allows for a coordinating GOPROXY and GOSUMDB to serve a client malicious module content that cannot be detected by evaluating…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 13 Aug 2026 21:58:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56865 · 8.4 HIGH — Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog</title>
      <link>https://vulnogram.org/CVE-2026-56865</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56865</guid>
      <description>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 GO…</description>
      <category>High</category>
      <pubDate>Thu, 13 Aug 2026 21:58:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56858 · 6.1 MEDIUM 🌩️ — Fix Javascript regexp context tracking in html/template</title>
      <link>https://vulnogram.org/CVE-2026-56858</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56858</guid>
      <description>Previously, pathological inputs could close an unescaped &apos;/&apos; early, allowing for attack-controlled data to inject arbitrary content, potentially leading to XSS.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 13 Aug 2026 21:58:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56862 · 7.5 HIGH 🌩️ — Limit handshake messages we are willing to accept post-handshake in crypto/tls</title>
      <link>https://vulnogram.org/CVE-2026-56862</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56862</guid>
      <description>Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing k…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 13 Aug 2026 21:58:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56853 · 7.5 HIGH 🌩️ — Apply ReadHeaderTimeout when doing unencrypted HTTP/2 check in net/http</title>
      <link>https://vulnogram.org/CVE-2026-56853</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56853</guid>
      <description>When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 13 Aug 2026 21:58:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56859 · 7.5 HIGH 🌩️ — Add recursion depth guard during decode in encoding/xml</title>
      <link>https://vulnogram.org/CVE-2026-56859</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56859</guid>
      <description>Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 13 Aug 2026 21:58:52 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-33818 · 7.5 HIGH 🌩️ — Enforce maximum recursion depth in encoding/asn1</title>
      <link>https://vulnogram.org/CVE-2026-33818</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-33818</guid>
      <description>Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 13 Aug 2026 21:58:52 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-56852 · 7.5 HIGH 🌩️ — Infinite loop on invalid input in golang.org/x/text</title>
      <link>https://vulnogram.org/CVE-2026-56852</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-56852</guid>
      <description>A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Tue, 21 Jul 2026 19:18:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-46600 · 7.5 HIGH 🌩️ — Parsing an invalid SVCB or HTTPS RR can panic in golang.org/x/net/dns/dnsmessage</title>
      <link>https://vulnogram.org/CVE-2026-46600</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-46600</guid>
      <description>Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Tue, 21 Jul 2026 19:18:59 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-42505 · 5.3 MEDIUM 🌩️ — Invoking Encrypted Client Hello privacy leak in crypto/tls</title>
      <link>https://vulnogram.org/CVE-2026-42505</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-42505</guid>
      <description>Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 08 Jul 2026 15:46:33 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-39822 · 7.8 HIGH — Root escape via symlink plus trailing slash in os</title>
      <link>https://vulnogram.org/CVE-2026-39822</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-39822</guid>
      <description>On Unix systems, opening a file in an os.Root improperly follows symlinks to locations outside of the Root when the final path component of the a path is a symbolic link and the path ends in /. For example, &apos;root.Open(&quot;symlink/&quot;)&apos; will open &quot;symlink&quot;…</description>
      <category>High</category>
      <pubDate>Wed, 08 Jul 2026 15:46:27 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-46604 · 7.5 HIGH 🌩️ — Panic decoding image with out-of-bounds strip offset in x/image/tiff in golang.org/x/image</title>
      <link>https://vulnogram.org/CVE-2026-46604</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-46604</guid>
      <description>The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 26 Jun 2026 20:22:46 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-46602 · 7.5 HIGH 🌩️ — Lack of limit on tile sizes in x/image/tiff in golang.org/x/image</title>
      <link>https://vulnogram.org/CVE-2026-46602</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-46602</guid>
      <description>The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:47:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-46601 · 7.5 HIGH 🌩️ — Panic on VP8 alpha channel size mismatch in x/image/webp in golang.org/x/image</title>
      <link>https://vulnogram.org/CVE-2026-46601</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-46601</guid>
      <description>The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Thu, 25 Jun 2026 19:47:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-42507 · 5.3 MEDIUM 🌩️ — Arbitrary inputs are included in errors without any escaping in net/textproto</title>
      <link>https://vulnogram.org/CVE-2026-42507</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-42507</guid>
      <description>When returning errors, functions in the net/textproto package would include its input as part of the error. This might allow an attacker to inject misleading content to errors that are printed or logged.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Tue, 02 Jun 2026 22:01:37 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-42504 · 7.5 HIGH 🌩️ — Quadratic complexity in WordDecoder.DecodeHeader in mime</title>
      <link>https://vulnogram.org/CVE-2026-42504</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-42504</guid>
      <description>Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Tue, 02 Jun 2026 22:01:37 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-27145 · 7.5 HIGH 🌩️ — Inefficient candidate hostname parsing in crypto/x509</title>
      <link>https://vulnogram.org/CVE-2026-27145</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-27145</guid>
      <description>(*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, &quot;.&quot;) to execute repeatedly on the same input hostname. With a large DNS SAN list, verif…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Tue, 02 Jun 2026 22:01:36 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-46599 · 7.5 HIGH 🌩️ — Excessive resource consumption in PackBits decompression in golang.org/x/image/tiff</title>
      <link>https://vulnogram.org/CVE-2026-46599</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-46599</guid>
      <description>The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of co…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 29 May 2026 19:35:33 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-42500 · 5.3 MEDIUM 🌩️ — Panic when reading out of bound palette index in golang.org/x/image/bmp</title>
      <link>https://vulnogram.org/CVE-2026-42500</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-42500</guid>
      <description>Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 29 May 2026 18:36:28 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-39824 · 3.3 LOW — Invoking  integer overflow in NewNTUnicodeString in golang.org/x/sys/windows</title>
      <link>https://vulnogram.org/CVE-2026-39824</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-39824</guid>
      <description>NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error.</description>
      <category>Low</category>
      <pubDate>Fri, 22 May 2026 19:39:47 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-27136 · 6.1 MEDIUM 🌩️ — Invoking  duplicate attributes can cause XSS in golang.org/x/net/html</title>
      <link>https://vulnogram.org/CVE-2026-27136</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-27136</guid>
      <description>Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 22 May 2026 15:01:22 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-25681 · 6.1 MEDIUM 🌩️ — Invoking  incorrect handling of character references in DOCTYPE nodes in golang.org/x/net/html</title>
      <link>https://vulnogram.org/CVE-2026-25681</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-25681</guid>
      <description>Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 22 May 2026 15:01:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-25680 · 6.5 MEDIUM 🌩️ — Invoking denial of service when parsing arbitrary HTML in golang.org/x/net/html</title>
      <link>https://vulnogram.org/CVE-2026-25680</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-25680</guid>
      <description>Parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 22 May 2026 15:01:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-42502 · 6.1 MEDIUM 🌩️ — Invoking  incorrect handling of HTML elements in foreign content in golang.org/x/net/html</title>
      <link>https://vulnogram.org/CVE-2026-42502</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-42502</guid>
      <description>Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 22 May 2026 15:01:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-39821 · 9.6 CRITICAL — Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna</title>
      <link>https://vulnogram.org/CVE-2026-39821</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-39821</guid>
      <description>The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode(&quot;xn--example-.com&quot;) incorrectly returns the name &quot;example.com&quot; rather than an error. This behavior can lead to p…</description>
      <category>Critical</category>
      <pubDate>Fri, 22 May 2026 15:01:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-42506 · 6.1 MEDIUM 🌩️ — Invoking  incorrect handling of namespaced elements in foreign content in golang.org/x/net/html</title>
      <link>https://vulnogram.org/CVE-2026-42506</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-42506</guid>
      <description>Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 22 May 2026 15:01:21 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-46598 · 5.3 MEDIUM 🌩️ — Invoking  pathological inputs can lead to client panic in golang.org/x/crypto/ssh/agent</title>
      <link>https://vulnogram.org/CVE-2026-46598</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-46598</guid>
      <description>For certain crafted inputs, a &apos;ed25519.PrivateKey&apos; was created by casting malformed wire bytes, leading to a panic when used.</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 22 May 2026 02:31:27 GMT</pubDate>
    </item>
  </channel>
</rss>
