Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 2.16% for the current model date.
BlackTreeCVE IntelligenceUnknown · Unknown
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | libvpx | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.12.0-1.2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | libvpx | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.12.0-1+deb12u2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | libvpx | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.12.0-1.2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | libvpx | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.12.0-1.2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | libvpx | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 1.12.0-1ubuntu2 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | mozjs102 | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch availableVP9 in libvpx before 1.13.1 mishandles widths, leading to a crash related to encoding.
VP9 in libvpx before 1.13.1 mishandles widths, leading to a crash related to encoding.
The product does not handle or incorrectly handles an exceptional condition.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
VP9 in libvpx before 1.13.1 mishandles widths, leading to a crash related to encoding.
The product does not handle or incorrectly handles an exceptional condition.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-755: Improper Handling of Exceptional Conditions. The product does not handle or incorrectly handles an exceptional condition.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 30 Sept 2023 · Last source change 23 Sept 2024, 16:15 UTC · CWE-755 · Improper Handling of Exceptional Conditions
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.