---METADATA---
VENDOR: Open WebUI
PRODUCT: Open WebUI
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability has been identified in the Open WebUI platform, an AI interface designed for self-hosted, offline environments.

Executive Summary:
A high-severity vulnerability in the Open WebUI platform exposes self-hosted AI services to potential security compromises.

Vulnerability Details

CVE-ID: CVE-2026-44553

Affected Software: Open WebUI

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the security posture of the Open WebUI platform, potentially allowing for unauthorized exploitation of its internal components.

Business Impact

With a CVSS score of 8.1, this vulnerability presents a serious threat to the security of the host environment. Organizations should treat this as a high-priority issue to prevent unauthorized access and potential data exfiltration from the AI platform.

Remediation Plan

Immediate Action: Actively monitor for and apply the latest security updates released by the vendor to remediate this vulnerability.

Proactive Monitoring: Maintain detailed logs of application access and monitor for unusual, high-frequency requests that may indicate an exploit attempt.

Compensating Controls: Ensure that the Open WebUI instance is running behind a secure gateway or proxy that can provide an additional layer of authentication and traffic inspection.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 16, 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 vulnerability poses a clear risk to the integrity of the Open WebUI platform. Administrators must act promptly to apply patches and ensure that security configurations are robust enough to defend against potential exploitation attempts.

---METADATA---
VENDOR: Open WebUI
PRODUCT: Open WebUI
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A vulnerability exists in Open WebUI that may allow for unauthorized access or system impact.

Executive Summary:
Open WebUI contains a security vulnerability that could potentially lead to unauthorized access or compromise of the platform.

Vulnerability Details

CVE-ID: CVE-2026-44552

Affected Software: Open WebUI

Affected Versions: See vendor advisory for affected versions

Vulnerability: The specific technical nature of this vulnerability is currently being addressed by the vendor; users should consult official documentation for the exact mechanism of compromise.

Business Impact

The CVSS score of 8.7 indicates a high-severity risk that could lead to significant unauthorized access or disruption of services, necessitating prompt attention from security teams.

Remediation Plan

Immediate Action: Apply the latest security patches provided by the vendor as soon as they become available.

Proactive Monitoring: Audit access logs for suspicious activity or patterns that deviate from normal user behavior.

Compensating Controls: Implement strict network access controls to minimize the attack surface of the Open WebUI instance.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 16, 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 stay vigilant and apply the vendor-provided patches as soon as they are published to mitigate the risk associated with this vulnerability.

---METADATA---
VENDOR: Open WebUI
PRODUCT: Open WebUI
AFFECTED_VERSIONS: Prior to 0.9.0
---END_METADATA---

Description Summary:
The LDAP authentication endpoint in Open WebUI fails to validate non-empty passwords, allowing unauthenticated attackers to bypass authentication and obtain session tokens.

Executive Summary:
An authentication bypass vulnerability in Open WebUI allows unauthenticated attackers to gain unauthorized access to the platform via empty LDAP password submissions.

Vulnerability Details

CVE-ID: CVE-2026-44551

Affected Software: Open WebUI

Affected Versions: Prior to 0.9.0

Vulnerability: This is an authentication bypass vulnerability occurring in the LDAP bind process; the application fails to enforce a minimum length constraint on the password field, permitting an unauthenticated attacker to successfully bind as an arbitrary user.

Business Impact

Successful exploitation leads to full account takeover, granting attackers unauthorized access to sensitive AI data and administrative functions. With a CVSS score of 9.1, this represents a critical risk to data confidentiality and integrity.

Remediation Plan

Immediate Action: Upgrade the Open WebUI instance to version 0.9.0 or later to ensure proper LDAP password validation.

Proactive Monitoring: Review LDAP authentication logs for patterns of unusual bind requests or successful logins with anomalous user-agent strings.

Compensating Controls: Implement network-level restrictions to limit access to the login interface to trusted IP ranges until the patch can be applied.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 15, 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 severity of this authentication bypass, administrators must prioritize the update to version 0.9.0 immediately. Failure to patch leaves the platform vulnerable to trivial account takeover by unauthenticated remote actors.

---METADATA---
VENDOR: Open WebUI
PRODUCT: Open WebUI
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
Open WebUI, a self-hosted AI platform, contains a high-severity vulnerability that requires immediate remediation through vendor-issued security updates.

Executive Summary:
A high-severity security vulnerability in the Open WebUI platform could allow unauthorized access, requiring immediate attention to secure the environment.

Vulnerability Details

CVE-ID: CVE-2026-44549

Affected Software: Open WebUI

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This high-severity vulnerability affects the Open WebUI platform, with technical details currently subject to vendor disclosure and patch availability.

Business Impact

A CVSS score of 7.3 indicates that successful exploitation could result in significant security breaches, including unauthorized access to internal AI tools or sensitive information. This poses a threat to both operational continuity and data security.

Remediation Plan

