CVE-2018-6548

What it is

A use-after-free issue was discovered in libwebm through 2018-02-02. If a Vp9HeaderParser was initialized once before, its property frame_ would not be changed because of code in vp9parser::Vp9HeaderParser::SetFrame. Its frame_ could be freed while the corresponding pointer would not be updated, leading to a dangling pointer. This is related to the function OutputCluster in webm_info.cc.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2018-02-02 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2018-02-02 09:29 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 02:02 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.4% in the next 30 days (EPSS).
• Severity: 9.8 CRITICAL (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2018-02-02 09:29 UTC

Last modified

2026-06-17 02:02 UTC

Exploit probability

1.4% · EPSS, next 30 days

Weakness

CWE-416 · Use after free

Record status

Modified

Affected

• Webmproject Libwebm ≤ 1.0.0.27

Attack profile CVSS 3.0 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2018-6548.md and follow it. Check whether this project is affected by CVE-2018-6548. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge