Dell PowerStore 500T has an authorization bypass vulnerability (CWE-863) that allows a low-privileged attacker to elevate privileges to administrator. This flaw is addressed in version 5.1.0.0-2798105 or later. The vulnerability has a high severity with a CVSS score of 8.8.
A malicious file identified by the SHA-256 hash c283ec4b601b124d0f73a6c3dc9b90dc0cc8530257882ef87f4c65dff8290200 was observed by OffSeq Mirage honeypot sensors on 2026-11-16. This file was seen 7 times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file hash corresponds to a specific malicious payload such as a dropper, web shell, miner, or post-exploitation tool used during the attack. Organizations are advised to match this hash against files in their environments and security tools.
A malicious file identified by the SHA-256 hash 2c12964e25ea73ec4ae6be6b6f4b89cf5280c0dafc3ae6112bf2b8e1a97c2943 was observed three times on November 16, 2026, by OffSeq Mirage honeypot sensors. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in the Netherlands. Organizations are advised to match this hash against their files and security telemetry to detect potential compromise.
A malicious file identified by the SHA-256 hash db3f5bb77ed357748222aa1dc8cdc30fc12951a615159b81ed6e4ed6c7573273 was observed by OffSeq Mirage honeypot sensors on 2026-11-16. The file was detected 7 times during attacker activity involving the T1105 technique (Ingress Tool Transfer) from attacker infrastructure located in the Netherlands. This hash corresponds to a specific malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check this hash against their environment and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash 91bc4b83f3a02601f6038c1aa99af51f13b5742fb7f933003bbe27e61e1a80f8 was observed by OffSeq Mirage honeypot sensors on 2026-11-16. This file is associated with attacker activity involving the T1105 technique (Ingress Tool Transfer) and was seen originating from attacker infrastructure in the Netherlands. The file likely represents a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check for this hash in their environments and security tools.
A malicious file identified by the SHA-256 hash 056d31f9c19593f25a51965e279098aa487c79e5d2600eb56176cb34d8146746 was observed by OffSeq Mirage honeypot sensors on 2026-11-16. The file was detected seven times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. This hash corresponds to a specific malicious payload such as a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to match this hash against files in their environments and security feeds to detect potential compromise.
A malicious file identified by the SHA-256 hash 2abe0263c6e96f13d2f53f36e29c4210006ef841f4382eee40ae985443abedc9 was observed by OffSeq Mirage honeypot sensors on 2026-11-16. This file was detected three times during attacker activity involving the T1105 technique (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in the Netherlands. Organizations are advised to check their environments and security tools for this hash to detect potential compromise.
A malicious file identified by the SHA-256 hash f61c060ecc313f9a454f9a1510bab930c6ea89509d5a1bb3b4991a2336acb44b was observed by OffSeq Mirage honeypot sensors on 2026-11-16. This file was seen 7 times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file is associated with a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check their environments and security tools for this hash to detect potential compromise.
A malicious file identified by the SHA-256 hash 6a9e31305898a3bee036b222aa9d3f3034c12b718eefd7a79b4644633fce443d was observed by OffSeq Mirage honeypot sensors on 2026-11-16. This file was seen three times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file hash corresponds to a specific malicious payload such as a dropper, web shell, miner, or post-exploitation tool that was staged or delivered during the attack. Organizations are advised to match this hash against files in their environments and security feeds.
A vulnerability in the http2 library up to version 5.4.13 allows malformed CONNECT requests to bypass validation checks. Specifically, the library failed to enforce the presence of the :authority header and the consistency between :authority and Host headers, enabling request smuggling past front-end access controls when front-end and backend use different headers for routing or authorization. This was fixed in http2 version 5.4.14, which properly validates CONNECT requests and rejects malformed ones with a PROTOCOL_ERROR stream error.
CVE-2026-129543 is a type confusion vulnerability in Samsung Open Source Starfish that allows input data manipulation. The flaw involves accessing a resource using an incompatible type, which can lead to impacts on confidentiality, integrity, and availability.
CVE-2026-129542 is a low-severity vulnerability in Samsung Open Source Starfish where certain files or directories are accessible to external parties. This issue allows external users to probe system files, potentially exposing information. The vulnerability has a CVSS score of 3.1, indicating low impact, with network attack vector, high attack complexity, no privileges required, and user interaction needed. No known exploits or patches are currently documented.
SSCMS versions 7.2.0 through 7.4.0 have an arbitrary file read vulnerability in the layerImageUpload endpoint. This flaw allows any registered user-center account to copy server files by supplying crafted source paths. Attackers can use siteId 0 with malicious filePaths to copy configuration files into a publicly accessible upload directory and then download them anonymously.
VoAPI versions 1.0.0 through 1.2.0 have a SQL injection vulnerability that allows authenticated users to inject SQL via crafted column names in search filter keys on list endpoints such as GET /api/log. Exploiting this flaw, attackers can read the HS256 JWT signing secret from the option table and forge manager role tokens to take over management APIs.
EdgeChat versions 2.5.0 through 2.21.0 have a cross-site scripting (XSS) vulnerability in the Vditor @-mention autocomplete feature. This flaw allows invited users to inject malicious HTML via unescaped usernames. An attacker can register a username containing an image tag with an onerror JavaScript payload that executes when mentioned, enabling theft of localStorage session tokens and account takeover.
The npm package @univerjs-pro/sheets-pivot-chart version 1.5.0 contains malicious code that can fully compromise any computer on which it is installed or running. The compromise may allow an attacker full control over the system, risking exposure of all stored secrets and keys. Immediate removal of the package and rotation of all secrets from a different machine is strongly advised.
The npm package pmhq-dist-win-x64 version 9.0.2 contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a separate, uncompromised device. Removing the package alone does not guarantee full remediation, as the attacker may have established persistent control over the system.
Qbian61 forum-java commit 20f7e68 through commit 63152c4 contains a stored cross-site scripting vulnerability that allows authenticated users to inject script by posting unsanitized comment content rendered via jQuery .html() in the reply dialog. Attackers can post comments with img onerror payloads that execute when victims click Reply, stealing the non-HttpOnly sid session cookie to hijack accounts including administrators.