---METADATA---
VENDOR: Apache
PRODUCT: MINA
AFFECTED_VERSIONS: 2.0.0 <= 2.0.27, 2.1.0 <= 2.1.10, 2.2.0 <= 2.2.5
CONFIDENCE: high
MISSING: exploit_status
---END_METADATA---

Description Summary:
An incomplete fix for deserialization vulnerabilities in Apache MINA’s AbstractIoBuffer allows attackers to bypass allowlist protections via early static initializer execution.

Executive Summary:
A critical deserialization vulnerability in Apache MINA allows remote code execution due to an incomplete fix in the classname allowlist implementation.

Vulnerability Details

CVE-ID: CVE-2026-41409

Affected Software: Apache MINA

Affected Versions: 2.0.0 <= 2.0.27, 2.1.0 <= 2.1.10, 2.2.0 <= 2.2.5

Vulnerability: The vulnerability exists because the classname allowlist is applied too late during the deserialization process in AbstractIoBuffer.getObject(), allowing malicious classes to be initialized.

Business Impact

With a CVSS score of 9.8, this vulnerability poses a severe threat to any application utilizing the Apache MINA framework for object deserialization. Successful exploitation allows an attacker to achieve remote code execution on the host system, potentially resulting in full system compromise and data breach.

Remediation Plan

Immediate Action: Update Apache MINA to versions 2.0.28, 2.1.11, or 2.2.6, which implement the classname allowlist earlier in the deserialization process.

Proactive Monitoring: Review application performance and error logs for unexpected class loading or deserialization exceptions that may indicate exploitation attempts.

Compensating Controls: If upgrading is not immediately feasible, restrict the exposure of services that deserialize untrusted data to minimize the attack surface.

Exploitation Status

Public Exploit Available: Not specified

Analyst Notes: As of Apr 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability highlights the dangers of insecure deserialization, which is a frequent target for remote attackers. Administrators must verify their current MINA version and apply the recommended security updates to ensure the classname allowlist is enforced correctly.

---METADATA---
VENDOR: OpenClaw
PRODUCT: OpenClaw
AFFECTED_VERSIONS: Before 2026.3.22
---END_METADATA---

Description Summary:
A privilege escalation vulnerability in OpenClaw during device pairing allows attackers to gain unauthorized access by manipulating device roles.

Executive Summary:
OpenClaw contains a critical privilege escalation flaw that allows unauthorized users to manipulate device roles during the pairing process.

Vulnerability Details

CVE-ID: CVE-2026-41386

Affected Software: OpenClaw

Affected Versions: Before 2026.3.22

Vulnerability: Bootstrap setup codes are not properly bound to specific device roles or scopes, allowing an unauthenticated attacker to escalate privileges during initial pairing.

Business Impact

The CVSS score of 9.1 underscores the critical nature of this flaw, which allows an attacker to bypass intended access controls. This could lead to unauthorized administrative control over devices, potentially exposing sensitive operational data or allowing for broader network compromise.

Remediation Plan

Immediate Action: Update OpenClaw to version 2026.3.22 or later immediately to enforce proper scope and role binding during pairing.

Proactive Monitoring: Review system logs for pairing events and privilege changes that occur during the onboarding of new devices.

Compensating Controls: Implement strict physical and network access controls during the device pairing window to minimize the exposure to unauthorized individuals.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Apr 28, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Updating to the latest version is mandatory to correct the logic error in the pairing process. Administrators should ensure that all new device onboarding follows the updated, secure pairing procedures defined in the latest documentation.

---METADATA---
VENDOR: MLflow
PRODUCT: MLflow
AFFECTED_VERSIONS: mlflow mlflow/mlflow: unspecified up to (excluding) 3.11.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
MLflow versions prior to 3.11.0 are vulnerable to the creation of temporary files with insecure permissions, potentially allowing local attackers to gain unauthorized access to sensitive information.

Executive Summary:
MLflow versions prior to 3.11.0 contain a vulnerability involving insecure temporary file permissions that could lead to unauthorized local data access.

Vulnerability Details

CVE-ID: CVE-2026-4137

Affected Software: MLflow

Affected Versions: mlflow mlflow/mlflow: unspecified up to (excluding) 3.11.0

Vulnerability: This is an insecure file permission issue (CWE-378) where temporary files are created with overly permissive access rights. Exploitation requires local access to the system (AV:L) and specific conditions regarding the local environment.

Business Impact

While the attack vector requires local access, successful exploitation could allow an attacker to read or modify sensitive temporary data, potentially leading to privilege escalation or the theft of credentials stored within the MLflow workspace. The CVSS score of 7.0 (High) reflects the potential for full compromise of the affected local environment.

Remediation Plan

Immediate Action: Update the MLflow package to version 3.11.0 or later to ensure temporary files are created with appropriate, restrictive system permissions.

