CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-35203 remediation guide

ZLMediaKit ZLMediaKit, zlmediakit

ZLMediaKit is a streaming media service framework. the VP9 RTP payload parser in ext-codec/VP9Rtp.cpp reads multiple fields from the RTP payload based on flag bits in the first byte, without verifying that sufficient data exists in the buffer. A crafted VP9 RTP packet with a 1-byte payload (0xFF, all flags set) causes the parser to read past the end of the allocated buffer, resulting in a heap-buffer-overflow. This vulnerability is fixed with commit 435dcbcbbf700fd63b2ca9eac6cef3b5ea75169d.

Open CVE record
ProductZLMediaKit ZLMediaKit, zlmediakit
Affected versions>= < 435dcbcbbf700fd63b2ca9eac6cef3b5ea75169d, < 2026-03-29
Fixed versions2026-03-29
Priority basisReview · CVSS 7.5 · EPSS 0.34%
01

Identify the affected asset

Confirm whether ZLMediaKit ZLMediaKit, zlmediakit is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= < 435dcbcbbf700fd63b2ca9eac6cef3b5ea75169d, < 2026-03-29. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 2026-03-29. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.