<?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-15T03:25:57.096486+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/cve-2025-61727</id>
    <title>CVE-2025-61727 — Improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509</title>
    <updated>2026-10-15T03:25:57.101381+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go standard library crypto/x509</p>
<p>An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate. For example a constraint that excludes the subdomain test.example.com does not prevent a leaf certificate from claiming the SAN *.example.com.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-61727"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4v7x-pqxf-cx7m</id>
    <title>GHSA-4v7x-pqxf-cx7m — net/http, x/net/http2: close connections when receiving too many headers</title>
    <updated>2026-10-15T03:25:57.101442+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: net/http, Go: golang.org/x/net/http2, Go: golang.org/x/net</p>
<p>An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4v7x-pqxf-cx7m"/>
  </entry>
</feed>
