CVE-2026-58823High· 7.8▾ TwilightIn stpropnci_process_std of stpropnci_std.cc, there is a possible memory safety issue due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Sep 10.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
— → 7.8
none → high
0.08%
In stpropnci_process_std of stpropnci_std.cc, there is a possible memory safety issue due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-55285High· 7.8In openLogicalChannel of multiple files, there is a possible out-of-bounds write due to a missing bounds check
CVE-2026-55290Low· 3.3In setTo of ResourceTypes.cpp, there is a possible out-of-bounds heap read due to a missing bounds check
CVE-2026-58839High· 7.8In forEachLine of MountRegistry.cpp, there is a possible out of bounds read due to a buffer overflow
CVE-2026-56978High· 8.4In get_global_config_item_addr of gc.c, there is a possible out-of-bounds read due to a missing bounds check
CVE-2026-58710High· 8.8In DecodeFilmGrainParams of film_grain_dec.cc, there is a possible out-of-bounds write due to a missing bounds check
CVE-2026-58695High· 7.8In gmc_phy_lp3_exit_restore_registers of phy_power.c, there is a possible escalation of privilege due to a missing bounds check