---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (3f70364834c6aa09fed4520d6144867e921c75f416d315addf2ec3b28a92d2e4)
The package advertises itself as text helpers for AI pipelines (toText/normalizeText) but src/index.js unconditionally invokes a dropper at module top level on require()/import. The dropper downloads a platform-specific installer from https://anymeetvia.com/download/{win|mac-x86_64|linux}/install1[.ps1] into the OS temp directory, chmods it 0755 on macOS/Linux, and executes it via powershell -File on Windows or bash on Unix, then calls process.exit. There is no version pinning, no hash or signature verification, and the download endpoint is an author-controlled domain unrelated to the advertised functionality. The remote installer content is not present in the package and can be changed by whoever controls anymeetvia.com at any time. The README and module.exports document only the text-helper API; the dropper is undocumented.
## Source: ghsa-malware (157801df9aca5cfc352c39f3fae51f04dd16ee810064ea6d95d4cd99f98931ff)
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.
CVE-2026-70719 is a vulnerability in Oracle Hyperion Calculation Manager version 11.2.25.0.000. It allows an unauthenticated attacker who has logon access to the infrastructure where the product runs to gain unauthorized read access to some data accessible by the application. The vulnerability has a medium severity with a CVSS 3.1 base score of 4.0, indicating limited confidentiality impact without integrity or availability effects. No public exploits are known, and Oracle has not explicitly provided a patch link in the advisory. The vulnerability is related to security controls within the product component.
Team82 research uncovered 23 vulnerabilities in Copeland XWEB Pro supervisory controllers, including 21 high-severity issues. These vulnerabilities can be chained to bypass security controls and achieve root-level remote code execution without authentication. In testing, attackers could manipulate connected refrigeration systems by compromising the supervisory controller. This demonstrates a significant IT-to-physical impact path where an attacker can affect physical processes without obvious tampering signs.
Security controls can block a familiar attack method while missing quieter ways to achieve the same objective. Picus Security's Blue Report 2026 shows how prevention rates can vary dramatically by technique and why behavioral testing is needed to uncover those gaps. [...]
A cross-site scripting (XSS) vulnerability was identified in GitLab CE/EE affecting versions from 18.2 up to but not including 19.0.6, 19.1 up to but not including 19.1.4, and 19.2 up to but not including 19.2.2. The issue arises from improper neutralization of user-controlled input rendered in pagination controls within an analytics dashboard component. This vulnerability has been remediated in the specified fixed versions.
CVE-2024-14045 is an improper authorization vulnerability in OpenBoxes affecting versions 0.9.0, 0.9.1, and 0.9.2. The flaw exists in the Product Supplier Edit Controller component, specifically in the RoleInterceptor.groovy file. An attacker can exploit this remotely to bypass authorization controls. A public exploit is available. Upgrading to version 0.9.3 resolves the issue.
Multiple security vulnerabilities have been identified in Performance Co-Pilot (PCP), a suite of tools for system-level performance measurement analysis. These include arbitrary command execution via command injection, privilege escalation to root, unauthenticated access bypassing access controls, and denial of service due to signed integer overflow. Red Hat has issued an important security advisory providing updates to address these issues in Red Hat Enterprise Linux 10 and related products.
Storm-0501 is a financially motivated cybercrime group conducting sophisticated ransomware campaigns targeting Microsoft Azure cloud environments. Unlike traditional ransomware that encrypts local endpoints, Storm-0501 hijacks cloud tenants by compromising high-privilege administrative identities, dismantling defensive controls such as resource locks and backups, and weaponizing native cloud tools. This cloud ransomware campaign involves evading detection, exfiltrating data, destroying backups, and demanding ransom payments. Detection requires cloud detection and response (CDR) capabilities that provide full visibility into the attack chain and connect disparate cloud activity logs into a unified threat story. Tenable One Cloud Exposure offers AI-powered threat detection tailored to Storm-0501’s tactics, enabling rapid triage, containment, and recovery actions to mitigate the impact of these attacks.
openssl_encrypt versions before 1.4.0 contain a sandbox bypass vulnerability where the plugin sandbox fails to restrict alternative file access methods like pathlib.Path and io.open. Attackers can import pathlib or io modules to read and write arbitrary files, completely bypassing the restricted_open file access controls.
CVE-2026-19997 is an authorization bypass vulnerability in Webkul Bagisto affecting versions 2.4.0 through 2.4.4. The flaw exists in the processing of the /admin/sales/rma/requests endpoint within the Backend Sales RMA component. This vulnerability allows remote attackers with high privileges to bypass authorization controls. The vendor has acknowledged the issue and indicated that some fixes have been implemented internally, with remaining fixes planned for future releases. The CVSS 4.0 score rates this vulnerability as medium severity.
CVE-2026-19994 is an authorization bypass vulnerability in Webkul Bagisto versions 2.4.0 through 2.4.4. It affects the /admin/configuration/cache-management/execute endpoint in the Configuration Management component. The flaw allows remote attackers to manipulate the 'action' argument to bypass authorization controls. The vendor has acknowledged the issue and is addressing it through their internal security processes, with some fixes already applied and others planned for future releases. The vulnerability has a medium severity rating with a CVSS score of 5.3. Exploit code has been made public, but no known exploitation in the wild has been reported.
This article provides an in-depth analysis of Microsoft's new unified Microsoft 365 Copilot super app, detailing its architectural shift that merges consumer and enterprise AI features. It highlights critical cybersecurity and data governance implications, including how Microsoft Entra enforces strict separation between personal and enterprise data to prevent leaks. The piece also outlines deprecated features and advises defenders on monitoring identity switching and file-sharing controls within the new environment.
CVE-2026-19966 is an authorization bypass vulnerability in CodeCanyon TimeCamp Integration for CRM versions 2.0 through 2.8. It involves improper processing of the contact_id argument in the /clients/save_contact component, allowing remote attackers to bypass authorization controls. The vulnerability has a medium severity with a CVSS 4.0 base score of 5.3. Exploit code is publicly available, but no official patch or remediation guidance has been provided yet.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (91cc3a6ca908fc8beff657d21068318704e4576cb3778c360036ab5bfef4e56c)
depcruise-baseline@99.9.1 has a name resembling dependency-cruiser/depcruise but ships an empty index.js and declares its sole runtime dependency as a direct https:// tarball URL rather than a registry package: "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.4.tgz". On npm install, npm downloads and installs that tarball as a transitive dependency, so whoever controls the ltidi.storage.googleapis.com bucket controls arbitrary code that runs on the installer via that dependency's require graph and lifecycle hooks. The package has no functional code of its own; its only effect is to pull code from an author-controlled, out-of-registry location into the installer's dependency tree.
## Source: ossf-package-analysis (446d5f8b4c581782feffc22437e24c36313ac56e648162a5f80e21eee9e9f083)
The OpenSSF Package Analysis project identified 'depcruise-baseline' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix stack info leak in RME Digiface status snd_rme_digiface_read_status() reads a four-word status block from the device into an uninitialised on-stack __le32 buf[4] and, whenever the vendor control-IN transfer does not return a negative error, copies all four words into the caller's status[]. snd_usb_ctl_msg() copies the full requested size back into the caller's buffer regardless of how many bytes the data stage actually delivered: buf = kmemdup(data, size, GFP_KERNEL); err = usb_control_msg(dev, pipe, request, requesttype, value, index, buf, size, timeout); memcpy(data, buf, size); usb_control_msg() returns the transferred length on a short control-IN, which is a non-negative value, and writes only that many bytes. The remainder of the copy back is the kmemdup()ed image of the caller's buffer, so a device answering with a short data stage leaves the trailing words of buf[] holding leftover kernel stack. The only guard in the caller is err < 0, so those words are stored into status[]. They then reach user space: snd_rme_digiface_get_status_val() selects a 16-bit halfword of status[] per the control's reg/mask, and the eight Digiface status controls together expose the whole 16-byte frame to an unprivileged reader of /dev/snd/controlC*. Zero-initialise the buffer so a short read yields zeros instead of stack residue. This mirrors snd_rme_get_status1(), which already clears its output word before the same kind of vendor read. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>
ContextForge is an AI gateway, registry, and proxy that provides centralized discovery, guardrails, and management for MCP, A2A, and REST or gRPC APIs. Prior to 1.0.3, the /admin/gateways/test call site in mcpgateway/admin.py calls validate_gateway_test_url() in mcpgateway/common/validators.py to resolve and reject private, loopback, link-local, and cloud-metadata addresses, but ResilientHttpClient later resolves the original hostname again without binding the validated address. When MCPGATEWAY_ADMIN_API_ENABLED is enabled, an attacker with a database-backed role containing explicit gateways.read permission can use DNS rebinding to return a public address during validation and a private or metadata address during connection, bypassing ssrf_blocked_networks and ssrf_dns_fail_closed because those controls apply only to the validation-time result. The endpoint's allow_admin_bypass=False setting means a bootstrap-only virtual platform-admin identity without a database role is not sufficient. Successful exploitation can reach internal services and cloud metadata, expose cloud credentials, access internal APIs, or probe internal network ports. This issue is fixed in version 1.0.3.
A vulnerability in Webkul Bagisto up to version 2.4.4 affects the Customer Item Deletion Endpoint, leading to improper access controls. The issue can be exploited remotely and the exploit code is publicly available. The vendor has acknowledged the issue, stating it was identified internally prior to public disclosure and is being addressed through their security and development lifecycle, with some fixes already implemented and others planned for upcoming releases. The vulnerability has a low severity rating.
CVE-2026-47191 is a vulnerability in Siemens kas, a setup tool for bitbake-based projects, affecting versions prior to 5.3. The issue involves improper verification of cryptographic signatures when relying solely on git commit IDs (SHA-1 or SHA-256) to validate repository state. This can allow an attacker who controls the repository to trick users into checking out malicious branches with the same name. The vulnerability primarily impacts SHA-256 commit IDs due to the possibility of hash collisions with SHA-1. Version 5.3 addresses this issue. Workarounds include avoiding sole reliance on commit IDs, validating cryptographically signed commits or tags, or using mirrored repositories with verified integrity.