Version: Wowza Streaming Engine™ 4.10.0+14 build 20260507202104 released May 13, 2026.
Java support: Wowza Streaming Engine 4.10.0 is compiled using Java 17 (OpenJDK Java SE JRE 17.0.12) but can be used with Java versions 17 or 21. For more details, see Java version information.
Contents
Detailed list of changes in Wowza Streaming Engine 4.10.
Known issues with Wowza Streaming Engine 4.10.0
New features and functionality in Wowza Streaming Engine 4.10.0
Wowza Streaming Engine 4.10.0 delivers significant advancements in GPU-accelerated transcoding, streaming reliability, and security while optimizing performance across the platform. This release marks the graduation of the MainConcept Easy Video API (EVA) from beta to production-ready status, introduces critical security updates, and streamlines the platform by deprecating legacy streaming formats no longer in active use.
MainConcept Easy Video API (EVA) reaches general availability
The MainConcept Easy Video API (EVA) has successfully transitioned from beta to general availability in Wowza Streaming Engine 4.10.0, bringing production-ready GPU-accelerated transcoding to enterprise streaming workflows. Originally introduced in version 4.9.7 as a foundation for next-generation NVIDIA GPU transcoding, EVA has undergone extensive testing, optimization, and refinement based on real-world deployment feedback.
For detailed configuration and deployment guidance, see Set up and run Transcoder in Wowza Streaming Engine.
Enhanced performance and optimization across core streaming components
Wowza Streaming Engine 4.10.0 includes multiple performance enhancements to improve streaming reliability, throughput, and resource efficiency. The HTTP-origin application infrastructure has been optimized to improve responsiveness for both live and VOD playback. The engine's ability to handle complex video content has been enhanced. These improvements directly benefit customers running high-volume streaming operations, as they reduce server load and improve transcoder session startup reliability.
Improved reliability and error handling for transcoding workflows
Wowza Streaming Engine 4.10.0 addresses several reliability issues that affected transcoding operations and secure playback workflows. A particularly important fix resolves a transcoder initialization failure on modern Linux distributions (Ubuntu 25.04+, Debian 13, Fedora, and Arch Linux) where the "Cannot enable executable stack" error prevented transcoder startup. This issue affected customers upgrading to recent Linux kernel versions and has now been fully resolved.
The release also improves transcoding performance and stability when working with variable bitrate (VBR) source streams, addressing issues where fluctuating bitrates could degrade output quality or cause transcoder instability. Additionally, intermittent TLS errors that affected RTSPS workflows have been resolved improving reliable secure playback connections for organizations requiring encrypted media transport.
These improvements ensure smoother deployments, reduce operational troubleshooting, and increase uptime for streaming infrastructure. For more information on troubleshooting transcoding issues, see Troubleshoot Wowza Streaming Engine Transcoder issues.
Modernized security with vulnerability patches
Wowza Streaming Engine 4.10.0 addresses five security vulnerabilities affecting Apache Tomcat, log4j, Spring Security, and OpenSSL components. The platform now include an updated version of Apache Tomcat, which resolves CVE-2026-24734 and CVE-2026-29145, along with updated Spring Security Core 6.5.9 and Spring 6.2.17 to address CVE-2026-22732. Log4j has been updated to resolve CVE-2025-68161, and OpenSSL on Windows installations has been updated to version 3.5.5 ensuring cryptographic operations meet current security standards.
Enhanced developer experience with public REST API documentation
Wowza Streaming Engine 4.10.0 debuts public-facing REST API documentation, making it easier for developers to understand and integrate with our REST API. Developers can now quickly reference endpoint specifications, response schemas, and authentication requirements in the Wowza Developer Portal.
Detailed list of changes in Wowza Streaming Engine 4.10.0
The following changes were released in Wowza Streaming Engine 4.10.0.
- Improvements:
- Improved stability and performance for transcoder overlays.
- MainConcept Easy Video API (EVA) has moved out of beta to general availability.
- Optimized stream target implementation.
- Improved reliability of transcoder session start.
- Optimized live and VOD HTTP-origin applications. Removed the following deprecated playback client type properties:
smoothCacheControlPlaylistsmoothCacheControlMediaChunksmoothCacheControlDataChunksmoothStreamingEncryptionRandomIV
- Engine can now handle higher-resolution and higher-complexity input frames.
- Public-facing REST API documentation is now available on the Wowza Developer Portal.
- Bug fixes:
- WSE transcoder failed during ingest initialization with a "Cannot enable executable stack" error. Fixed on Ubuntu 25.04+, Debian 13, Fedora, and Arch Linux.
- Updated the default
Application.xmltemplate for live and VOD applications deployed in AWS cloud images.- The following packetizers have been removed:
sanjosestreamingpacketizer(Adobe HDS)smoothstreamingpacketizer(Microsoft Smooth Streaming)
- Added
<SRTListener>block
- The following packetizers have been removed:
- Improved transcoder functionality with variable bitrate (VBR) source-streams.
- Intermittent TLS errors during RTSPS playback affected customers using secure RTSP pull workflows.
- Security:
- Resolved CVE-2026-24734 affecting Apache Tomcat.
- Resolved CVE-2026-29145 by updating Apache Tomcat to version 10.1.53.
- Resolved CVE-2025-68161 related to log4j version.
- Resolved CVE-2026-22732 (updated Spring Security Core 6.5.9 and Spring 6.2.17)
- Resolved CVE-2025-2223 security vulnerability.
- Updated OpenSSL to 3.5.5 on Windows Wowza Streaming Engine installation.
Known issues with Wowza Streaming Engine 4.10.0
For a detailed list of currently known issues, see Known issues with Wowza Streaming Engine.




