---METADATA---
VENDOR: Milvus
PRODUCT: Milvus Vector Database
AFFECTED_VERSIONS: Prior to 2.5.27 and 2.6.10
---END_METADATA---

Description Summary:
Milvus vector database contains multiple authentication bypass vulnerabilities via exposed TCP ports and unauthenticated REST API endpoints, allowing full data manipulation and credential access.

Executive Summary:
Milvus vector database is subject to a critical authentication bypass that allows unauthenticated attackers to perform arbitrary business operations, including data manipulation and credential theft.

Vulnerability Details

CVE-ID: CVE-2026-26190

Affected Software: Milvus Vector Database

Affected Versions: Prior to 2.5.27 and 2.6.10

Vulnerability: This critical flaw stems from the default exposure of TCP port 9091 and an unauthenticated REST API. Unauthenticated attackers can exploit a predictable debug token or access the management port to evaluate arbitrary expressions and perform unauthorized data operations.

Business Impact

A successful exploit grants an attacker full control over the vector database, which is often the backbone of generative AI applications. This can result in the total loss of data integrity, unauthorized access to sensitive proprietary information, and the potential compromise of downstream AI services. The CVSS score of 9.8 reflects the catastrophic impact on confidentiality, integrity, and availability.

Remediation Plan

Immediate Action: Administrators must immediately upgrade Milvus deployments to version 2.5.27, 2.6.10, or later to close the exposed debug and management endpoints.

Proactive Monitoring: Security teams should review network logs for unauthorized connections to TCP port 9091 and inspect application logs for unusual activity on the /expr and /api/v1 endpoints.

Compensating Controls: Restrict network access to Milvus management ports using firewalls or VPNs, ensuring only trusted internal services can communicate with the database infrastructure.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Feb 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw and the use of predictable default tokens, the potential for exploitation is high.

Analyst Recommendation

The severity of this vulnerability cannot be overstated, as it provides a direct path to total database compromise without authentication. Organizations utilizing Milvus for AI workloads must prioritize the application of the official security patches immediately to mitigate the risk of data exfiltration and manipulation.

---METADATA---
VENDOR: Treeverse
PRODUCT: lakeFS
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
lakeFS, an open-source data versioning tool for object storage, contains a high-severity vulnerability that may affect repository security.

Executive Summary:
A security vulnerability in lakeFS poses a high risk to the integrity and confidentiality of data stored within Git-like object storage repositories.

Vulnerability Details

CVE-ID: CVE-2026-26187

Affected Software: Treeverse lakeFS

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects lakeFS, a tool designed to transform object storage into versioned repositories. The flaw is rated with a CVSS score of 8.1, indicating a High severity impact on the security operations of the data management layer, though the specific exploit vector is currently undisclosed.

Business Impact

A compromise of lakeFS could allow a threat actor to manipulate data versions, delete critical datasets, or gain unauthorized access to sensitive object storage buckets (e.g., S3, GCS). With a CVSS score of 8.1, the business impact includes potential data loss, loss of data lineage, and the introduction of malicious data into production environments, which could disrupt data science and engineering workflows.

Remediation Plan

Immediate Action: Apply the latest security patches from the lakeFS GitHub repository or official vendor distribution immediately.

Proactive Monitoring: Audit lakeFS access logs and S3/object storage logs for unauthorized API calls or unexpected data modifications.

Compensating Controls: Implement strict IAM policies on the underlying object storage to ensure that lakeFS only has the minimum necessary permissions (Principle of Least Privilege).

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of February 14, 2026, there is no public information indicating active exploitation of this vulnerability. The complexity of data versioning tools often hides vulnerabilities that, once discovered, are highly sought after by actors targeting big data infrastructure.

Analyst Recommendation

Organizations relying on lakeFS for data versioning should treat this vulnerability as a high priority. The potential for data manipulation in a production environment is a significant risk that can only be mitigated through rapid patching. We recommend an immediate audit of lakeFS configurations following the update.

---METADATA---
VENDOR: Microsoft
PRODUCT: Power Apps
AFFECTED_VERSIONS: See vendor advisory
CONFIDENCE: medium
MISSING: versions, patch, exploit_status
---END_METADATA---

Description Summary:
Microsoft Power Apps contains a vulnerability involving improper neutralization of control sequences that allows an authorized attacker to bypass security features.

Executive Summary:
A critical security feature bypass vulnerability in Microsoft Power Apps allows an authorized attacker to compromise system integrity over a network.

