Secuno
ENNL
Book demo

CVE-2026-58699

8.4 HIGHEPSS 0.11%
  1. Published15 Sept 2026

Description

In Vp9DecEndOfStream of vp9hwd_output.cc, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-569788.4
In get_global_config_item_addr of gc.c, there is a possible out-of-bounds read due to a…
CVE-2026-845168.1
An out-of-bounds read was addressed with improved bounds checking. This issue is fixed…
CVE-2026-552099.8
resdata is software for reading and writing result files from the Eclipse reservoir…
CVE-2026-905608.2
zstd-jni versions 1.2.0 through 1.5.7-13 contain an out-of-bounds read vulnerability in…
CVE-2026-890468.2
zstd-jni versions 1.5.5-6 through 1.5.7-13 contain an out-of-bounds read vulnerability…
CVE-2026-225909.1
eprosima Fast DDS is a C++ implementation of the DDS (Data Distribution Service)…

Frequently asked

Is CVE-2026-58699 being actively exploited?

CVE-2026-58699 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.11%.

How severe is CVE-2026-58699?

CVE-2026-58699 has a CVSS 3.1 base score of 8.4, rated high. EPSS estimates a 0.11% probability of exploitation.

How do I fix CVE-2026-58699?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-58699 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.