Proactive Monitoring: Monitor local file system activity for unexpected file creation or access patterns within temporary directories used by MLflow services.

Compensating Controls: Implement strict OS-level access controls and ensure that the service runs with the least privilege necessary, minimizing the impact if a local attacker attempts to leverage insecure files.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of May 19, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The requirement for local access naturally limits the attack surface to multi-user or compromised-host scenarios.

Analyst Recommendation

Administrators should prioritize updating to the patched version 3.11.0 to close this local security gap. Ensure that all systems running MLflow are hardened with appropriate file system permissions to further mitigate risk.

---METADATA---
VENDOR: OpenClaw
PRODUCT: OpenClaw
AFFECTED_VERSIONS: Before 2026.3.31
CONFIDENCE: high
MISSING: exploit_status
---END_METADATA---

Description Summary:
A sandbox bypass vulnerability in OpenClaw before 2026.3.31 allows attackers to escalate privileges by manipulating heartbeat context inheritance and the senderIsOwner parameter.

Executive Summary:
A critical sandbox bypass vulnerability in OpenClaw allows attackers to escalate privileges, potentially leading to full system compromise.

Vulnerability Details

CVE-ID: CVE-2026-41329

Affected Software: OpenClaw

Affected Versions: Before 2026.3.31

Vulnerability: This vulnerability involves improper context validation within the OpenClaw sandbox. By manipulating the heartbeat context inheritance and the senderIsOwner parameter, an attacker can bypass sandbox restrictions to achieve unauthorized privilege escalation.

Business Impact

The severity of this vulnerability is underscored by its 9.9 CVSS score, indicating a nearly maximal risk to system security. Successful exploitation grants an attacker elevated privileges, which could result in complete host compromise, data theft, and the disruption of critical business services.

Remediation Plan

Immediate Action: Upgrade all instances of OpenClaw to version 2026.3.31 or later immediately.

Proactive Monitoring: Review system logs for unusual heartbeat signals or repeated attempts to manipulate context parameters that may indicate exploitation efforts.

Compensating Controls: Ensure the application is running within a containerized environment with hardened kernel-level protections to limit the impact of a sandbox breakout.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Apr 21, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the critical nature of this privilege escalation vulnerability, immediate patching is required. Administrators should verify that all deployments are updated to version 2026.3.31 to effectively close the sandbox bypass vector.

---METADATA---
VENDOR: Dgraph
PRODUCT: Dgraph
AFFECTED_VERSIONS: Prior to 25.3.3
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
An unauthenticated DQL injection vulnerability in Dgraph's default configuration allows attackers to read all database contents via crafted mutation requests.

Executive Summary:
A critical DQL injection vulnerability in Dgraph allows unauthenticated attackers to bypass security controls and gain full read access to the entire database.

Vulnerability Details

CVE-ID: CVE-2026-41328

Affected Software: Dgraph

Affected Versions: Prior to 25.3.3

Vulnerability: The vulnerability stems from improper sanitization of the Lang value in DQL mutations. By sending specifically crafted HTTP POST requests to the /alter and /mutate endpoints, an unauthenticated attacker can inject arbitrary query logic, effectively bypassing ACL restrictions in default configurations.

Business Impact

With a CVSS score of 9.1, this vulnerability allows for total compromise of database confidentiality. An attacker can exfiltrate all stored records, posing an existential threat to data privacy and regulatory compliance.

Remediation Plan

Immediate Action: Upgrade Dgraph to version 25.3.3 or later to ensure proper sanitization of DQL inputs.

Proactive Monitoring: Review audit logs for suspicious activity on the /alter and /mutate endpoints and investigate any unexpected DQL query structures.

Compensating Controls: Enable Access Control Lists (ACLs) if they are not already active, and restrict network access to the Dgraph API ports to authorized application servers only.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Apr 24, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This is a severe vulnerability that grants full read access to the database without authentication. It is critical to apply the provided patch immediately and verify that ACLs are properly configured to add a layer of defense-in-depth.

---METADATA---
VENDOR: Dgraph
PRODUCT: Dgraph
AFFECTED_VERSIONS: Prior to 25.3.3
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Dgraph is vulnerable to an unauthenticated DQL injection attack that allows full read access to database data via crafted HTTP POST requests.

Executive Summary:
A critical DQL injection vulnerability in Dgraph allows unauthenticated attackers to gain full read access to sensitive database contents.

Vulnerability Details

CVE-ID: CVE-2026-41327

Affected Software: Dgraph Dgraph

Affected Versions: Prior to 25.3.3

Vulnerability: This vulnerability involves improper input sanitization within the DQL query parser, where an unauthenticated attacker can inject arbitrary query blocks into the cond field of an upsert mutation. The lack of parameterization allows the injected query to execute server-side and return sensitive data in the HTTP response.