Vulnerability Details

CVE-ID: CVE-2026-26149

Affected Software: Microsoft Power Apps

Affected Versions: See vendor advisory

Vulnerability: This vulnerability stems from improper neutralization of escape, meta, or control sequences. It requires the attacker to be an authorized user, enabling them to circumvent established security controls.

Business Impact

The ability to bypass security features poses a significant risk to organizational data and application integrity. With a CVSS score of 9.0, this flaw indicates a high potential for unauthorized actions that could lead to data exfiltration or privilege escalation, threatening the overall security posture of the business environment.

Remediation Plan

Immediate Action: Apply the latest security updates provided by Microsoft for Power Apps immediately to neutralize the vulnerability.

Proactive Monitoring: Review application access logs for unusual patterns or attempts to execute unauthorized control sequences.

Compensating Controls: Ensure that strict Role-Based Access Control (RBAC) is enforced to limit the potential impact of an authorized user attempting to exploit this bypass.

Exploitation Status

Public Exploit Available: Not specified

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

Given the critical severity score of 9.0, organizations utilizing Microsoft Power Apps must prioritize the identification and installation of vendor-supplied patches. Failure to remediate this bypass vulnerability leaves sensitive business processes and data exposed to potential manipulation by authenticated malicious actors.

---METADATA---
VENDOR: Nuance
PRODUCT: PowerScribe
AFFECTED_VERSIONS: PowerScribe One (2019.x and 2023.1 lines) and PowerScribe 360 4.0.x
---END_METADATA---

Description Summary:
An insecure deserialization vulnerability in Nuance PowerScribe allows an unauthenticated attacker to execute arbitrary code over a network.

Executive Summary:
A critical deserialization flaw in Nuance PowerScribe exposes clinical infrastructure to unauthenticated remote code execution.

Vulnerability Details

CVE-ID: CVE-2026-26142

Affected Software: Nuance PowerScribe

Affected Versions: PowerScribe One (2019.x and 2023.1 lines) and PowerScribe 360 4.0.x

Vulnerability: This vulnerability involves the deserialization of untrusted data, which permits an unauthenticated attacker to execute code over a network. Exploitation is contingent upon network reachability to the PowerScribe server, which is often deployed within segmented clinical environments.

Business Impact

With a CVSS score of 9.8, this vulnerability represents a severe risk to healthcare operations. Successful exploitation could lead to full system compromise, unauthorized access to sensitive patient data, and significant disruption to critical clinical workflows.

Remediation Plan

Immediate Action: Review vendor documentation for available updates and apply the latest security patches to all PowerScribe instances immediately.

Proactive Monitoring: Monitor network traffic for anomalous deserialization patterns or unauthorized attempts to reach PowerScribe servers from untrusted segments.

Compensating Controls: Ensure the PowerScribe server remains isolated within a strictly segmented network and utilize a Web Application Firewall (WAF) to inspect and block malicious serialized payloads.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Jun 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 critical CVSS rating and the potential for total system takeover, administrators should prioritize the identification and patching of all affected PowerScribe installations. Immediate isolation of these assets is recommended until updates can be verified and applied.

---METADATA---
VENDOR: Microsoft
PRODUCT: 365 Copilot Business Chat
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A Server-Side Request Forgery (SSRF) vulnerability in Microsoft 365 Copilot's Business Chat allows an authenticated attacker to elevate privileges across a network.

Executive Summary:
A high-severity SSRF vulnerability in Microsoft 365 Copilot Business Chat enables authenticated attackers to perform unauthorized network requests and escalate their privileges within the environment.

Vulnerability Details

CVE-ID: CVE-2026-26137

Affected Software: Microsoft 365 Copilot Business Chat

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability involves a Server-Side Request Forgery (SSRF) flaw where an authorized user can manipulate the application into making unauthorized requests to internal or external resources. This can be leveraged to bypass network security controls and achieve privilege escalation.

Business Impact

Successful exploitation allows an attacker to interact with internal services that are not intended to be public-facing. This can lead to the exposure of sensitive internal data, lateral movement within the Microsoft 365 environment, and elevated access to corporate resources. The CVSS score of 8.9 reflects the significant risk to network security and data confidentiality.

Remediation Plan

Immediate Action: Apply the security updates provided by Microsoft immediately. Administrators should refer to the official Microsoft Security Response Center (MSRC) advisory for specific deployment instructions.