Immediate Action: Monitor vendor security advisories and apply the latest patches for Open WebUI immediately upon release.

Proactive Monitoring: Regularly audit user access and system configurations to detect any signs of exploitation.

Compensating Controls: Use network access controls to restrict connections to the Open WebUI server to known, trusted IP addresses only.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of May 17, 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 must prioritize the remediation of this vulnerability. Ensure all instances of Open WebUI are accounted for and updated promptly once the vendor provides the necessary security patches.

---METADATA---
VENDOR: ChurchCRM
PRODUCT: ChurchCRM
AFFECTED_VERSIONS: 7.2.0 through 7.2.2
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
ChurchCRM versions 7.2.0 to 7.2.2 contain an incomplete authentication fix, leaving the application vulnerable to unauthorized access due to a missing critical security check.

Executive Summary:
An incomplete authentication patch in ChurchCRM 7.2.x allows unauthenticated attackers to bypass security controls and gain unauthorized access to the application.

Vulnerability Details

CVE-ID: CVE-2026-44547

Affected Software: ChurchCRM

Affected Versions: 7.2.0, 7.2.1, 7.2.2

Vulnerability: The vulnerability stems from a missing critical authentication step that was inadvertently removed from the codebase during a merge process. This allows unauthenticated users to bypass security measures and interact with sensitive API functions.

Business Impact

With a CVSS score of 9.6, this flaw represents a major security risk, potentially allowing unauthorized access to sensitive member databases and administrative functions. Successful exploitation could lead to data breaches, unauthorized data modification, and complete loss of application integrity.

Remediation Plan

Immediate Action: Upgrade to ChurchCRM version 7.3.1 or later to ensure the authentication hardening is properly implemented.

Proactive Monitoring: Review application access logs for suspicious API requests originating from unauthorized or unknown IP addresses.

Compensating Controls: Implement strict network-level access controls (VPN or IP allowlisting) to restrict access to the CRM interface until the software is updated.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of May 12, 2026, there is a public proof-of-concept available for this vulnerability. Security teams must treat this as a high-priority issue as the barrier to entry for attackers is significantly lowered by the availability of exploit code.

Analyst Recommendation

Administrators should move immediately to update ChurchCRM to version 7.3.1. The presence of a public exploit significantly increases the risk of successful exploitation, making prompt remediation essential to preventing unauthorized access to sensitive organizational data.

---METADATA---
VENDOR: Kubernetes
PRODUCT: Local Path Provisioner
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability in the Kubernetes Local Path Provisioner may allow users to gain unauthorized access to local storage nodes.

Executive Summary:
A high-severity vulnerability in the Kubernetes Local Path Provisioner potentially allows for unauthorized local storage access, compromising cluster security.

Vulnerability Details

CVE-ID: CVE-2026-44543

Affected Software: Kubernetes Local Path Provisioner

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability involves a flaw in how the provisioner handles storage capabilities, which could allow authenticated users to escape intended storage boundaries and access unauthorized local data on the node.

Business Impact

The CVSS score of 8.7 indicates a high risk to containerized environments. By exploiting this flaw, an attacker could potentially access sensitive data stored on host nodes that they are not authorized to reach, leading to data breaches or the corruption of critical system files, thereby violating the principle of least privilege.

Remediation Plan

Immediate Action: Update the Local Path Provisioner to the latest version that includes the necessary security fixes for storage capability management.

Proactive Monitoring: Audit Kubernetes PersistentVolumeClaim (PVC) requests and monitor for unauthorized or unusual storage mount activity within the cluster.

Compensating Controls: Implement strict Pod Security Admissions and ensure that storage access is governed by granular RBAC policies that limit the ability of users to interact with host-path storage.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 9, 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 potential for lateral movement and data access within a cluster, this update should be prioritized. Cluster administrators must evaluate their storage configurations and apply the necessary patches to maintain container isolation and cluster security.

---METADATA---
VENDOR: FileBrowser
PRODUCT: FileBrowser Quantum
AFFECTED_VERSIONS: Prior to 1.3.1-stable and 1.3.9-beta
---END_METADATA---

Description Summary:
A directory traversal vulnerability in FileBrowser Quantum allows unauthenticated attackers with share access to delete arbitrary files.

Executive Summary:
A critical directory traversal vulnerability in FileBrowser Quantum allows an unauthenticated attacker to delete arbitrary files on the host system.

Vulnerability Details

CVE-ID: CVE-2026-44542

Affected Software: FileBrowser Quantum

Affected Versions: Prior to 1.3.1-stable and 1.3.9-beta

Vulnerability: Improper sanitization of path input allows traversal sequences (e.g., ../) to escape intended directories, enabling unauthorized file deletion by an attacker with a valid public share hash.

Business Impact

This flaw allows for the malicious deletion of critical system or user files, potentially resulting in complete service disruption or data loss. With a CVSS score of 9.1, this represents a severe threat to the availability and integrity of the managed file storage.

