<?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-02T12:04:02.277583+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-41254</id>
    <title>CVE-2025-41254 — Spring Framework STOMP CSRF Vulnerability</title>
    <updated>2026-10-02T12:04:02.291499+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> VMware Spring Framework</p>
<p>STOMP over WebSocket applications may be vulnerable to a security bypass that allows an attacker to send unauthorized messages.</p>
<p>Affected Spring Products and VersionsSpring Framework:</p>
<p>*  6.2.0 - 6.2.11
  *  6.1.0 - 6.1.23
  *  6.0.x - 6.0.29
  *  5.3.0 - 5.3.45
  *  Older, unsupported versions are also affected.</p>
<p>MitigationUsers of affected versions should upgrade to the corresponding fixed version.</p>
<p>Affected version(s)Fix versionAvailability6.2.x6.2.12OSS6.1.x6.1.24 Commercial https://enterprise.spring.io/ 6.0.xN/A Out of support https://spring.io/projects/spring-framework#support 5.3.x5.3.46 Commercial https://enterprise.spring.io/ No further mitigation steps are necessary.</p>
<p>CreditThis vulnerability was discovered and responsibly reported by Jannis Kaiser.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-41254"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6rw7-vpxm-498p</id>
    <title>GHSA-6rw7-vpxm-498p — qs's arrayLimit bypass in its bracket notation allows DoS via memory exhaustion</title>
    <updated>2026-10-02T12:04:02.291566+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: qs</p>
<p>### Summary</p>
<p>The `arrayLimit` option in qs did not enforce limits for bracket notation (`a[]=1&amp;a[]=2`), only for indexed notation (`a[0]=1`). This is a consistency bug; `arrayLimit` should apply uniformly across all array notations.</p>
<p>**Note:** The default `parameterLimit` of 1000 effectively mitigates the DoS scenario originally described. With default options, bracket notation cannot produce arrays larger than `parameterLimit` regardless of `arrayLimit`, because each `a[]=value` consumes one parameter slot. The severity has been reduced accordingly.</p>
<p>### Details</p>
<p>The `arrayLimit` option only checked limits for indexed notation (`a[0]=1&amp;a[1]=2`) but did not enforce it for bracket notation (`a[]=1&amp;a[]=2`).</p>
<p>**Vulnerable code** (`lib/parse.js:159-162`):
```javascript
if (root === '[]' &amp;&amp; options.parseArrays) {
    obj = utils.combine([], leaf);  // No arrayLimit check
}
```</p>
<p>**Working code** (`lib/parse.js:175`):
```javascript
else if (index &lt;= options.arrayLimit) {  // Limit checked here
    obj = [];
    obj[index] = leaf;
}
```</p>
<p>The bracket notation handler at line 159 uses `utils.combine([], leaf)` without validating against `options.arrayLimit`, while indexed notation at line 175 checks `index &lt;= options.arrayLimit` before creating arrays.</p>
<p>### PoC</p>
<p>```javascript
const qs = require('qs');
const result = qs.parse('a[]=1&amp;a[]=2&amp;a[]=3&amp;a[]=4&amp;a[]=5&amp;a[]=6', { arrayLimit: 5 });
console.log(result.a.length);  // Output: 6 (should be max 5)
```</p>
<p>**Note on parameterLimit interaction…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6rw7-vpxm-498p"/>
  </entry>
</feed>
