<?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-07T14:29:51.510056+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-30204</id>
    <title>CVE-2025-30204 — jwt-go allows excessive memory allocation during header parsing</title>
    <updated>2026-10-07T14:29:51.528538+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> golang-jwt jwt</p>
<p>golang-jwt is a Go implementation of JSON Web Tokens. Starting in version 3.2.0 and prior to versions 5.2.2 and 4.5.2, the function parse.ParseUnverified splits (via a call to strings.Split) its argument (which is untrusted data) on periods. As a result, in the face of a malicious request whose Authorization header consists of Bearer  followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. This issue is fixed in 5.2.2 and 4.5.2.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-30204"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mh63-6h87-95cp</id>
    <title>GHSA-mh63-6h87-95cp — jwt-go allows excessive memory allocation during header parsing</title>
    <updated>2026-10-07T14:29:51.528596+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/golang-jwt/jwt/v5, Go: github.com/golang-jwt/jwt/v4, Go: github.com/golang-jwt/jwt</p>
<p>### Summary</p>
<p>Function [`parse.ParseUnverified`](https://github.com/golang-jwt/jwt/blob/c035977d9e11c351f4c05dfeae193923cbab49ee/parser.go#L138-L139) currently splits (via a call to [strings.Split](https://pkg.go.dev/strings#Split)) its argument (which is untrusted data) on periods.</p>
<p>As a result, in the face of a malicious request whose _Authorization_ header consists of `Bearer ` followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. Relevant weakness: [CWE-405: Asymmetric Resource Consumption (Amplification)](https://cwe.mitre.org/data/definitions/405.html)</p>
<p>### Details</p>
<p>See [`parse.ParseUnverified`](https://github.com/golang-jwt/jwt/blob/c035977d9e11c351f4c05dfeae193923cbab49ee/parser.go#L138-L139)</p>
<p>### Impact</p>
<p>Excessive memory allocation</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mh63-6h87-95cp"/>
  </entry>
</feed>