Remediation Plan

Immediate Action: Update FileBrowser Quantum to version 1.3.1-stable or 1.3.9-beta immediately.

Proactive Monitoring: Monitor file system access logs for deletion activities involving paths outside of designated shared directory structures.

Compensating Controls: Implement file system permissions at the OS level to restrict the service's ability to modify files outside of its intended scope, providing a defense-in-depth measure.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 14, 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 ability to delete arbitrary files is a high-impact risk. Organizations must apply the provided updates immediately to prevent malicious data destruction and maintain system stability.

---METADATA---
VENDOR: Note
PRODUCT: Note Mark
AFFECTED_VERSIONS: Prior to 0.19.4
---END_METADATA---

Description Summary:
The Note Mark application fails to enforce entropy or length requirements on JWT_SECRET configurations, significantly weakening authentication security.

Executive Summary:
A critical cryptographic weakness in Note Mark allows the use of insecurely short JWT secrets, making the authentication tokens vulnerable to brute-force attacks.

Vulnerability Details

CVE-ID: CVE-2026-44523

Affected Software: Note, Note Mark

Affected Versions: Prior to 0.19.4

Vulnerability: The application does not enforce minimum length or entropy for the JWT_SECRET. Secrets as short as one byte are accepted, allowing attackers to easily brute-force the secret and forge authentication tokens.

Business Impact

With a CVSS score of 10.0, this vulnerability represents an existential threat to the application's authentication mechanism. An attacker who successfully brute-forces the secret can gain full administrative privileges, leading to a complete compromise of user data and application integrity.

Remediation Plan

Immediate Action: Update Note Mark to version 0.19.4 or later and immediately rotate the JWT_SECRET to a long, cryptographically secure random string.

Proactive Monitoring: Monitor authentication logs for an unusual volume of failed login attempts or signs of forged token usage.

Compensating Controls: Limit access to the application configuration files and ensure the environment is hardened against unauthorized file access.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 14, 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 critical due to the trivial nature of the exploit and the severity of the impact. Organizations must update the software and rotate their secrets immediately to prevent unauthorized access and token forgery.

---METADATA---
VENDOR: elFinder
PRODUCT: elFinder
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
A vulnerability has been identified in the elFinder open-source web-based file manager, potentially impacting systems utilizing its JavaScript-based interface.

Executive Summary:
The elFinder web-based file manager is affected by a security vulnerability that could permit unauthorized access or manipulation of files within the web environment.

Vulnerability Details

CVE-ID: CVE-2026-44521

Affected Software: elFinder

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability affects the elFinder file manager, a tool written in JavaScript using jQuery UI. The specific nature of the flaw is currently unidentified, but it involves the core file management operations of the web interface.

Business Impact

Successful exploitation of a file management utility can result in unauthorized file access, data exfiltration, or complete system compromise via remote code execution. The CVSS score of 8.8 highlights the high severity, reflecting the high risk to business operations that rely on this software for data handling.

Remediation Plan

Immediate Action: Audit all instances of elFinder in the production environment and update to the latest version provided by the vendor.

Proactive Monitoring: Inspect web server access logs for unusual file operations or attempts to access directories outside of the intended scope of the file manager.

Compensating Controls: Utilize a Web Application Firewall (WAF) to filter suspicious requests targeted at file management endpoints and restrict access to the file manager via IP allowlisting.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 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

Web-based file managers are frequent targets for attackers seeking to gain a foothold in an environment. Administrators must treat this vulnerability with urgency and ensure that all instances of elFinder are isolated or updated to a secure version to prevent unauthorized file system manipulation.

---METADATA---
VENDOR: Zebra
PRODUCT: Zebra (Zcash node)
AFFECTED_VERSIONS: zebrad < 4.4.0, zebra-script < 6.0.0
---END_METADATA---

Description Summary:
Insufficient error handling in Zcash node Zebra's sighash computation allows for consensus splits between nodes.

Executive Summary:
A critical consensus vulnerability in the Zebra Zcash node software may lead to network splits and potential transaction validation failures.

Vulnerability Details

CVE-ID: CVE-2026-44497

Affected Software: Zebra Zcash node

Affected Versions: zebrad prior to 4.4.0; zebra-script prior to 6.0.0

Vulnerability: This is a consensus-level vulnerability involving improper error handling of invalid sighash types during signature validation, which allows an attacker to bypass intended rejection logic and potentially force a consensus split.

Business Impact

Successful exploitation poses a significant risk to the integrity of the Zcash node network, potentially leading to chain forks or denial-of-service for specific nodes. Given the CVSS score of 9.1, this flaw threatens the operational continuity of financial systems relying on Zebra nodes.

Remediation Plan

Immediate Action: Upgrade all instances of zebrad to version 4.4.0 and zebra-script to version 6.0.0 immediately.

