Release 4.1

October 11, 2026

BlazeMeter 4.1 lets you test MCP servers in JMeter with familiar test plans and choose JMeter-only or empty Taurus Cloud images to reduce unused components. Taurus Cloud version 2.4.538-reduced also resolves three identified security vulnerabilities.

JMeter-only and empty Taurus Cloud images | Taurus Cloud

These images let your organization reduce the third-party executors bundled in the Taurus Cloud image, which can reduce CVE findings for components you do not use. You can choose a JMeter-only Taurus Cloud image or use the empty image, which loads supported executors when a test starts. The empty image supports only selected executors and may need internet access or a custom executor download URL.

To learn more, see Special Taurus Cloud images for Private Locations.

Fixed and removed vulnerabilities | Taurus Cloud

The current Taurus Cloud version, 2.4.538-reduced, resolves identified security vulnerabilities by applying the required fixes and removing affected components:

• CVE-2026-80212 (high) in resolv (Ruby)

• CVE-2026-84304 (high) in google.golang.org/grpc/internal/transport (k6)

• CVE-2026-84304 (high) in google.golang.org/grpc/mem (k6)

To learn more, see Mitigate Taurus Cloud Vulnerabilities.

MCP server testing in JMeter | Performance testing

The BlazeMeter MCP Plugin for JMeter v1.0 lets you check, automate, and load test MCP servers over STDIO, SSE, or Streamable HTTP. You can use your existing JMeter test plans, assertions, listeners, and thread groups.

To learn more, see the BlazeMeter MCP Plugin for JMeter GitHub repository.