<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 16:23:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-61727 — Improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-61727</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go standard library crypto/x509&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go standard library crypto/x509&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-61727</guid>
    </item>
    <item>
      <title>GHSA-c6gw-w398-hv78 — DoS in go-jose Parsing</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c6gw-w398-hv78</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/go-jose/go-jose/v4, Go: github.com/go-jose/go-jose/v3, Go: github.com/go-jose/go-jose&lt;/p&gt;
&lt;p&gt;### Impact
When parsing compact JWS or JWE input, go-jose could use excessive memory. The code used strings.Split(token, &amp;#34;.&amp;#34;) to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of &amp;#39;.&amp;#39; characters.  An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service.&lt;/p&gt;
&lt;p&gt;### Patches
Version 4.0.5 fixes this issue&lt;/p&gt;
&lt;p&gt;### Workarounds
Applications could pre-validate payloads passed to go-jose do not contain an excessive number of &amp;#39;.&amp;#39; characters.&lt;/p&gt;
&lt;p&gt;### References
This is the same sort of issue as in the golang.org/x/oauth2/jws package as CVE-2025-22868 and Go issue https://go.dev/issue/71490.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/go-jose/go-jose/v4, Go: github.com/go-jose/go-jose/v3, Go: github.com/go-jose/go-jose&lt;/p&gt;
&lt;p&gt;### Impact
When parsing compact JWS or JWE input, go-jose could use excessive memory. The code used strings.Split(token, &amp;#34;.&amp;#34;) to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of &amp;#39;.&amp;#39; characters.  An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service.&lt;/p&gt;
&lt;p&gt;### Patches
Version 4.0.5 fixes this issue&lt;/p&gt;
&lt;p&gt;### Workarounds
Applications could pre-validate payloads passed to go-jose do not contain an excessive number of &amp;#39;.&amp;#39; characters.&lt;/p&gt;
&lt;p&gt;### References
This is the same sort of issue as in the golang.org/x/oauth2/jws package as CVE-2025-22868 and Go issue https://go.dev/issue/71490.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c6gw-w398-hv78</guid>
    </item>
  </channel>
</rss>