Proactive Monitoring: Monitor node logs for synchronization errors or unexpected consensus-related warnings that deviate from standard operating parameters.

Compensating Controls: Ensure nodes are behind robust firewalls and restrict peer-to-peer connections to trusted, known entities only.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 8, 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 represents a significant risk to blockchain consensus integrity. Organizations running Zebra nodes must prioritize the update to the patched versions to prevent network-level disruption and ensure continued compatibility with the Zcash network.

---METADATA---
VENDOR: Axios
PRODUCT: Axios
AFFECTED_VERSIONS: From 1.0.0 to before 1.16.0
---END_METADATA---

Description Summary:
Axios is vulnerable to a Prototype Pollution attack that can be escalated into a full Man-in-the-Middle (MITM) attack.

Executive Summary:
A high-severity Prototype Pollution gadget in Axios can be leveraged to intercept and modify HTTP traffic, resulting in a full Man-in-the-Middle attack.

Vulnerability Details

CVE-ID: CVE-2026-44494

Affected Software: Axios

Affected Versions: From 1.0.0 to before 1.16.0

Vulnerability: This vulnerability is a Prototype Pollution 'Gadget' attack. It allows any Object.prototype pollution existing in the application's dependency tree to be escalated into a full Man-in-the-Middle (MITM) attack, enabling the interception, reading, and modification of HTTP traffic.

Business Impact

With a CVSS score of 8.7, this vulnerability poses a severe threat to the confidentiality and integrity of communications handled by applications using Axios. By enabling MITM attacks, an attacker can steal session cookies, credentials, or sensitive business data transmitted over the network, leading to significant reputational and financial damage.

Remediation Plan

Immediate Action: Update the Axios library to version 1.16.0 or higher across all development projects and production deployments.

Proactive Monitoring: Monitor network traffic for anomalous patterns or unexpected proxy redirects that could indicate active traffic interception.

Compensating Controls: Audit the application's dependency tree to identify and remediate other sources of Prototype Pollution that could serve as a trigger for this gadget.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of June 12, 2026, a public exploit is available for this vulnerability. While there is no specific confirmation of active exploitation in the wild, the presence of a public exploit significantly increases the risk level.

Analyst Recommendation

The ability to escalate prototype pollution into a full MITM attack makes this a high-priority update. Developers should immediately audit their dependency manifests and update Axios to version 1.16.0 to mitigate this critical risk.

---METADATA---
VENDOR: Axios
PRODUCT: Axios
AFFECTED_VERSIONS: Prior to 0.32.0 and 1.16.0
---END_METADATA---

Description Summary:
Axios fails to properly validate IPv4-mapped IPv6 addresses in its proxy bypass function, leading to potential SSRF.

Executive Summary:
An SSRF vulnerability in Axios allows attackers to bypass proxy configurations by exploiting improper handling of IPv4-mapped IPv6 addresses.

Vulnerability Details

CVE-ID: CVE-2026-44492

Affected Software: Axios

Affected Versions: Prior to 0.32.0 and 1.16.0

Vulnerability: The shouldBypassProxy function in Axios does not correctly recognize IPv4-mapped IPv6 addresses. This allows an attacker to bypass NO_PROXY settings, potentially leading to Server-Side Request Forgery (SSRF) and allowing unauthorized access to internal network resources.

Business Impact

With a CVSS score of 8.6, this vulnerability facilitates SSRF, which can allow an attacker to interact with internal services that are not exposed to the public internet. This could result in the unauthorized retrieval of internal data, internal service discovery, or the exploitation of other internal-only vulnerabilities, creating a significant risk to internal network security.

Remediation Plan

Immediate Action: Update the Axios library to version 1.16.0 or 0.32.0 to resolve the proxy bypass logic error.

Proactive Monitoring: Monitor server-side network logs for requests directed at internal IP addresses or services that should be shielded by proxy bypass configurations.

Compensating Controls: Implement strict firewall rules to ensure that application servers cannot initiate unauthorized connections to sensitive internal segments, regardless of proxy configuration.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of June 12, 2026, a public exploit is available for this vulnerability. While there is no specific confirmation of active exploitation in the wild, the presence of a public exploit significantly increases the risk level.

Analyst Recommendation

The potential for SSRF makes this a critical security concern for any environment relying on internal service segmentation. Organizations should update Axios to the recommended versions immediately and review their network egress policies to ensure internal resources are properly protected.

---METADATA---
VENDOR: Remix (RVF)
PRODUCT: RVF (Remix Validated Form)
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
The RVF (formerly Remix Validated Form) library contains a vulnerability that may impact form validation and state management within React applications.

Executive Summary:
A high-severity vulnerability in the RVF library for React applications may allow for insecure form validation or state management, posing a risk to application integrity.

Vulnerability Details

CVE-ID: CVE-2026-44483

Affected Software: RVF (Remix Validated Form)

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability impacts the RVF library, a tool used for form validation and state management in React. The lack of specific technical details prevents a granular assessment, but such flaws often involve improper sanitization or validation logic that could lead to data injection or unauthorized state manipulation.

Business Impact

Applications relying on RVF for data handling are at risk of input-based attacks. If the validation logic is bypassed, an attacker could inject malicious data into the application, potentially leading to cross-site scripting (XSS) or unauthorized data processing. The CVSS score of 8.2 indicates a high-risk scenario for web applications requiring robust data integrity.

Remediation Plan

Immediate Action: Update the RVF package to the latest version released by the vendor to ensure all known validation patches are integrated.

Proactive Monitoring: Review application logs for unusual form submissions or anomalous state changes that could indicate an attempt to bypass validation logic.

Compensating Controls: Implement strict server-side validation for all data submitted via forms, ensuring that the application does not rely solely on client-side or library-based validation.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 29, 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

Developers should prioritize updating the RVF library in their React projects to mitigate the risk of data injection or state manipulation. Always ensure that server-side validation remains the primary security control, regardless of the validation libraries used on the client-side.

---METADATA---
VENDOR: Discord
PRODUCT: Rich Presence (soundcloud-rpc)
AFFECTED_VERSIONS: Prior to 0.1.8
---END_METADATA---

Description Summary:
A vulnerability in the soundcloud-rpc Discord integration allows local command execution via malicious track metadata.

Executive Summary:
A critical vulnerability in the soundcloud-rpc integration for Discord allows remote attackers to achieve local command execution on the user's machine via manipulated track metadata.

Vulnerability Details

CVE-ID: CVE-2026-44482

Affected Software: Discord Rich Presence (soundcloud-rpc)

Affected Versions: Prior to 0.1.8

Vulnerability: The application incorrectly handles track metadata, rendering it as raw HTML within privileged Electron views. This allows an attacker to execute arbitrary code locally by crafting a track title with a malicious payload.

Business Impact

Successful exploitation results in full local command execution on the victim's machine, potentially compromising all data and credentials stored on the host. With a CVSS score of 9.6, this flaw poses a severe risk to endpoint security and user confidentiality.

Remediation Plan

Immediate Action: Update the soundcloud-rpc application to version 0.1.8 or later.

Proactive Monitoring: Monitor for unexpected child processes spawned by the Electron-based application.

Compensating Controls: Restrict application permissions where possible and ensure the endpoint is protected by robust EDR solutions.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 14, 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 of the soundcloud-rpc integration should update immediately to mitigate the risk of remote code execution. Given the impact on the local operating system, this update should be treated with high urgency.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: prior to 146.0.7680.153
---END_METADATA---

Description Summary:
Google Chrome contains an inappropriate implementation in the V8 JavaScript engine that allows remote code execution via a crafted HTML page.

Executive Summary:
A critical vulnerability in the V8 engine of Google Chrome allows remote attackers to execute arbitrary code within a sandboxed environment.

Vulnerability Details

CVE-ID: CVE-2026-4447

Affected Software: Google Chrome

Affected Versions: prior to 146.0.7680.153

Vulnerability: This is an inappropriate implementation vulnerability in the V8 JavaScript engine. A remote attacker can trigger this flaw by enticing a user to visit a specially crafted HTML page, leading to arbitrary code execution within the browser's sandbox.

Business Impact

With a CVSS score of 8.8, this is a high-severity risk. While the code execution is constrained within the sandbox, such vulnerabilities are frequently leveraged as part of larger attack chains to escape the sandbox, potentially leading to full system compromise or sensitive data theft from the user's local environment.

Remediation Plan

Immediate Action: Update Google Chrome to version 146.0.7680.153 or later to ensure the V8 engine is patched against this implementation flaw.

Proactive Monitoring: Use endpoint security tools to monitor for suspicious browser process behavior or unexpected network connections originating from Chrome instances.

Compensating Controls: Enable browser-based security features such as site isolation and ensure that users are trained to avoid interacting with untrusted or suspicious web content.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Jun 11, 2026, there is no public information indicating active exploitation of this vulnerability. However, browser-based vulnerabilities are high-value targets for attackers.

Analyst Recommendation

Given the ubiquity of Google Chrome, this update should be deployed across all workstations immediately. Proactive patching is the most effective defense against the potential for remote code execution and subsequent sandbox escape attempts.

---METADATA---
VENDOR: Zed Industries
PRODUCT: Zed
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
A security vulnerability has been identified in the Zed code editor. Further technical details regarding the nature of the flaw are currently unavailable.

Executive Summary:
The Zed code editor is affected by a security vulnerability that poses a significant risk to development environments.

Vulnerability Details

CVE-ID: CVE-2026-44466

Affected Software: Zed Industries Zed

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The provided data lacks specific technical details regarding the vulnerability type or the authentication level required for exploitation. Users should treat this as a high-priority security flaw affecting the core functionality of the Zed editor.

Business Impact

The identified vulnerability carries a CVSS score of 8.6, indicating a high level of risk to organizational infrastructure. Successful exploitation could lead to unauthorized code execution, potential compromise of sensitive source code, or the installation of malicious payloads on developer workstations.

Remediation Plan

Immediate Action: Consult the official Zed security advisory portal to identify the specific versions requiring updates and apply the latest security patches immediately.

Proactive Monitoring: Monitor developer workstation logs and network traffic for anomalous outbound connections or unauthorized process executions originating from the Zed application.

Compensating Controls: Implement endpoint detection and response (EDR) solutions to restrict the execution of unauthorized binaries and isolate development environments from critical network segments.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 29, 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 high severity of this vulnerability, organizations should prioritize auditing their installations of the Zed code editor. Ensure that all instances are updated to the latest vendor-provided version to mitigate potential security risks while awaiting further technical disclosure.

---METADATA---
VENDOR: Zed Industries
PRODUCT: Zed
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
A security vulnerability has been identified in the Zed code editor. Further technical details regarding the nature of the flaw are currently unavailable.

Executive Summary:
The Zed code editor is affected by a security vulnerability that poses a significant risk to development environments.

Vulnerability Details

CVE-ID: CVE-2026-44465

Affected Software: Zed Industries Zed

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The provided data lacks specific technical details regarding the vulnerability type or the authentication level required for exploitation. Users should treat this as a high-priority security flaw affecting the core functionality of the Zed editor.

Business Impact

The identified vulnerability carries a CVSS score of 8.6, indicating a high level of risk to organizational infrastructure. Successful exploitation could lead to unauthorized code execution, potential compromise of sensitive source code, or the installation of malicious payloads on developer workstations.

Remediation Plan

Immediate Action: Consult the official Zed security advisory portal to identify the specific versions requiring updates and apply the latest security patches immediately.

Proactive Monitoring: Monitor developer workstation logs and network traffic for anomalous outbound connections or unauthorized process executions originating from the Zed application.

Compensating Controls: Implement endpoint detection and response (EDR) solutions to restrict the execution of unauthorized binaries and isolate development environments from critical network segments.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 29, 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 high severity of this vulnerability, organizations should prioritize auditing their installations of the Zed code editor. Ensure that all instances are updated to the latest vendor-provided version to mitigate potential security risks while awaiting further technical disclosure.

---METADATA---
VENDOR: Zed Industries
PRODUCT: Zed
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
A security vulnerability has been identified in the Zed code editor. Further technical details regarding the nature of the flaw are currently unavailable.

Executive Summary:
The Zed code editor is affected by a security vulnerability that poses a significant risk to development environments.

Vulnerability Details

CVE-ID: CVE-2026-44463

Affected Software: Zed Industries Zed

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The provided data lacks specific technical details regarding the vulnerability type or the authentication level required for exploitation. Users should treat this as a high-priority security flaw affecting the core functionality of the Zed editor.

Business Impact

The identified vulnerability carries a CVSS score of 8.6, indicating a high level of risk to organizational infrastructure. Successful exploitation could lead to unauthorized code execution, potential compromise of sensitive source code, or the installation of malicious payloads on developer workstations.

Remediation Plan

Immediate Action: Consult the official Zed security advisory portal to identify the specific versions requiring updates and apply the latest security patches immediately.

Proactive Monitoring: Monitor developer workstation logs and network traffic for anomalous outbound connections or unauthorized process executions originating from the Zed application.

Compensating Controls: Implement endpoint detection and response (EDR) solutions to restrict the execution of unauthorized binaries and isolate development environments from critical network segments.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 29, 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 high severity of this vulnerability, organizations should prioritize auditing their installations of the Zed code editor. Ensure that all instances are updated to the latest vendor-provided version to mitigate potential security risks while awaiting further technical disclosure.

---METADATA---
VENDOR: Zed Industries
PRODUCT: Zed
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
A security vulnerability has been identified in the Zed code editor. Technical details regarding the specific nature of the flaw remain limited at this time.

Executive Summary:
A high-severity vulnerability in the Zed code editor poses a significant risk to development environments and local system integrity.

Vulnerability Details

CVE-ID: CVE-2026-44461

Affected Software: Zed Industries Zed

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The exact vulnerability type is currently unspecified, but the high CVSS score of 8.6 indicates a potential for severe impact on the host system. Authentication requirements are not currently documented.

Business Impact

Successful exploitation of this vulnerability could lead to unauthorized system access, potential code execution, or data compromise within the development environment. Given the CVSS score of 8.6, this flaw is considered High severity and requires prompt attention to prevent lateral movement or local privilege escalation.

Remediation Plan

Immediate Action: Monitor official Zed security advisories and apply available patches immediately upon release.

Proactive Monitoring: Review local application logs and system access patterns for anomalous behavior associated with the Zed editor process.

