CVE-2018-6548
Reported by mitre · Published February 2, 2018
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| libwebm | webmproject | 1.0.0.27 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| n/a | n/a | * |
Timeline
- Feb 2, 2018 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Apr 6, 2026 Security Advisory
- Jun 17, 2026 CVE Updated
- Sep 19, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2018-6548
vulnetix vdb fixes CVE-2018-6548
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2018-6548/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart