Search and filter 21637 vulnerabilities with AI analyst insights
SocialEngine versions 7
SocialEngine versions 7
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
SocialEngine versions 7.8.0 and prior contain a SQL injection vulnerability in the /activity/index/get-memberall endpoint where user-supplied input pa...
SocialEngine versions 7.8.0 and prior contain a SQL injection vulnerability in the /activity/index/get-memberall endpoint where user-supplied input passed via the text parameter is not sanitized before being incorporated into a SQL query. An unauthenticated remote attacker can exploit this vulnerability to read arbitrary data from the database, reset administrator account passwords, and gain unauthorized access to the Packages Manager in the Admin Panel, potentially enabling remote code execution.
Update SocialEngine Multiple Products to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
WeKan before 8
WeKan before 8
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
WeKan before 8
WeKan before 8
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Krayin CRM before 2
Krayin CRM before 2
---METADATA---
VENDOR: Krayin
PRODUCT: Laravel CRM
AFFECTED_VERSIONS: 0 up to (excluding) 2.2.4
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
Krayin Laravel CRM is vulnerable to SQL injection via the lead datagrid, allowing authenticated attackers to execute arbitrary SQL commands.
Executive Summary:
A SQL injection vulnerability in Krayin Laravel CRM allows authenticated attackers to manipulate database queries and potentially access sensitive information.
Vulnerability Details
CVE-ID: CVE-2026-41453
Affected Software: Krayin Laravel CRM
Affected Versions: 0 up to (excluding) 2.2.4
Vulnerability: The application fails to properly neutralize special elements used in SQL commands (CWE-89) within the lead datagrid functionality. This allows an authenticated user to perform blind SQL injection by injecting malicious payloads into the rotten lead parameter.
Business Impact
Successful exploitation allows an attacker to extract sensitive data from the underlying database, bypass authentication, or modify application data. With a CVSS score of 8.8, this vulnerability represents a significant risk to the confidentiality and integrity of customer relationship data managed within the CRM.
Remediation Plan
Immediate Action: Update Krayin Laravel CRM to version 2.2.4 or later to remediate the SQL injection flaw.
Proactive Monitoring: Review database query logs for suspicious patterns, such as unexpected use of SQL keywords or syntax errors in query strings.
Compensating Controls: Deploy a Web Application Firewall (WAF) with SQL injection protection rules to block malicious requests targeting the vulnerable lead datagrid parameter.
Exploitation Status
Public Exploit Available: unknown
Analyst Notes: As of August 4, 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 vulnerability is highly exploitable via common web request manipulation techniques.
Analyst Recommendation
Given the existence of a proof-of-concept and the high severity of SQL injection, organizations should prioritize updating their CRM instances to version 2.2.4. Failure to patch may expose critical business data to unauthorized access.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A missing authentication vulnerability in the Krayin CRM installer middleware allows unauthenticated remote attackers to overwrite the administrator a...
A missing authentication vulnerability in the Krayin CRM installer middleware allows unauthenticated remote attackers to overwrite the administrator account and gain full CRM access.
---METADATA---
VENDOR: krayin
PRODUCT: laravel-crm
AFFECTED_VERSIONS: 0 through 2.2.0, 2.2.4
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A missing authentication vulnerability in the Krayin CRM installer middleware allows unauthenticated remote attackers to overwrite the administrator account and gain full CRM access.
Executive Summary:
A critical authentication bypass in Krayin CRM allows unauthenticated attackers to perform an account takeover of the primary administrator profile.
Vulnerability Details
CVE-ID: CVE-2026-41452
Affected Software: krayin laravel-crm
Affected Versions: 0 through 2.2.0, 2.2.4
Vulnerability: The vulnerability exists in the installer middleware, where a flaw in the CanInstall redirect check allows attackers to bypass authentication. By sending a crafted HTTP POST request with a specific header, an attacker can access the admin-config-setup endpoint to overwrite the primary administrator credentials.
Business Impact
Successful exploitation grants an attacker full administrative access to the CRM platform. This results in the potential loss of sensitive customer data, unauthorized configuration changes, and complete compromise of business information stored within the application. Given the CVSS score of 9.8, this vulnerability is critical as it completely invalidates the security model of the CRM.
Remediation Plan
Immediate Action: Update krayin laravel-crm to a patched version (specifically those outside the range of 2.2.0 through 2.2.4, such as 2.2.1 through 2.2.3 if applicable per vendor guidance).
Proactive Monitoring: Audit user account logs for unexpected changes to the administrator account and monitor for unauthorized access to the admin-config-setup endpoint.
Compensating Controls: Deploy a Web Application Firewall (WAF) to block requests containing the X-Requested-With: XMLHttpRequest header directed at the installer endpoints.
Exploitation Status
Public Exploit Available: Yes, a public proof-of-concept exists via security research write-ups.
Analyst Notes: As of August 3, 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 vulnerability is highly severe because it allows for immediate, unauthenticated account takeover.
Analyst Recommendation
This is a critical security vulnerability that directly threatens the integrity and confidentiality of the CRM database. Administrators should verify their current version and apply the vendor-recommended patches immediately to prevent unauthorized administrative account creation and potential data breaches.
Update krayin laravel-crm to the latest version. Check the vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
During an internal security assessment, a potential vulnerability was discovered in Lenovo Software Fix that could allow a local authenticated user to...
During an internal security assessment, a potential vulnerability was discovered in Lenovo Software Fix that could allow a local authenticated user to perform arbitrary code execution with elevated privileges
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
FirmaCheck for Windows before 1
FirmaCheck for Windows before 1
---METADATA---
VENDOR: Zucchetti S.p.a.
PRODUCT: FirmaCheck
AFFECTED_VERSIONS: 0 up to (excluding) 1.3.16
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
FirmaCheck for Windows is vulnerable to DLL hijacking due to an untrusted search path, which could allow local attackers to execute arbitrary code.
Executive Summary:
An untrusted search path vulnerability in Zucchetti FirmaCheck allows local attackers to perform DLL hijacking and gain unauthorized code execution.
Vulnerability Details
CVE-ID: CVE-2026-41447
Affected Software: Zucchetti S.p.a. FirmaCheck
Affected Versions: 0 up to (excluding) 1.3.16
Vulnerability: This vulnerability is a classic untrusted search path issue (CWE-426) where the application improperly validates the path used to load libraries. An authenticated local attacker can leverage this flaw to execute arbitrary code with the privileges of the application.
Business Impact
Exploitation of this vulnerability allows a local user to escalate privileges or execute malicious code within the context of the FirmaCheck application. With a CVSS score of 7.8, this poses a significant risk to the integrity and security of local workstations, potentially facilitating further attacks on the internal network.
Remediation Plan
Immediate Action: Update FirmaCheck to version 1.3.16 or later to ensure proper validation of library search paths.
Proactive Monitoring: Review system logs for unauthorized file access or the loading of unsigned DLLs by the FirmaCheck process.
Compensating Controls: Restrict local user permissions to write to application directories and use Endpoint Detection and Response (EDR) tools to identify suspicious process execution patterns.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of August 4, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherently exploitable by any local user with the ability to place a malicious DLL in the application's search path.
Analyst Recommendation
Organizations utilizing FirmaCheck on Windows workstations must prioritize this update to prevent local privilege escalation. Administrators should verify the installation of version 1.3.16 across all endpoints to mitigate this high-severity risk.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
KissFFT before commit 8a8e66e contains an integer overflow vulnerability in the kiss_fftndr_alloc() function in kiss_fftndr
KissFFT before commit 8a8e66e contains an integer overflow vulnerability in the kiss_fftndr_alloc() function in kiss_fftndr
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard
OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard
---METADATA---
VENDOR: OpenTelemetry
PRODUCT: eBPF Instrumentation
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---
Description Summary:
The OpenTelemetry eBPF Instrumentation tool is affected by a high-severity security vulnerability that could threaten the integrity of system-level observability.
Executive Summary:
A high-severity vulnerability in OpenTelemetry eBPF Instrumentation could allow for unauthorized system-level impacts due to its privileged nature.
Vulnerability Details
CVE-ID: CVE-2026-41433
Affected Software: OpenTelemetry eBPF Instrumentation
Affected Versions: See vendor advisory for affected versions
Vulnerability: This vulnerability affects the eBPF instrumentation component, which runs at a high-privilege level within the kernel or system space. The CVSS score of 8.4 suggests a critical risk related to improper handling of eBPF programs or data, potentially leading to privilege escalation or kernel-level instability.
Business Impact
A CVSS score of 8.4 indicates a high risk to infrastructure security. Since eBPF tools operate with elevated privileges, exploitation could allow an attacker to bypass security controls, monitor kernel-level activities, or disrupt system observability, leading to significant operational risks.
Remediation Plan
Immediate Action: Update the OpenTelemetry eBPF Instrumentation agent to the latest version as recommended by the vendor.
Proactive Monitoring: Monitor system logs for unusual kernel activity or errors related to eBPF program loading and execution.
Compensating Controls: Restrict access to the observability platform and ensure only authorized personnel can deploy or modify eBPF instrumentation.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of April 26, 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
Security teams should prioritize updating observability tools that utilize eBPF. Given the privileged nature of this software, vulnerabilities must be addressed immediately to prevent kernel-level compromises.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system
New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system
---METADATA---
VENDOR: New API
PRODUCT: New API
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
New API, an LLM gateway and AI asset management system, contains an unspecified vulnerability that may impact system security.
Executive Summary:
A security vulnerability in the New API LLM gateway and AI asset management system requires immediate attention to prevent potential exploitation.
Vulnerability Details
CVE-ID: CVE-2026-41432
Affected Software: New API
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability affects New API, a gateway for large language models and AI asset management. The specific nature of the flaw is currently being tracked and requires verification through vendor documentation.
Business Impact
With a CVSS score of 7.1, this vulnerability is rated as High. It indicates that the AI management system could be leveraged to gain unauthorized access or manipulate AI assets, potentially leading to data leakage or the corruption of AI-driven workflows.
Remediation Plan
Immediate Action: Apply vendor-provided security updates immediately upon release.
Proactive Monitoring: Monitor API logs for unusual access patterns, unexpected model requests, or configuration changes within the AI management dashboard.
Compensating Controls: Implement strict API key management and ensure that the New API gateway is protected by network-level access controls.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of May 10, 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
Organizations deploying AI gateways must maintain rigorous update cycles. Consult the vendor's security advisory to confirm the specific impact and ensure all necessary patches are applied to safeguard your AI infrastructure.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Zen is a firefox-based browser
Zen is a firefox-based browser
---METADATA---
VENDOR: Zen Browser
PRODUCT: Zen Browser
AFFECTED_VERSIONS: < 1.19.9b
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
Zen Browser contains a vulnerability in its release pipeline related to the improper verification of cryptographic signatures, which could allow for the execution of unauthorized or malicious code.
Executive Summary:
A vulnerability in the Zen Browser release pipeline allows for improper cryptographic signature verification, creating a risk of unauthorized code execution.
Vulnerability Details
CVE-ID: CVE-2026-41431
Affected Software: Zen Browser desktop
Affected Versions: < 1.19.9b
Vulnerability: This vulnerability stems from improper verification of cryptographic signatures during the release process, which may allow an attacker with high privileges to compromise the integrity of the browser installation.
Business Impact
A CVSS score of 8.0 indicates a high risk to the software's integrity. If an attacker can successfully bypass signature verification, they could potentially distribute malicious updates or payloads, leading to full browser compromise and potential data theft for end-users.
Remediation Plan
Immediate Action: Update Zen Browser to version 1.19.9b or later to ensure proper cryptographic signature verification is enforced.
Proactive Monitoring: Monitor for any anomalies in browser update processes and ensure that only official, signed binaries are deployed to workstations.
Compensating Controls: Utilize endpoint security solutions to block the execution of unsigned or improperly signed binaries on systems where Zen Browser is deployed.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of May 13, 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 vulnerability effectively undermines the security trust model of the software update mechanism.
Analyst Recommendation
This vulnerability represents a significant risk to the supply chain of the browser. Organizations must prioritize upgrading to the latest version to ensure that cryptographic integrity checks are functioning correctly, preventing the potential installation of unauthorized code.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
arduino-esp32 is an Arduino core for the ESP32, ESP32-S2, ESP32-S3, ESP32-C3, ESP32-C6 and ESP32-H2 microcontrollers
arduino-esp32 is an Arduino core for the ESP32, ESP32-S2, ESP32-S3, ESP32-C3, ESP32-C6 and ESP32-H2 microcontrollers
---METADATA---
VENDOR: Espressif Systems
PRODUCT: arduino-esp32
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---
Description Summary:
The arduino-esp32 core, used for various ESP32 microcontrollers, contains an unspecified high-severity vulnerability requiring urgent security review.
Executive Summary:
A high-severity vulnerability exists in the arduino-esp32 core, potentially impacting the security posture of devices utilizing ESP32, ESP32-S, and ESP32-C series microcontrollers.
Vulnerability Details
CVE-ID: CVE-2026-41429
Affected Software: Espressif Systems arduino-esp32
Affected Versions: See vendor advisory for affected versions
Vulnerability: This vulnerability affects the Arduino development framework for ESP32 microcontrollers. While specific technical details are currently limited, the high CVSS score of 8.8 suggests a significant risk, likely involving memory corruption or privilege escalation within the microcontroller's runtime.
Business Impact
A CVSS score of 8.8 indicates a high risk of system compromise. In an IoT or industrial context, exploitation could lead to unauthorized control over microcontrollers, potentially disrupting critical operations or allowing attackers to intercept data transmitted by connected sensors and devices.
Remediation Plan
Immediate Action: Monitor the official Espressif Systems and Arduino GitHub repositories for security advisories and apply the latest firmware or library core updates as they become available.
Proactive Monitoring: Audit device logs and network traffic for anomalous behavior originating from ESP32-based devices, which may indicate attempted exploitation.
Compensating Controls: Isolate IoT devices on segmented networks to limit the potential impact if a device is compromised via this vulnerability.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of April 26, 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 broad deployment of ESP32 microcontrollers, IT teams should inventory all devices using the arduino-esp32 core. Apply vendor-provided patches as soon as they are released to mitigate the risk of remote compromise.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Budibase contains an authentication bypass vulnerability where unanchored regular expressions allow attackers to access protected endpoints via crafte...
Budibase contains an authentication bypass vulnerability where unanchored regular expressions allow attackers to access protected endpoints via crafted query strings.
---METADATA---
VENDOR: Budibase
PRODUCT: Budibase
AFFECTED_VERSIONS: Prior to 3.35.4
---END_METADATA---
Description Summary:
Budibase contains an authentication bypass vulnerability where unanchored regular expressions allow attackers to access protected endpoints via crafted query strings.
Executive Summary:
An authentication bypass vulnerability in Budibase allows unauthenticated attackers to access restricted endpoints, posing a severe risk to data confidentiality and integrity.
Vulnerability Details
CVE-ID: CVE-2026-41428
Affected Software: Budibase
Affected Versions: Prior to 3.35.4
Vulnerability: The application utilizes unanchored regular expressions in its middleware to validate request URLs. Attackers can leverage this to bypass authentication by appending a public endpoint path as a query parameter, effectively tricking the system into granting unauthorized access.
Business Impact
With a CVSS score of 9.1, this vulnerability is critical as it allows for the complete compromise of administrative and system-level functions. Unauthorized access could lead to the exposure of sensitive platform data, modification of user accounts, or full system takeover, resulting in significant operational disruption and loss of trust.
Remediation Plan
Immediate Action: Upgrade Budibase to version 3.35.4 or later immediately to implement the corrected regex anchoring logic.
Proactive Monitoring: Review web server access logs for anomalous requests containing suspicious query parameters that mimic internal API paths.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules designed to inspect and filter query strings for unauthorized path traversal or API endpoint manipulation patterns.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of April 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 authentication bypass cannot be overstated, as it effectively removes the primary security barrier for the platform. Administrators must prioritize the patch application in all production instances of Budibase to prevent unauthorized lateral movement and data exfiltration.
Update Arch Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Daptin is a GraphQL/JSON-API headless CMS
Daptin is a GraphQL/JSON-API headless CMS
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
SiYuan is an open-source personal knowledge management system
SiYuan is an open-source personal knowledge management system
---METADATA---
VENDOR: SiYuan
PRODUCT: SiYuan
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---
Description Summary:
SiYuan, an open-source personal knowledge management system, is affected by a high-severity vulnerability that could lead to unauthorized access or system compromise.
Executive Summary:
A security vulnerability in the SiYuan knowledge management system poses a high risk to the confidentiality and integrity of stored personal data.
Vulnerability Details
CVE-ID: CVE-2026-41421
Affected Software: SiYuan
Affected Versions: See vendor advisory for affected versions
Vulnerability: This vulnerability affects SiYuan, an open-source knowledge management platform. With a CVSS score of 8.8, the flaw likely involves improper authentication or input validation, potentially allowing an attacker to access user data or gain unauthorized control over the local instance.
Business Impact
The high CVSS score of 8.8 suggests a significant risk to users and organizations utilizing SiYuan. Successful exploitation could result in the unauthorized disclosure of sensitive knowledge bases, personal notes, or proprietary information stored within the system.
Remediation Plan
Immediate Action: Update SiYuan to the latest version released by the vendor to address the identified security flaw.
Proactive Monitoring: Audit access logs for the SiYuan application to identify any suspicious login attempts or unauthorized access to notes.
Compensating Controls: Ensure that the SiYuan instance is not exposed directly to the public internet and use VPN or proxy access to restrict exposure.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of April 26, 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
Users and administrators of SiYuan should check the project's official security pages and apply updates immediately. Given the nature of knowledge management software, protecting the confidentiality of stored data should be the highest priority.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
4ga Boards is a boards system for realtime project management
4ga Boards is a boards system for realtime project management
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Skim is a fuzzy finder designed to through files, lines, and commands
Skim is a fuzzy finder designed to through files, lines, and commands
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized w...
The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a static initializer in a class to be read might already have been executed. Affected versions are Apache MINA 2.0.0 <= 2.0.27, 2.1.0 <= 2.1.10, and 2.2.0 <= 2.2.5. The problem is resolved in Apache MINA 2.0.28, 2.1.11, and 2.2.6 by applying the classname allowlist earlier. Affected are applications using Apache MINA that call IoBuffer.getObject(). Applications using Apache MINA are advised to upgrade
---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.
Update Apache MINA AbstractIoBuffer to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A privilege escalation vulnerability in OpenClaw during device pairing allows attackers to gain unauthorized access by manipulating device roles.
A privilege escalation vulnerability in OpenClaw during device pairing allows attackers to gain unauthorized access by manipulating device roles.
---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.
Update OpenClaw Multiple Products to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
In mlflow/mlflow versions prior to 3
In mlflow/mlflow versions prior to 3
---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.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenShell before 2026
OpenShell before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
During an internal security assessment, a potential vulnerability was discovered in Lenovo Software Fix, that during installation could allow a local...
During an internal security assessment, a potential vulnerability was discovered in Lenovo Software Fix, that during installation could allow a local authenticated user to execute code with elevated privileges
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026.3.31 contains a sandbox bypass vulnerability allowing attackers to escalate privileges via heartbeat context inheritance and send...
OpenClaw before 2026.3.31 contains a sandbox bypass vulnerability allowing attackers to escalate privileges via heartbeat context inheritance and senderIsOwner parameter manipulation. Attackers can exploit improper context validation to bypass sandbox restrictions and achieve unauthorized privilege escalation.
---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.
Update OpenClaw Multiple Products to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
Dgraph is an open source distributed GraphQL database. Prior to 25.3.3, a vulnerability has been found in Dgraph that gives an unauthenticated attacke...
Dgraph is an open source distributed GraphQL database. Prior to 25.3.3, a vulnerability has been found in Dgraph that gives an unauthenticated attacker full read access to every piece of data in the database. This affects Dgraph's default configuration where ACL is not enabled. The attack requires two HTTP POSTs to port 8080. The first sets up a schema predicate with @unique @index(exact) @lang via /alter (also unauthenticated in default config). The second sends a crafted JSON mutation to /mutate?commitNow=true where a JSON key contains the predicate name followed by @ and a DQL injection payload in the language tag position. The injection exploits the addQueryIfUnique function in edgraph/server.go, which constructs DQL queries using fmt.Sprintf with unsanitized predicateName that includes the raw pred.Lang value. The Lang field is extracted from JSON mutation keys by x.PredicateLang(), which splits on @, and is never validated by any function in the codebase. The attacker injects a closing parenthesis to escape the eq() function, adds an arbitrary named query block, and uses a # comment to neutralize trailing template syntax. The injected query executes server-side and its results are returned in the HTTP response. This vulnerability is fixed in 25.3.3.
---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.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Dgraph is an open source distributed GraphQL database. Prior to 25.3.3, a vulnerability has been found in Dgraph that gives an unauthenticated attacke...
Dgraph is an open source distributed GraphQL database. Prior to 25.3.3, a vulnerability has been found in Dgraph that gives an unauthenticated attacker full read access to every piece of data in the database. This affects Dgraph's default configuration where ACL is not enabled. The attack is a single HTTP POST to /mutate?commitNow=true containing a crafted cond field in an upsert mutation. The cond value is concatenated directly into a DQL query string via strings.Builder.WriteString after only a cosmetic strings.Replace transformation. No escaping, parameterization, or structural validation is applied. An attacker injects an additional DQL query block into the cond string, which the DQL parser accepts as a syntactically valid named query block. The injected query executes server-side and its results are returned in the HTTP response. This vulnerability is fixed in 25.3.3.
---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.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
basic-ftp is an FTP client for Node
basic-ftp is an FTP client for Node
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Kyverno is a policy engine designed for cloud native platform engineering teams
Kyverno is a policy engine designed for cloud native platform engineering teams
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The HTTP Headers plugin for WordPress is vulnerable to External Control of File Name or Path leading to Remote Code Execution in all versions up to an...
The HTTP Headers plugin for WordPress is vulnerable to External Control of File Name or Path leading to Remote Code Execution in all versions up to and including 1
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
ERB is a templating system for Ruby
ERB is a templating system for Ruby
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
---METADATA---
VENDOR: SocialEngine
PRODUCT: Multiple Products
AFFECTED_VERSIONS: 7.8.0 and prior
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
SocialEngine versions 7.8.0 and prior contain a SQL injection vulnerability in the activity module, allowing unauthenticated attackers to gain unauthorized access to the administrative panel.
Executive Summary:
An unauthenticated SQL injection vulnerability in SocialEngine versions 7.8.0 and prior allows attackers to compromise administrative accounts and potentially execute remote code.
Vulnerability Details
CVE-ID: CVE-2026-41460
Affected Software: SocialEngine, Multiple Products
Affected Versions: 7.8.0 and prior
Vulnerability: This is a SQL injection vulnerability within the
/activity/index/get-memberallendpoint, where insufficient sanitization of thetextparameter allows unauthenticated remote attackers to execute arbitrary SQL queries against the database.Business Impact
Successful exploitation allows an attacker to bypass authentication, extract sensitive database information, reset administrator credentials, and potentially gain access to the Packages Manager. With a CVSS score of 9.8, this vulnerability poses a critical risk to data integrity and system availability, as the resulting administrative access could lead to full remote code execution.
Remediation Plan
Immediate Action: Update all SocialEngine instances to the latest version as provided by the vendor to ensure the SQL injection vulnerability is patched.
Proactive Monitoring: Review database query logs for suspicious SQL syntax and monitor access logs for unauthorized attempts to reach the Admin Panel or the
get-memberallendpoint.Compensating Controls: Utilize a Web Application Firewall (WAF) configured with rules to detect and block common SQL injection patterns in HTTP requests.
Exploitation Status
Public Exploit Available: Not specified
Analyst Notes: As of Apr 23, 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 is highly critical due to the potential for full administrative takeover. Security teams should prioritize patching to the latest version immediately, as the attack vector is accessible to unauthenticated users and the impact is severe.