Compensating Controls: Ensure the application is running with the least privilege necessary and utilize host-based intrusion detection systems to monitor for unexpected process execution.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 29, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw and the high CVSS score, the potential for exploitation is significant.

Analyst Recommendation

Organizations utilizing the Zed code editor should treat this vulnerability with urgency. Given the current lack of specific patch information, administrators must maintain close vigilance over the vendor's security channels and be prepared to deploy updates as soon as they become available.

---METADATA---
VENDOR: Lumiverse
PRODUCT: AI chat application
AFFECTED_VERSIONS: Prior to 0.9.7
---END_METADATA---

Description Summary:
A vulnerability in the Lumiverse AI chat application allows authenticated users to achieve arbitrary OS-level code execution via the MCP server creation endpoint.

Executive Summary:
A critical command injection vulnerability in Lumiverse allows authenticated users to execute arbitrary commands on the underlying host server.

Vulnerability Details

CVE-ID: CVE-2026-44450

Affected Software: Lumiverse AI chat application

Affected Versions: Prior to 0.9.7

Vulnerability: The MCP server creation endpoint fails to validate the args array passed to child processes, allowing an attacker to inject inline-code execution flags. While the exploit requires the attacker to be logged in, it bypasses intended restrictions to grant OS-level code execution.

Business Impact

With a CVSS score of 9.9, this vulnerability poses a maximum risk to the server infrastructure. An attacker with standard user access can escalate privileges to the OS level, resulting in full control over the Lumiverse server and potential access to sensitive data or internal network resources.

Remediation Plan

Immediate Action: Update the Lumiverse AI chat application to version 0.9.7 or later.

Proactive Monitoring: Monitor server process logs for unexpected child processes or unusual commands being executed by the application user.

Compensating Controls: Implement strict containerization or sandboxing for the application to limit the impact if code execution is achieved.

Exploitation Status

Public Exploit Available: Null

Analyst Notes: As of May 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

All users of Lumiverse must upgrade to version 0.9.7 immediately. Given the ease of achieving OS-level code execution, this update is essential for maintaining the security and integrity of the hosting environment.

---METADATA---
VENDOR: ERPNext
PRODUCT: ERPNext
AFFECTED_VERSIONS: < 16.9.1
CONFIDENCE: high
MISSING: exploit_status, technical_details
---END_METADATA---

Description Summary:
ERPNext contains a missing authorization check in certain endpoints, allowing authenticated users to modify data beyond their assigned permissions.

Executive Summary:
A critical authorization flaw in ERPNext allows authenticated users to perform unauthorized data modifications, threatening the integrity of business-critical information.

Vulnerability Details

CVE-ID: CVE-2026-44442

Affected Software: ERPNext

Affected Versions: < 16.9.1

Vulnerability: The application fails to enforce proper authorization checks on specific endpoints (CWE-862), allowing authenticated users to manipulate data outside their authorized role. This indicates a failure in access control logic within the application's backend.

Business Impact

With a CVSS score of 9.9, this vulnerability presents a critical risk to business data integrity. An attacker could modify financial records, supply chain data, or user roles, leading to severe reputational damage and operational disruption.

Remediation Plan

Immediate Action: Upgrade all ERPNext instances to version 16.9.1 or higher immediately.

Proactive Monitoring: Audit database logs for unusual record modifications or unauthorized changes made by low-privileged user accounts.

Compensating Controls: Apply strict Role-Based Access Control (RBAC) and review audit trails for any sensitive configuration changes.

Exploitation Status

Public Exploit Available: Not specified

Analyst Notes: As of May 13, 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 flaw necessitates an immediate upgrade to version 16.9.1. Organizations should also conduct a post-remediation audit of their ERPNext environment to ensure no unauthorized data modifications occurred prior to the patch.

---METADATA---
VENDOR: FreeRDP
PRODUCT: FreeRDP
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
A vulnerability exists in FreeRDP, a free implementation of the Remote Desktop Protocol, which may allow for unauthorized system interaction.

Executive Summary:
A high-severity vulnerability in FreeRDP poses a significant risk to remote access infrastructure and requires immediate attention.

Vulnerability Details

CVE-ID: CVE-2026-44421

Affected Software: FreeRDP FreeRDP

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability relates to the FreeRDP implementation of the Remote Desktop Protocol. Insufficient technical documentation prevents definitive classification of the authentication requirement, though RDP flaws often involve remote, unauthenticated access vectors.

Business Impact

Successful exploitation of RDP-related vulnerabilities can lead to unauthorized remote code execution, potential system takeover, and lateral movement within the network. With a CVSS score of 8.8, this vulnerability is classified as High, indicating a severe threat to the confidentiality, integrity, and availability of affected systems.

Remediation Plan

Immediate Action: Identify all instances of FreeRDP within the environment and apply the latest security updates provided by the vendor.

