Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for IWF CSAM URL...
CVE-2026-8889
Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for IWF CSAM URL matching (25,020 hashes) an
共收录 24063 条相关情报。
← 返回所有主题CVE-2026-8889
Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for IWF CSAM URL matching (25,020 hashes) an
CVE-2026-50033
Local privilege escalation due to DLL hijacking vulnerability. The following products are affected: Acronis DeviceLock D
CVE-2026-8874
Version 3.0.7 of the Securly Chrome Extension downloads JSON files containing crisis alert keywords and filtering rules
CVE-2026-37700
Cross Site Scripting vulnerability in MaxSite CMS v.109.2 allows a remote attacker to obtain sensitive information via t
CVE-2026-26825
A use-of-uninitialized memory vulnerability exists in libxls 1.6.3 when parsing malformed XLS files. The issue is reacha
CVE-2026-44682
Local privilege escalation due to DLL hijacking vulnerability. The following products are affected: Acronis DeviceLock D
CVE-2026-42840
An authenticated user can persist arbitrary HTML/JavaScript in the email_id or mobile_no fields of a Customer record and
CVE-2026-42839
An authenticated ERPNext user with Item record edit permissions can persist arbitrary HTML/JavaScript in the item_name,
CVE-2026-7888
Concrete CMS below 9.5.2 is vulnerable to PHP Object Injection via unserialize() calls in the Workflow, Form block, and
CVE-2026-26378
Cross Site Scripting vulnerability in Koha 25.11 and before allows a remote attacker to execute arbitrary code via file
CVE-2026-26379
An issue in Koha v.25.11 and before allows a remote attacker to execute arbitrary code via the Z39.50 configuration modu
CVE-2026-44180
### Summary Jupyter Enterprise Gateway has a prohibited UID and GID feature that by default prevents launching kernels
CVE-2026-44023
### Impact In versions `>= 1.5.0, = 2.74.1` ### Workarounds If upgrading is not immediately possible, avoid passing unt
CVE-2026-44019
### Impact In versions `>= 2.5.0, = 2.74.1` ### Workarounds If upgrading is not immediately possible: - reject `file:`
CVE-2026-47214
### Impact The HTML backend did not perform sufficient validation during resource handling: - Accepted `file://` URIs en
CVE-2026-44022
### Impact The LaTeX backend's handling of `\includegraphics`, `\input`, and `\include` commands lacked path containment
CVE-2026-44020
### Impact The USPTO patent XML parser used the standard `xml.sax.parseString()` without protection against XML External
CVE-2026-44018
### Impact The METS-GBS backend's XML parsing and the input document format detection lacked security controls, enabling
CVE-2026-44016
### Impact In versions `>= 2.82.0, < 2.91.0`, if the HTML backend was explicitly configured for rendering (rendering opt
CVE-2026-43980
Node names (long_name, short_name) received via MQTT are stored in SQLite without sanitization and rendered into the DOM