CVE-2026-7468 is a medium severity vulnerability in 1024-lab smart-admin up to version 3.30.0 involving improper access controls in the /smart-admin-api/druid/index.html file of the Demo Site component. The vulnerability can be exploited remotely without authentication and has been publicly disclosed. The vendor has not yet responded or provided a fix. The CVSS 4.0 base score is 6.9, reflecting network attack vector and no required privileges or user interaction. No official patch or mitigation guidance is currently available.
Bad actors exploited Kuse, a legitimate AI-based workplace application, to conduct a phishing campaign. Attackers leveraged a Vendor Email Compromise (VEC) to send malicious emails from a trusted vendor's compromised mailbox, establishing initial trust. The attack utilized Kuse's file-sharing features to host a fake blurred document with a Markdown file extension (.md) under the legitimate domain app[.]kuse[.]ai. Victims were presented with a fabricated document preview containing Spanish text prompting them to click a link. This redirected users to a fraudulent Microsoft login page designed to harvest credentials. The attack combined multiple social engineering techniques including domain trust exploitation, unusual file extensions to evade detection, and vendor relationship abuse to bypass security controls and user scrutiny.
OpenClaw versions before 2026.4.8 have a vulnerability where an approval-timeout fallback mechanism allows bypassing explicit user approval for inline eval commands on gateway and node execution hosts. This flaw enables attackers with limited privileges to execute commands that should require explicit approval, violating the intended security controls.
OpenClaw versions before 2026.4.8 have an authentication state management vulnerability where the resolved authentication closure becomes stale after configuration reload. This allows new gateway connections to use outdated authentication state, potentially bypassing authentication controls.
CVE-2026-41388 is a configuration management vulnerability in OpenClaw versions before 2026.3.31. The issue arises because the startup migration process treats empty-array settings as missing values, allowing an attacker to restart the application and rehydrate revoked Tlon configuration from file state. This behavior bypasses intended revocation controls.
ZionSiphon is operational technology-focused malware targeting water treatment and desalination facilities in Israel. The sample demonstrates ICS-awareness through industrial protocol interaction capabilities including Modbus, with incomplete support for DNP3 and S7comm. It incorporates geographic and environmental validation controls designed to restrict execution to Israeli water infrastructure systems. The malware attempts persistence through registry autorun entries, privilege escalation, and removable media propagation. Functionality includes network discovery of industrial devices, process manipulation targeting chlorine dosing and flow control, and configuration file modification. A critical validation flaw prevents successful execution, suggesting the analyzed sample represents incomplete development or testing. Embedded pro-Iran and anti-Israel messaging indicates politically motivated intent, though no specific threat actor attribution exists.
The Aranda File Server (AFS) component in Aranda Software Aranda Service Desk before 8.3.12 stores daily activity logs with predictable names in a publicly accessible directory, which allows unauthenticated remote attackers to obtain direct virtual paths of uploaded files and bypass access controls to download sensitive documents containing PII.
Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Apache Camel Camel-Coap component.
Apache Camel's camel-coap component is vulnerable to Camel message header injection, leading to remote code execution when routes forward CoAP requests to header-sensitive producers (e.g. camel-exec)
The camel-coap component maps incoming CoAP request URI query parameters directly into Camel Exchange In message headers without applying any HeaderFilterStrategy.
Specifically, CamelCoapResource.handleRequest() iterates over OptionSet.getUriQuery() and calls camelExchange.getIn().setHeader(...) for every query parameter. CoAPEndpoint extends DefaultEndpoint rather than DefaultHeaderFilterStrategyEndpoint, and CoAPComponent does not implement HeaderFilterStrategyComponent; the component contains no references to HeaderFilterStrategy at all.
As a result, an unauthenticated attacker who can send a single CoAP UDP packet to a Camel route consuming from coap:// can inject arbitrary Camel internal headers (those prefixed with Camel*) into the Exchange. When the route delivers the message to a header-sensitive producer such as camel-exec, camel-sql, camel-bean, camel-file, or template components (camel-freemarker, camel-velocity), the injected headers can alter the producer's behavior. In the case of camel-exec, the CamelExecCommandExecutable and CamelExecCommandArgs headers override the executable and arguments configured on the endpoint, resulting in arbitrary OS command execution under the privileges of the Camel process.
The producer's output is written back to the Exchange body and returned in the CoAP response payload by CamelCoapResource, giving the attacker an interactive RCE channel without any need for out-of-band exfiltration.
Exploitation prerequisites are minimal: a single unauthenticated UDP datagram to the CoAP port (default 5683). CoAP (RFC 7252) has no built-in authentication, and DTLS is optional and disabled by default. Because the protocol is UDP-based, HTTP-layer WAF/IDS controls do not apply.
This issue affects Apache Camel: from 4.14.0 through 4.14.5, from 4.18.0 before 4.18.1, 4.19.0.
Users are recommended to upgrade to version 4.18.1 or 4.19.0, fixing the issue.
OpenClaw versions before 2026.3.31 have an authentication boundary vulnerability due to improper handling of trust propagation in Telegram legacy allowFrom migration. This flaw allows attackers to bypass authentication controls and gain unauthorized access to named accounts.
A security advisory from Red Hat addresses vulnerabilities in the Red Hat Trusted Artifact Signer (RHTAS) Operator, which integrates with OpenShift Container Platform versions 4.16 through 4.20. One notable vulnerability (CVE-2026-33186) involves an authorization bypass in the gRPC-Go implementation due to improper validation of the HTTP/2 :path pseudo-header, allowing remote attackers to circumvent access controls under specific conditions. The advisory highlights that this issue is rated as important severity and affects environments using path-based authorization interceptors without proper normalization of incoming requests. The Red Hat Trusted Artifact Signer facilitates cryptographic signing and verification of software artifacts to ensure software supply chain integrity. No fixes are currently listed in the advisory for these vulnerabilities.
IBM Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 enables privilege escalation, allowing unauthorized users to perform administrative operations after being demoted. Attackers could access sensitive data, modify system configurations, or change permissions for other users. The issue undermines administrative controls and could lead to data breaches, system compromise, and loss of trust in the application's security mechanisms.
CVE-2026-22753 is a vulnerability in Spring Security versions 7.0.0 through 7.0.4 where using securityMatchers(String) combined with a PathPatternRequestMatcher. Builder bean to prepend a servlet path can cause requests to bypass the intended security filter chain. This results in authentication, authorization, and other security controls not being applied to those requests as designed, potentially allowing unauthorized actions. The vulnerability has a CVSS score of 7.5, indicating high severity. No official patch or remediation guidance is currently provided by the vendor.
Neko is a a self-hosted virtual browser that runs in Docker and uses WebRTC In versions 3.0.0 through 3.0.10 and 3.1.0 through 3.1.1, any authenticated user can immediately obtain full administrative control of the entire Neko instance (member management, room settings, broadcast control, session termination, etc.). This results in a complete compromise of the instance. The vulnerability has been patched in v3.0.11 and v3.1.2. If upgrading is not immediately possible, the following mitigations can reduce risk: Restrict access to trusted users only (avoid granting accounts to untrusted parties); ensure all user passwords are strong and only shared with trusted individuals; run the instance only when needed; avoid leaving it continuously exposed; place the instance behind authentication layers such as a reverse proxy with additional access controls; disable or restrict access to the /api/profile endpoint if feasible; and/or monitor for suspicious privilege changes or unexpected administrative actions. Note that these are temporary mitigations and do not fully eliminate the vulnerability. Upgrading is strongly recommended.
In early 2026, phishing attacks remain a top threat vector in security operations. This analysis covers a novel attack method exploiting Microsoft's OAuth 2.0 Device Authorization Grant (Device Code Flow) to compromise user accounts. Attackers use phishing emails containing Mailchimp's Mandrill service links to bypass security controls, leading victims to fake Adobe-themed websites. The sites abuse legitimate Microsoft authentication mechanisms to obtain access and refresh tokens, granting persistent delegated access to critical resources like Graph API, Teams, Outlook, and SharePoint. The technique leverages shared client IDs across tenants and family of client IDs (FOCI) for lateral movement. Two variants exist: one using external phishing infrastructure with dynamic code generation, and another relying solely on fake meeting invitations containing pre-generated device codes. The attack is particularly effective as it uses legitimate Microsoft services, making detection challenging.
This Red Hat security advisory addresses a set of bug fixes and enhancements for Red Hat Hardened Images RPMs, specifically targeting dotnet8.0 components. Among the related vulnerabilities is CVE-2025-55315, an important security flaw in ASP.NET Core's HTTP request handling that can lead to HTTP request smuggling attacks. This flaw allows an authorized network attacker to manipulate request boundaries, potentially bypassing security controls and enabling unauthorized actions on request data. The advisory notes that mitigation options are limited or not meeting Red Hat's criteria for ease of use and stability. The .NET 6.0 stream for RHEL has reached end of life and will not receive fixes. No explicit fixed versions are provided in this advisory.
PraisonAI's MCP command handling function parse_mcp_command() suffers from an OS command injection vulnerability (CVE-2026-41497). The function lacks proper validation of executables and arguments, allowing arbitrary commands such as bash, python, or /bin/sh with inline code execution to be executed via subprocess calls. Although a patch (commit 47bff654) was released, it does not implement critical controls like an allowlist of permitted commands, basename checks, or argument inspection, leaving the vulnerability partially unmitigated. Versions prior to 4.5.149 are affected, with 4.5.149 containing the fix. The vulnerability has a CVSS score of 9.8, indicating critical severity.
In late February 2026, following escalating Middle East tensions and coordinated military actions, Iranian APT group Seedworm launched sophisticated social engineering attacks via Microsoft Teams. Attackers impersonated IT support personnel using deceptive Microsoft 365 tenant domains to convince victims to execute malicious MSI installers. The campaign deployed a custom backdoor called Dindoor, which leveraged legitimate Deno runtime to execute obfuscated payloads in-memory, minimizing detection. The operation included multiple components for persistence, command-and-control communications, and data exfiltration. Infrastructure overlapped with previously reported MuddyWater operations. The attack demonstrates the group's evolution in using collaboration platforms as initial access vectors while combining dual-use tooling with living-off-the-land techniques to bypass traditional security controls.
The Rapid7 Insight Agent (versions > 4.1.0.2) is vulnerable to a local privilege escalation attack that allows users to gain SYSTEM level control of a Windows host. Upon startup the agent service attempts to load an OpenSSL configuration file from a non-existent directory that is writable by standard users. By planting a crafted openssl.cnf file an attacker can trick the high-privilege service into executing arbitrary commands. This effectively permits an unprivileged user to bypass security controls and achieve a full host compromise under the agent’s SYSTEM level access.
@fastify/express v4.0.4 and earlier contains a path handling bug in the onRegister function that causes middleware paths to be doubled when inherited by child plugins. When a child plugin is registered with a prefix that matches a middleware path, the middleware path is prefixed a second time, causing it to never match incoming requests. This results in complete bypass of Express middleware security controls, including authentication, authorization, and rate limiting, for all routes defined within affected child plugin scopes. No special configuration or request crafting is required.
Upgrade to @fastify/express v4.0.5 or later.
libsixel is a SIXEL encoder/decoder implementation derived from kmiya's sixel. Versions 1.8.7 and prior contain a use-after-free vulnerability in sixel_encoder_encode_bytes() because sixel_frame_init() stores the caller-owned pixel buffer pointer directly in frame->pixels without making a defensive copy. When a resize operation is triggered, sixel_frame_convert_to_rgb888() unconditionally frees this caller-owned buffer and replaces it with a new internal allocation, leaving the caller with a dangling pointer. Any subsequent access to the original buffer by the caller constitutes a use-after-free, confirmed by AddressSanitizer. An attacker who controls incoming frames can trigger this bug repeatedly and predictably, resulting in a reliable crash with potential for code execution. This issue has been fixed in version 1.8.7-r1.