Proactive Monitoring: Review RDP access logs for anomalous login attempts or unauthorized sessions originating from unknown IP addresses.

Compensating Controls: Restrict RDP access to trusted networks via VPNs or firewalls to minimize the attack surface until patches are applied.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 30, 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 High severity rating, administrators should prioritize the identification and patching of all FreeRDP deployments. Failure to address this vulnerability may expose organizational infrastructure to unauthorized remote access and potential compromise.

---METADATA---
VENDOR: FreeRDP
PRODUCT: FreeRDP
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
A vulnerability exists in FreeRDP, a free implementation of the Remote Desktop Protocol, which may lead to security instability.

Executive Summary:
A high-severity vulnerability in FreeRDP necessitates urgent patching to prevent potential remote exploitation of the RDP service.

Vulnerability Details

CVE-ID: CVE-2026-44420

Affected Software: FreeRDP FreeRDP

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the FreeRDP implementation of the Remote Desktop Protocol. The specific mechanism of the flaw remains undefined, but RDP-based vulnerabilities typically threaten the security of remote connections and the underlying host operating system.

Business Impact

Exploitation of this vulnerability could result in severe business disruption, including unauthorized access to sensitive data or complete system compromise. The CVSS score of 8.8 underscores the urgency of remediation, as this vulnerability presents a significant risk to remote connectivity security.

Remediation Plan

Immediate Action: Update all FreeRDP installations to the latest version released by the vendor to resolve the identified security risk.

Proactive Monitoring: Monitor network traffic and authentication logs for suspicious activity associated with RDP services.

Compensating Controls: Implement strict network access control lists (ACLs) to limit RDP exposure to only authorized personnel and secure segments.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 30, 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 must treat this advisory with high urgency. Ensure that all affected systems are audited and updated immediately to mitigate the risk of remote exploitation and subsequent unauthorized system access.

---METADATA---
VENDOR: BentoML
PRODUCT: BentoML
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, technical_details
---END_METADATA---

Description Summary:
A security vulnerability impacts the BentoML Python library, which is used for building online serving systems for AI applications and model inference.

Executive Summary:
The BentoML framework for AI model serving is affected by a vulnerability that could potentially expose systems hosting sensitive machine learning inference models.

Vulnerability Details

CVE-ID: CVE-2026-44346

Affected Software: BentoML

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability resides within the BentoML library, a toolset designed for model serving and AI inference. The specific technical details regarding the vulnerable component or authentication requirements are currently unconfirmed.

Business Impact

Exploitation of AI infrastructure can lead to model theft, data poisoning, or unauthorized execution of code within the inference environment. A CVSS score of 8.8 indicates a high-impact scenario, potentially compromising the integrity of AI-driven business processes and the underlying infrastructure.

Remediation Plan

Immediate Action: Identify all services utilizing BentoML and ensure they are updated to the most recent version available from the maintainer.

Proactive Monitoring: Monitor inference endpoints for unusual latency, unexpected request patterns, or unauthorized API calls that deviate from standard model usage.

Compensating Controls: Implement strict network segmentation for AI serving clusters and deploy WAF rules to validate input data being sent to inference models.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 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

As AI components increasingly become critical parts of the enterprise stack, their security is paramount. Organizations using BentoML should proactively track vendor security advisories and apply patches as soon as they are made available to protect their model serving environments from potential compromise.

---METADATA---
VENDOR: BentoML
PRODUCT: BentoML
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
CONFIDENCE: low
MISSING: versions, patch, exploit_status, technical_details
---END_METADATA---

Description Summary:
A vulnerability exists within the BentoML Python library, which is used for building AI model inference and online serving systems.

Executive Summary:
The BentoML library is affected by a high-severity vulnerability that may compromise the security of AI serving infrastructure.

Vulnerability Details

CVE-ID: CVE-2026-44345

Affected Software: BentoML BentoML

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The provided data lacks specific technical details regarding the nature of the vulnerability, such as the attack vector or authentication requirements. Users should treat the library as potentially insecure until further vendor documentation is reviewed.

Business Impact

Given the CVSS score of 8.8, this vulnerability poses a significant risk to organizations deploying AI models. Successful exploitation could lead to unauthorized access to sensitive model inference data, potential manipulation of AI outputs, or compromise of the underlying serving infrastructure.

Remediation Plan

Immediate Action: Monitor the official BentoML security advisory page for the release of a patched version and apply updates immediately upon availability.

Proactive Monitoring: Review system and access logs for unusual patterns originating from the AI serving environment.

Compensating Controls: Implement strict network segmentation around AI inference servers and utilize a Web Application Firewall (WAF) to inspect traffic for anomalous requests.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 28, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the high CVSS score, the potential for exploitation is considered significant.

Analyst Recommendation

Organizations utilizing BentoML in production environments should prioritize this alert. Until specific patch details are provided by the vendor, ensure that all AI serving systems are isolated and monitored for unauthorized access.