What's New

Available now: ReadyAPI MCP Server

ReadyAPI MCP Plugin 1.2.0 is now available. From ReadyAPI 4.1.0 onwards, you can now build human and agentic workflows through MCP tools, keeping you in control of your data and workspace. MCP support is opt-in and becomes active only after you install the ReadyAPI MCP Plugin. See MCP Integration to learn more.

Once installed, you can connect Claude, GitHub Copilot, Cursor, and other AI assistants directly to your ReadyAPI workspace and describe what you need in plain English - the MCP Server handles the rest.

  • ReadyAPI 4.3.1 is a patch release. See Version History for changes in previous releases.

  • Security Mitigation for CVE-2026-114938

    A high-severity vulnerability (CVE-2026-114938, CVSS 3.1 score 8.1) affects the OpenJDK Compiler component. The Java runtime in ReadyAPI relies on this component. On x86-64 systems with AVX-512 VBMI, the vulnerability allows remote code execution through memory corruption. Attackers can exploit it only by supplying data to affected APIs, for example, through a web service.

    ReadyAPI 4.3.1 includes the JVM flags that mitigate the vulnerability. Upgrade to ReadyAPI 4.3.1 to apply the mitigation. ReadyAPI 4.4.0 will update the bundled OpenJDK version to fix the vulnerability.

  • Workaround for Earlier Versions

    If you cannot upgrade yet, add one of the following flags to the JVM startup parameters:

    • Disable Base64 intrinsics (recommended): -XX:-UseBASE64Intrinsics

    • Disable AVX-512 execution (x86-64 only): -XX:UseAVX=2

    Both flags can affect application performance. Test them in your environment before a wide rollout.

    To apply the flag, add it to the JVM options file for ReadyAPI, then restart the application:

    • ReadyAPI: ReadyAPI.vmoptions

    • Docker: Set the JAVA_TOOL_OPTIONS environment variable, for example, -e JAVA_TOOL_OPTIONS="-XX:-UseBASE64Intrinsics".

    For help, contact SmartBear Support.

See Also

Publication date: