Release 4.2

October 26, 2026

BlazeMeter 4.2 adds SSO group access controls for API Monitoring buckets and makes AI Auto Correlation generally available, so you can limit bucket access and generate JMeter scripts from browser-recorded HAR files. Taurus Cloud version 2.4.556-reduced also resolves seven identified security vulnerabilities.

Limit SSO groups to API Monitoring buckets | API Monitoring

Account admins can now select the public API Monitoring buckets that members of an SSO group can access. Users in a group with selected buckets see only those buckets.

To learn more, see Manage groups.

AI Auto Correlation | Performance testing

AI Auto Correlation is now generally available in BlazeMeter. Upload a HAR file recorded in your browser, and AI detects and correlates dynamic values in the traffic. BlazeMeter generates the extractors and injectors, and the Analysis tab shows each file's correlation health. When you finalize, BlazeMeter creates a JMeter .jmx script. In most cases, all dynamic values are correlated automatically. You can review and manually correlate any values that remain.

To learn more, see Extract values using AI auto correlation.

Fixed and removed vulnerabilities | Taurus Cloud

The current version of Taurus Cloud (2.4.556-reduced) resolved several identified security vulnerabilities by applying the necessary fixes and removing affected components.

The following vulnerabilities are fixed / removed:

• CVE-2026-102276 (high) brace-expansion (npm)

• CVE-2026-102278 (high) brace-expansion (npm)

• CVE-2026-106445 (critical) handlebars (Newman)

• CVE-2026-106446 (critical) handlebars (Newman)

• CVE-2026-93748 (high) http-cache-semantics (npm)

• CVE-2026-97687 (high) urllib3 (Python)

• CVE-2026-97689 (high) urllib3 (Python)

To learn more, see Mitigate Taurus Cloud Vulnerabilities.