CVE-2026-118631 is a vulnerability in Philips Hue Bridge Pro affecting the factory data service that listens on TCP port 5001. It allows a local attacker with low-privileged code execution within a container to perform argument injection, leading to restricted file write capabilities. The flaw arises from improper validation of user-supplied strings before executing system calls, enabling modification of files under the service account context. The vulnerability has a low CVSS score of 3.8 and does not have known exploits in the wild.
SEPPmail Secure Email Gateway versions before 15.1.1 have a weakness in the password recovery mechanism for unregistered GINA accounts with empty initial passwords. This flaw allows a remote unauthenticated attacker to reset the password of such an account without proper ownership verification, enabling unauthorized access and denial of service to the legitimate user.
The npm package @ifasn/mmdd-doc-mcp, which claims to be a Markdown TOC/stats/table MCP server, contains malicious code that, upon startup, performs unauthorized access to Alibaba Cloud ECS instance metadata service (IMDSv2). It retrieves temporary security credentials and sensitive host files such as /etc/shadow, /etc/passwd, SSH private keys, environment files, and Kubernetes service account tokens, writing this data to local files. This behavior is unrelated to the package's stated functionality and constitutes unauthorized credential and sensitive data harvesting.
@eeacms/volto-chatbot version prior to 2.0.4 contains an unauthenticated proxy vulnerability that allows attackers to invoke arbitrary Danswer API operations with server-side credentials. The middleware route '**/_v1_da/**' accepts any HTTP method and path without authentication or path restrictions, forwarding requests with attached API keys or session cookies. This enables a Confused Deputy attack where attackers can perform privileged actions on the upstream Danswer API as the configured service account.
In June 2026, iRhythm, a medical equipment provider specializing in wearable cardiac monitors, suffered a data breach impacting over 8.1 million individuals. Hackers accessed personal information and iRhythm account and device data from third-party-hosted business applications and attempted to extort a ransom. The compromised data includes names, addresses, dates of birth, email addresses, phone numbers, and device-related identifiers. iRhythm has not found evidence of identity theft or impact on its medical devices or operations. Notifications have been sent to affected individuals and regulatory bodies, including the US Department of Health and Human Services.
The npm package @zmtcdn/components version 9999.0.0 is a malicious dependency-confusion package. Its postinstall script collects system information including hostname, username, platform, working directory, and environment variable names, then sends this data to an external logging service. This reconnaissance can expose sensitive environment variables such as CI or secret tokens, potentially leading to credential theft. The package was published by the npm account kill_shs, which also published a similar malicious package @zmtcdn/ui.
Aokigahara is an infostealer malware targeting traditional data sources such as browsers, VPN clients, cryptocurrency wallets, FTP/SFTP clients, password managers, and email applications. It uniquely targets AI applications and development tools, stealing authentication files, session data, and configuration files from services like Claude, ChatGPT Desktop, Codex, and GitHub Copilot. It also collects developer credentials including Git files, SSH private keys, and cloud service credentials (AWS, Azure, Google Cloud). The stolen AI credentials may be used for unauthorized access, account resale, or data extortion. The malware uses anti-analysis techniques and secures its command-and-control communications with AES-256 encryption and X25519 key exchange.
The npm package data-pipeline-testmetest version 2.0.1 contains malicious code that executes during installation without a declared install script. It uses a binding.gyp file to run an obfuscated loader that decrypts and executes a large payload. This payload steals credentials from GitHub, npm, PyPI, RubyGems, and cloud services, then commits them to a public GitHub repository created in the victim's account. It also republishes the victim's packages with the same malicious hook. If a GitHub token is found, it installs a destructive service that deletes the user's home directory once the token is revoked. Removal of this service before token revocation and credential rotation is necessary to prevent data loss.
A vulnerability in Grafana allows an authenticated user or service account with read-only access to modify Git Sync connection configurations via the status subresource. This improper authorization flaw enables unauthorized configuration changes despite lacking administrative or write permissions. The issue affects Red Hat Hardened Images RPMs including grafana13.2. A security update is available that addresses this vulnerability.
A security update for Red Hat Hardened Images addresses multiple vulnerabilities in CUPS, including CVE-2026-55453. This flaw allows a remote attacker controlling a network printer to execute arbitrary code by injecting newline characters in printer status messages. The issue arises from improper sanitization in the CUPS IPP backend, enabling command execution with the print service account's privileges. Exploitation requires configuring a queue against a malicious IPP printer and using legacy driver filters. Systems using modern driverless printing or operating in headless environments are not affected.
An information disclosure vulnerability exists in the @backstage/plugin-kubernetes-backend prior to version 0.21.9. Authenticated users with Kubernetes resource read permissions could access sensitive data that the plugin is intended to mask, including credentials and confidential information from connected clusters. Exposure is limited to resources accessible by the Backstage service account and matching the targeted namespace and label selectors. The issue is fixed in version 0.21.9, which also improves masking behavior for certain custom resources.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (6457aa73ec15f68e06005977033aaba349467d40e3d406f0810684a43b74fcb5)
The package's preinstall script and its main entry (index.js) both perform identical credential-harvesting: they query the EC2 Instance Metadata Service (IMDSv2) at 169.254.169.254 for the identity document and IAM role security credentials, enumerate the entire process.env, and recursively read /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets). The collected data is POSTed to a hardcoded attacker-controlled host at hrnmn.dd.h4x.tv (paths /save_instance_info_hook from preinstall and /save_instance_info_index from index.js). The destination is unrelated to any legitimate package purpose, there is no user configuration, and the behavior fires automatically on `npm install` via the preinstall lifecycle hook as well as on any `require()`/`import` of the package. The harvested material — temporary AWS IAM credentials, cloud instance identity, arbitrary environment variables (which routinely contain API keys, tokens, and database credentials in CI/build environments), and Kubernetes service-account tokens — grants immediate cross-service access to the installer's cloud and cluster resources.
## Source: ghsa-malware (07386b2d1e2efa71fd38c591953684c11302ad77f1c7943bd542b71fd83184e3)
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 (9a26b9f2a46bdc8abd9882683d792c8fff6d94a9b89cc68162339e7fede47ceb)
On any require/import of @hrmony/pladddform-infrastructure, top-level code POSTs a beacon to the hardcoded attacker endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-infrastructure (host encodes the package name in the path). An aws_get() routine calls the AWS Instance Metadata Service at 169.254.169.254 using an IMDSv2 token, enumerates instance/identity metadata, iterates iam/security-credentials/<role> to retrieve short-lived IAM role credentials, and ships the result to the same attacker host. A local_get() routine serializes the entire process.env and recursively reads /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets), then POSTs the combined blob to the same endpoint. The package also declares a runtime dependency on @hrmony/kit-5 under the same scope, pulling additional code controlled by the same actor into any installer's environment. The package name and scope resemble a legitimate internal-sounding infrastructure package (typosquat/dependency-confusion shape targeting an internal '@harmony/platform-infrastructure'-style name).
## Source: ghsa-malware (fedcb513cf9f7b4f7d6598b35e8076c44199eadc1f143d5f46787b7635e0c30b)
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 (8f03abfe6149423144b6d3143a66cbca7925bb6eb736b1ece350d5a344684eb9)
@hrmony/pladddform-frontend@48.99.0 ships an index.js whose top-level code, executed on require/import, POSTs to the hardcoded attacker host https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-frontend and then invokes two harvesters. aws_get() queries the AWS EC2 Instance Metadata Service at 169.254.169.254 using IMDSv2 (PUT /latest/api/token) and sweeps /latest/meta-data/iam/security-credentials/ to collect instance identity, IAM role names, and temporary IAM security credentials. local_get() enumerates every entry of process.env and recursively reads /var/run/secrets/, capturing Kubernetes-mounted service-account tokens and secret files. Both payloads are POSTed to the same hardcoded hrnmn.dd.h4x.tv endpoint. The package has an empty description, no functional code beyond the stealer, an intentionally misspelled scope and name mimicking an internal 'harmony/platform-frontend', and declares a dependency on the similarly look-alike '@hrmony/kit-5', consistent with a dependency-confusion typosquat targeting an internal package name.
## Source: ghsa-malware (37ed7f1bf9d1ce61730644e3ac7eaf7f1525da3d26b9f9ba1f171d2ff2b72ae6)
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 (e9e61c4d5d499198c568d9f255e23b407eb7e47f7272c76bf5f50a0d0db31605)
On top-level module load, index.js queries the AWS instance metadata service at 169.254.169.254 (IMDSv2), retrieves the instance identity document, network interface information, and IAM security-credentials for every attached role (including temporary access key IDs, secret access keys, and session tokens), then POSTs the aggregated data to the hardcoded attacker endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-core. In the same import-time code path, it enumerates every entry in process.env and recursively reads all files under /var/run/secrets/ (Kubernetes service account tokens and mounted secrets) and POSTs those to the same host. The package exposes no functional API; its only behavior on require/import is credential and secret harvesting. package.json also declares a runtime dependency on the sibling scoped package @hrmony/kit-5 at ^1.0.0, which is fetched from the same author scope during install. The scoped name @hrmony/pladddform-core resembles a legitimate 'platform-core' package name, and the exfil host uses an attacker-controlled domain (h4x.tv) with a self-descriptive path.
## Source: ghsa-malware (547a909639f309cae645a90e1026d88e24c83cf90074a334e0dfb30a2b77f440)
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.
HomeBox is a home inventory and organization system. Prior to 0.26.0, POST /v1/groups/members invokes HandleGroupMemberAdd and GroupService.AddMember using a caller-supplied userID without requiring an owner role, an invitation token, target-user consent, or target-user notification. Any authenticated user can force another account into the caller's group, disclose the target user's email address and name through the resulting member list, and create the membership prerequisite used by a separate cross-group inventory-wipe vulnerability. This issue is fixed in version 0.26.0.
capgo.app (npm package `capgo`) through version 12.207.1 does not compare the caller's role rank against the requested role in the validateInvite() function of supabase/functions/_backend/private/invite_new_user_to_org.ts. The POST /private/invite_new_user_to_org endpoint only requires the org.update_user_roles permission for org_super_admin invitations, so an authenticated user holding only the org.invite_user permission (e.g., an org_member) can invite an external user as org_admin or org_billing_admin. When the invited account accepts the invitation via POST /private/accept_invitation, ensureOrgMembership creates the role binding using the Supabase service-role key, which bypasses the prevent_role_binding_priority_escalation and check_org_user_privileges database triggers. This allows privilege escalation resulting in full administrative control over the organization's apps, channels, members, and billing. The issue is addressed by pull request #3096, which compares the inviter's rank before permitting elevated invitations.
Konga before 2.1.0 contains a privilege escalation vulnerability that allows low-privileged local attackers to execute arbitrary code by planting attacker-controlled OpenSSL configuration or library files in a hardcoded filesystem path absent from default installations. On Windows, the missing directory resides in a location writable by any authenticated local user, enabling attackers to create the directory and place malicious files that execute at the privilege level of the user or service account that launches Konga, facilitating privilege escalation.
A security advisory from Red Hat addresses multiple vulnerabilities in the Red Hat Hardened Images RPMs, specifically in the Valkey component. One notable flaw (CVE-2026-85522) involves an out-of-bounds read in the Slot Migration component's createSlotImportJob function, which can be triggered remotely by manipulating the job_name argument. This vulnerability can cause the Valkey daemon to crash, resulting in a denial of service. The attack surface is limited by the unprivileged service account and SELinux policies, preventing further compromise. Red Hat has released updated RPM packages to fix these issues.