Business Impact

The ability for an unauthenticated user to retrieve the entire contents of a database represents a catastrophic security failure. Given the CVSS score of 9.1, this vulnerability poses an extreme risk of mass data exfiltration, regulatory non-compliance, and severe reputational damage to any organization utilizing Dgraph in its default configuration.

Remediation Plan

Immediate Action: Upgrade all Dgraph instances to version 25.3.3 or later immediately to resolve the query injection flaw.

Proactive Monitoring: Review access logs for suspicious HTTP POST requests directed to the /mutate endpoint, specifically looking for anomalous cond field values.

Compensating Controls: Implement strict network access controls to limit access to the Dgraph API and ensure that Access Control Lists (ACLs) are enabled and configured to prevent unauthorized operations.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Apr 24, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The severity of this vulnerability cannot be overstated, as it provides an unauthenticated path to total data exposure. Organizations must prioritize upgrading their Dgraph installations to version 25.3.3 immediately and audit their current configuration to ensure ACLs are properly enforced.

---METADATA---
VENDOR: NLnet Labs
PRODUCT: Unbound
AFFECTED_VERSIONS: 0 up to (excluding) 1.25.1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A resource exhaustion vulnerability in NLnet Labs Unbound allows for denial-of-service via inefficient algorithmic complexity and improper resource throttling.

Executive Summary:
A denial-of-service vulnerability in NLnet Labs Unbound allows remote, unauthenticated attackers to cause resource exhaustion.

Vulnerability Details

CVE-ID: CVE-2026-41292

Affected Software: NLnet Labs Unbound

Affected Versions: 0 up to (excluding) 1.25.1

Vulnerability: The software is susceptible to resource exhaustion (CWE-407/CWE-770) due to inefficient algorithmic complexity, allowing an unauthenticated remote attacker to trigger excessive resource consumption.

Business Impact

Successful exploitation results in a denial-of-service, rendering the DNS resolver unresponsive. With a CVSS score of 7.5 and the ability to be triggered remotely by unauthenticated attackers, this represents a high risk to network availability and service continuity for any infrastructure relying on Unbound for DNS resolution.

Remediation Plan

Immediate Action: Update NLnet Labs Unbound to version 1.25.1 or later to implement the necessary resource limits and algorithmic fixes.

Proactive Monitoring: Monitor DNS resolver performance metrics, specifically CPU and memory utilization, for spikes that could indicate an ongoing denial-of-service attempt.

Compensating Controls: Use rate-limiting at the network perimeter to throttle excessive incoming DNS traffic, potentially reducing the impact of a DoS attempt while patching is underway.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 21, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its remote, unauthenticated nature.

Analyst Recommendation

Due to the critical role of DNS in network operations and the remote exploitability of this flaw, immediate patching is required. Organizations should prioritize updating all instances of Unbound to version 1.25.1 to ensure continued service availability and to mitigate the risk of remote service disruption.

---METADATA---
VENDOR: OpenStack
PRODUCT: Mistral
AFFECTED_VERSIONS: OpenStack Mistral through 22.0.0.
---END_METADATA---

Description Summary:
OpenStack Mistral allows arbitrary remote code execution via exposed API endpoints, potentially leading to the exfiltration of sensitive service credentials.

Executive Summary:
A critical remote code execution vulnerability in OpenStack Mistral allows unauthenticated attackers to execute arbitrary commands and exfiltrate sensitive credentials.

Vulnerability Details

CVE-ID: CVE-2026-41283

Affected Software: OpenStack Mistral

Affected Versions: OpenStack Mistral through 22.0.0.

Vulnerability: The vulnerability exists in the API endpoints of OpenStack Mistral, which do not properly sanitize input or restrict execution, allowing an unauthenticated remote attacker to execute arbitrary code. This flaw provides a vector for attackers to compromise service credentials and gain broader control over the OpenStack environment.

Business Impact

With a CVSS score of 9.9, this vulnerability represents an extremely high risk. Successful exploitation can lead to a complete compromise of the OpenStack environment, resulting in data breaches, unauthorized access to cloud resources, and catastrophic loss of service integrity.

Remediation Plan

Immediate Action: Upgrade OpenStack Mistral to version 23.0.0 or later immediately to resolve the vulnerable API endpoints.

Proactive Monitoring: Review API access logs for unusual activity or requests directed at sensitive Mistral endpoints that could indicate exploitation.

Compensating Controls: Restrict access to the Mistral API service to trusted internal networks only, using firewalls or VPNs, until the patch can be applied.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Jun 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the critical nature of this RCE and its potential impact on cloud infrastructure, immediate patching is required. Organizations running OpenStack Mistral should prioritize this update to prevent unauthorized administrative access to their cloud platforms.