CVE-2025-5283VulnerabilityPublished 16 Jun 2025Updated 11 Oct 2026

SUSE · security update for libvpx

Affects SUSESource GCVE Database

Authoritative record:CVE-2025-5283· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium : upgrade the Red Hat redhat/libvpx package to 9.4.1 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.4.1

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade the Red Hat redhat/libvpx package to 9.4.1.

Affected software

Product	Affected	Fixed in
Red Hatredhat/libvpx`pkg:rpm/redhat/libvpx`Other threats	Affected =9.4 <9.4.1	Fixed in 9.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated libvpx packages that address this vulnerability. Users of affected Red Hat Enterprise Linux 9.4 Extended Update Support and related variants should apply the provided security update (libvpx-1.9.0-7.el9_4.1) as detailed in the Red Hat advisory RHSA-2025:9122 and the referenced article https://access.redhat.com/articles/11258. Applying this update fully mitigates the vulnerability.

Description

The libvpx packages provide the VP8 SDK, which allows the encoding and decoding of the VP8 video codec, commonly used with the WebM multimedia container file format. Security Fix(es): * libvpx: Double-free in libvpx encoder (CVE-2025-5283) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The double-free vulnerability in the libvpx encoder could allow an attacker to cause memory corruption, which may lead to application crashes or potentially arbitrary code execution depending on the context of use. The advisory rates the impact as important (high severity). No known exploits in the wild have been reported at the time of the advisory.

Summary

The libvpx packages, used for encoding and decoding the VP8 video codec, contain a double-free vulnerability in the encoder component identified as CVE-2025-5283. This vulnerability could potentially lead to memory corruption issues. Red Hat has issued an important security advisory (RHSA-2025:9122) and released updated libvpx packages for Red Hat Enterprise Linux 9.4 Extended Update Support and related product variants to fix this issue. The advisory references a bug fix (BZ-2368749) and provides updated package versions (libvpx-1.9.0-7.el9_4.1) for multiple architectures.

CWE-415Double Free (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The product calls free() twice on the same memory address.
Architecture and Design
Choose a language that provides automatic memory management.
Implementation
Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly.
Implementation
Use a static analysis tool to find double free instances.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Jun 2026, 22:06 UTC

WeaknessesCWE-415

Technical details

References

Community reviews

Related threats