Proactive Monitoring: Monitor network traffic for unusual outbound requests originating from the Copilot service and review audit logs for unauthorized privilege escalation attempts.

Compensating Controls: Implement strict egress filtering and network segmentation to limit the ability of the Copilot service to reach sensitive internal endpoints.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 21, 2026, there is no public information indicating active exploitation of this vulnerability. However, SSRF in AI-driven chat interfaces is a known area of interest for researchers and attackers alike.

Analyst Recommendation

Due to the integration of Microsoft 365 Copilot with sensitive corporate data, this high-severity SSRF must be addressed urgently. Organizations should prioritize the application of Microsoft's security patches to prevent potential privilege escalation and unauthorized internal network access.

---METADATA---
VENDOR: Microsoft
PRODUCT: Azure Custom Locations
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A Server-Side Request Forgery (SSRF) in the Azure Custom Locations Resource Provider allows authenticated attackers to elevate privileges over a network.

Executive Summary:
Azure Custom Locations contains an SSRF vulnerability that allows an authorized attacker to escalate their privileges, potentially compromising the underlying resource provider.

Vulnerability Details

CVE-ID: CVE-2026-26135

Affected Software: Azure Custom Locations Resource Provider (RP)

Affected Versions: See vendor advisory

Vulnerability: This is a Server-Side Request Forgery (SSRF) vulnerability that requires the attacker to be authorized (authenticated). An authenticated user can exploit the Resource Provider to make unauthorized requests, leading to privilege escalation within the Azure environment.

Business Impact

While this requires prior authentication, the CVSS score of 9.6 indicates a critical risk. An attacker with low-level access could escalate to administrative levels, gaining control over custom location resources and potentially pivoting to other connected Azure services, resulting in unauthorized data access and infrastructure manipulation.

Remediation Plan

Immediate Action: Update the Azure Custom Locations Resource Provider to the latest version immediately through the Azure portal or CLI.

Proactive Monitoring: Monitor for anomalous API calls to the Custom Locations Resource Provider and review logs for unexpected internal network traffic originating from the RP.

Compensating Controls: Enforce the principle of least privilege for all users and service principals interacting with Custom Locations to limit the potential scope of an SSRF-based escalation.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of April 3, 2026, there is no evidence of active exploitation. The requirement for authentication slightly reduces the attack surface compared to unauthenticated flaws, but the high CVSS score reflects the severity of the post-authentication impact.

Analyst Recommendation

Organizations utilizing hybrid or custom Azure locations should apply this update immediately. Even though authentication is required, the potential for an insider threat or a compromised low-privilege account to escalate to full control makes this a critical priority for security teams.

---METADATA---
VENDOR: Microsoft
PRODUCT: Windows Admin Center
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
Improper authentication within Microsoft Windows Admin Center enables an authorized attacker to escalate privileges via network access. This flaw facilitates unauthorized administrative control.

Executive Summary:
A privilege escalation vulnerability in Microsoft Windows Admin Center allows authenticated attackers to elevate their permissions across a network, potentially compromising managed infrastructure.

Vulnerability Details

CVE-ID: CVE-2026-26119

Affected Software: Microsoft Windows Admin Center

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability stems from improper authentication handling within the Windows Admin Center interface. An attacker who has already obtained authorized access to the network can exploit this flaw to elevate their privileges to a higher level than intended.

Business Impact

A successful exploit of this vulnerability could allow a low-privileged user to gain administrative rights over the Windows Admin Center, leading to full control over connected servers and infrastructure. With a CVSS score of 8.8, the risk is classified as High, as it directly threatens the integrity of the management plane and could result in widespread system downtime or unauthorized configuration changes.

Remediation Plan

Immediate Action: Apply the latest security updates provided by Microsoft for Windows Admin Center immediately to resolve the authentication logic error.

Proactive Monitoring: Review Windows Admin Center access logs for unusual login patterns or privilege changes and monitor network traffic for suspicious activity targeting management ports.

Compensating Controls: Restrict access to the Windows Admin Center interface using network-level access control lists (ACLs) or a VPN to ensure only trusted internal devices can reach the service.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of February 18, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw and its location in a central management tool, the potential for targeted exploitation is high.

Analyst Recommendation

The high CVSS score of 8.8 underscores the critical nature of this privilege escalation flaw. Because Windows Admin Center is a gateway to broader server infrastructure, administrators must prioritize the application of the vendor-supplied patch. Immediate remediation is essential to prevent internal lateral movement and unauthorized administrative takeovers.