---METADATA---
VENDOR: YunaiV
PRODUCT: yudao-cloud
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
A security vulnerability has been discovered in the YunaiV yudao-cloud platform, which may expose the system to unauthorized access or manipulation.

Executive Summary:
A high-severity security flaw in the YunaiV yudao-cloud platform necessitates immediate review and patching to prevent potential unauthorized access.

Vulnerability Details

CVE-ID: CVE-2026-7679

Affected Software: YunaiV yudao-cloud

Affected Versions: See vendor advisory for affected versions

Vulnerability: A security flaw has been discovered in versions of yudao-cloud up to 2026. While details are sparse, users should monitor the vendor's security bulletins for specific mitigation steps and affected components.

Business Impact

With a CVSS score of 7.3, this vulnerability represents a significant risk to the integrity and availability of applications built on the yudao-cloud platform. Exploitation could lead to unauthorized data access or disruption of cloud-based services.

Remediation Plan

Immediate Action: Apply the latest security updates and patches released by YunaiV for the yudao-cloud platform.

Proactive Monitoring: Review application logs for suspicious access requests and monitor the platform’s administrative console for signs of tampering.

Compensating Controls: Enforce strict identity and access management (IAM) policies and ensure that the platform is not exposed to the public internet without proper security controls.

Exploitation Status

Public Exploit Available: false

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

Analyst Recommendation

Organizations using the yudao-cloud platform should prioritize applying the latest updates. Proactive patching and robust access controls are essential to protecting against this and other potential vulnerabilities within the cloud environment.

---METADATA---
VENDOR: Aqara
PRODUCT: IAM/SSO gateway
AFFECTED_VERSIONS: Aqara IAM/SSO gateway (gw-builder.aqara.com)
---END_METADATA---

Description Summary:
The Aqara IAM/SSO gateway contains a critical flaw that exposes cryptographic signing keys, allowing unauthenticated attackers to perform unauthorized operations.

Executive Summary:
The Aqara IAM/SSO gateway is vulnerable to an unauthenticated cryptographic bypass that could allow attackers to forge authentication tokens and gain unauthorized system access.

Vulnerability Details

CVE-ID: CVE-2026-50086

Affected Software: Aqara IAM/SSO gateway

Affected Versions: Aqara IAM/SSO gateway (gw-builder.aqara.com)

Vulnerability: The gateway performs bidirectional AES round-trips against the platform’s signing key without requiring authentication. This allows an unauthenticated network attacker to leverage the signing key to forge authentication tokens.

Business Impact

The ability to forge authentication tokens effectively renders the Identity and Access Management system useless, allowing an attacker to masquerade as any user or administrator. This leads to a total compromise of the authentication boundary, potentially resulting in unauthorized access to sensitive user data and backend systems. While the base description suggests a lower severity, the ability to bypass core authentication warrants a critical response.

Remediation Plan

Immediate Action: Apply the patch provided in the official GitHub advisory (GHSA-3897-2crh-vgmr) immediately.

Proactive Monitoring: Monitor IAM/SSO logs for anomalous authentication requests or tokens that do not align with known user behavior patterns.

Compensating Controls: Implement strict network access control lists (ACLs) to limit access to the gateway to authorized internal infrastructure only.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Jun 12, 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

Authentication bypasses involving cryptographic signing keys are high-risk events. Security teams should treat this as a priority update to ensure the integrity of the platform’s identity services and prevent potential unauthorized access.

---METADATA---
VENDOR: Roxy-WI
PRODUCT: Roxy-WI
AFFECTED_VERSIONS: 8.2.6.4 and prior
---END_METADATA---

Description Summary:
Roxy-WI contains an authenticated arbitrary file write vulnerability in its WAF rule saving functionality, allowing for Remote Code Execution on managed load balancers.

Executive Summary:
An authenticated Remote Code Execution vulnerability exists in Roxy-WI versions 8.2.6.4 and prior, posing a critical risk to all managed load balancer infrastructure.

Vulnerability Details

CVE-ID: CVE-2026-45556

Affected Software: Roxy-WI

Affected Versions: 8.2.6.4 and prior

Vulnerability: This vulnerability is an authenticated arbitrary file write flaw within the WAF configuration saving function that fails to properly sanitize file paths. By manipulating the config_file_name parameter, an authenticated attacker can write malicious cron jobs to the filesystem, resulting in root-level Remote Code Execution.

Business Impact

With a CVSS score of 9.9, this vulnerability represents a critical threat. Successful exploitation grants an attacker full control over the load balancer, which acts as a central gateway for network traffic. This could lead to total compromise of application traffic, data exfiltration, and significant service disruption across the entire managed environment.

Remediation Plan

Immediate Action: Review the vendor security advisory at https://github.com/roxy-wi/roxy-wi/security/advisories and prioritize upgrading to the latest available version once released.

Proactive Monitoring: Monitor server logs for unauthorized modifications to system configuration files or suspicious cron jobs located in /etc/cron.d/.

Compensating Controls: Implement strict network segmentation to limit access to the Roxy-WI management interface to authorized administrative personnel only.

Exploitation Status

Public Exploit Available: False

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

The severity of this vulnerability necessitates immediate attention. Given the potential for full system compromise, administrators should restrict access to the Roxy-WI interface and monitor for any anomalous file system activity until a patch is applied.

---METADATA---
VENDOR: GitHub
PRODUCT: Copilot / Visual Studio Code
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
An insecure default resource initialization in GitHub Copilot and Visual Studio Code allows unauthenticated attackers to perform information disclosure over a network.

Executive Summary:
A critical security flaw in GitHub Copilot and Visual Studio Code exposes sensitive data to unauthorized network-based attackers due to insecure default resource initialization.

Vulnerability Details

CVE-ID: CVE-2026-45482

Affected Software: GitHub Copilot and Visual Studio Code

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability involves the improper initialization of a resource with insecure defaults. An unauthenticated remote attacker can exploit this configuration to intercept or access sensitive information transmitted over the network.

Business Impact

The potential for unauthorized information disclosure poses a significant risk to intellectual property and proprietary codebases managed within the development environment. With a CVSS score of 8.4, this high-severity vulnerability could lead to the exposure of credentials, API keys, or sensitive internal logic, ultimately resulting in severe reputational damage and loss of competitive advantage.

Remediation Plan

Immediate Action: Audit the development environment and apply all relevant security updates provided by GitHub and Microsoft for Visual Studio Code immediately.

Proactive Monitoring: Review network access logs for unusual traffic patterns originating from or directed toward development endpoints.

Compensating Controls: Implement strict network segmentation for development machines and utilize encrypted tunnels to minimize the exposure of sensitive development traffic.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 20, 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 CVSS score and the critical nature of development tools in the software supply chain, organizations must prioritize patching these components. Immediate deployment of vendor-supplied updates is the only definitive method to mitigate the risk of unauthorized data interception.

---METADATA---
VENDOR: GitHub
PRODUCT: Actions OIDC
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
GitHub Actions OIDC was exploited to publish malicious npm packages by chaining multiple vulnerabilities, including cache poisoning and token extraction.

Executive Summary:
An attacker successfully compromised the GitHub Actions OIDC trusted-publisher binding to inject malicious code into legitimate npm packages.

Vulnerability Details

CVE-ID: CVE-2026-45321

Affected Software: GitHub Actions OIDC

Affected Versions: See vendor advisory

Vulnerability: This is a supply chain compromise involving the chaining of a pull_request_target misconfiguration, GitHub Actions cache poisoning, and OIDC token theft from the runner process. This allowed the attacker to masquerade as a trusted identity to publish malicious versions of @tanstack/* packages.

Business Impact

This vulnerability represents a severe supply chain threat, potentially affecting any downstream software that relies on the compromised packages. With a CVSS score of 9.6, the incident highlights the risks associated with CI/CD pipeline trust boundaries.

Remediation Plan

Immediate Action: Audit all CI/CD workflows for pull_request_target usage and implement hardened OIDC token handling.

Proactive Monitoring: Monitor for unexpected package publications and scan dependencies for signs of tampering or unauthorized code.

Compensating Controls: Implement strict environment variable access controls and use ephemeral, short-lived tokens for all CI/CD operations.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of May 12, 2026, this vulnerability has been actively exploited in the wild, as demonstrated by the malicious publication of 84 package versions.

Analyst Recommendation

This incident serves as a critical reminder of CI/CD pipeline security. Organizations must review their GitHub Actions configurations, particularly regarding OIDC and pull request triggers, to prevent similar supply chain attacks.

---METADATA---
VENDOR: CloudPirates
PRODUCT: Open Source Helm Charts
AFFECTED_VERSIONS: Prior to commit fcf9302
---END_METADATA---

Description Summary:
A GitHub Actions workflow in CloudPirates Helm Charts exposes Personal Access Tokens and SSH signing keys to untrusted code.

Executive Summary:
Unsafe credential handling in CloudPirates Helm Charts exposes sensitive signing and access keys, creating an immediate risk of repository compromise.

Vulnerability Details

CVE-ID: CVE-2026-45132

Affected Software: CloudPirates Open Source Helm Charts

Affected Versions: Prior to commit fcf9302

Vulnerability: The generate-schema.yaml workflow uses unsafe checkout practices that allow fork-controlled code to access and exfiltrate Personal Access Tokens and SSH signing keys.

Business Impact

The theft of signing keys and access tokens allows an attacker to impersonate the project maintainers and push malicious code or sign fraudulent commits. With a CVSS score of 10.0, this represents a critical threat to the integrity of the entire software lifecycle.

Remediation Plan

Immediate Action: Update to commit fcf9302 or later to correct the workflow checkout and credential management practices.

Proactive Monitoring: Review repository logs for unauthorized commit activity or unusual use of the compromised SSH signing keys.

Compensating Controls: Immediately revoke and rotate all Personal Access Tokens and SSH keys that were configured for use within this workflow.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Jun 1, 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 secret exposure, users must treat this as a high-urgency remediation. Beyond updating the workflow, a full rotation of all exposed secrets is required to ensure the security of the repository and its associated assets.

---METADATA---
VENDOR: CloudPirates
PRODUCT: Open Source Helm Charts
AFFECTED_VERSIONS: Prior to commit fcf9302
---END_METADATA---

Description Summary:
A GitHub Actions workflow in CloudPirates Helm Charts executes attacker-controlled code from forks, exposing repository secrets.

Executive Summary:
A critical configuration flaw in CloudPirates Helm Charts exposes sensitive repository credentials to unauthorized actors via GitHub Actions.

Vulnerability Details

CVE-ID: CVE-2026-45131

Affected Software: CloudPirates Open Source Helm Charts

Affected Versions: Prior to commit fcf9302

Vulnerability: The pull-request.yaml GitHub Actions workflow runs code from untrusted forks in a privileged context, exposing Docker Hub credentials and other repository secrets without requiring approval.

Business Impact

Exposure of credentials allows attackers to access private container registries and potentially inject malicious code into the software supply chain. With a CVSS score of 10.0, this vulnerability presents a catastrophic risk to the security of the build pipeline and downstream software users.

Remediation Plan

Immediate Action: Update to commit fcf9302 or later to secure the GitHub Actions workflow and isolate untrusted code execution.

Proactive Monitoring: Audit repository secret usage logs and verify if any credentials have been accessed or used by unauthorized parties.

Compensating Controls: Rotate all secrets (Docker Hub credentials, tokens) that were exposed or potentially accessible during the vulnerable period.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Jun 1, 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 supply chain risk. Organizations using these Helm charts must update to the patched version and treat all previously stored secrets as compromised, necessitating a mandatory rotation of all affected credentials.

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

Description Summary:
A security vulnerability has been identified in GitHub's GuardDog CLI tool, which is used for identifying malicious PyPI packages.

Executive Summary:
The GitHub GuardDog CLI tool is affected by a security vulnerability that could potentially allow for the bypass of malicious package detection mechanisms.

Vulnerability Details

CVE-ID: CVE-2026-44971

Affected Software: GitHub GuardDog

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The input data does not specify the exact nature of the vulnerability, though it impacts a tool designed to analyze external dependencies. Users should assume that the vulnerability could allow for the misidentification or bypassing of security checks during package analysis.

Business Impact

Failure to accurately identify malicious PyPI packages can lead to the introduction of supply chain threats into internal development environments. With a CVSS score of 8.2, this vulnerability carries a high impact, as it undermines the security tooling intended to protect against malicious code execution.

Remediation Plan

Immediate Action: Monitor official GitHub releases for GuardDog and update to the latest version as soon as a security patch is provided.

Proactive Monitoring: Review CI/CD pipeline logs for any discrepancies in package scanning results or unauthorized modifications to dependency manifests.

Compensating Controls: Implement secondary, manual verification processes for critical Python dependencies while the primary scanning tool is being remediated.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of May 29, 2026, there is no public information indicating active exploitation of this vulnerability. Despite the lack of an exploit, the role of this tool in security workflows necessitates immediate prioritization of updates.

Analyst Recommendation

Security teams should immediately audit their use of GuardDog and monitor for vendor updates. Given the high severity, ensure that all automated scanning processes are verified and that redundant checks are in place to validate package integrity.

---METADATA---
VENDOR: Postiz
PRODUCT: Postiz
AFFECTED_VERSIONS: Prior to commit da44801
---END_METADATA---

Description Summary:
A "Pwn Request" vulnerability in Postiz allows unauthenticated users to execute arbitrary code via malicious pull requests, leading to credential exfiltration.

Executive Summary:
An unauthenticated arbitrary code execution vulnerability in the Postiz CI/CD workflow allows attackers to exfiltrate highly privileged tokens.

Vulnerability Details

CVE-ID: CVE-2026-42298

Affected Software: Postiz

Affected Versions: Prior to commit da44801

Vulnerability: The Docker build workflow fails to safely handle external inputs, allowing an unauthenticated attacker to inject malicious code during the build process and exfiltrate the GITHUB_TOKEN.

Business Impact

The ability to steal write-access tokens grants attackers control over the repository and potentially the entire software supply chain. Given the CVSS score of 10, this is a critical threat that could lead to widespread unauthorized code commits and severe reputational damage.

Remediation Plan

Immediate Action: Update the affected workflow files to the version provided in commit da44801 or later.

Proactive Monitoring: Audit recent pull requests and review repository audit logs for any unauthorized access or unusual CI/CD pipeline behavior.

Compensating Controls: Implement stricter branch protection rules and limit the permissions of the GITHUB_TOKEN used in automated workflows.

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 is an extremely severe supply chain vulnerability. Security teams must ensure all CI/CD pipelines are patched and that access tokens are rotated if there is any suspicion of compromise.

---METADATA---
VENDOR: GitHub
PRODUCT: Electerm
AFFECTED_VERSIONS: Prior to 3.3.8
---END_METADATA---

Description Summary:
A command injection vulnerability in Electerm allows attackers to execute arbitrary code by supplying a malicious release name.

Executive Summary:
A command injection vulnerability in Electerm prior to version 3.3.8 allows attackers to execute arbitrary code, posing a critical security risk to user systems.

Vulnerability Details

CVE-ID: CVE-2026-41500

Affected Software: GitHub Electerm

Affected Versions: Prior to 3.3.8

Vulnerability: The runMac() function fails to validate the releaseInfo.name variable before passing it to the exec() function, allowing for arbitrary command injection.

Business Impact

With a CVSS score of 9.8, this vulnerability allows for full system compromise on affected machines. An attacker successfully exploiting this can execute arbitrary code with the privileges of the user running the application, leading to complete data theft or malware installation.

Remediation Plan

Immediate Action: Upgrade to Electerm version 3.3.8 or later immediately.

Proactive Monitoring: Monitor for suspicious process creation or unexpected network connections originating from the Electerm application.

Compensating Controls: Avoid using the application with elevated privileges and ensure that the host OS is protected by robust endpoint detection and response (EDR) solutions.

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, the ease of exploitability via command injection necessitates immediate patching.

Analyst Recommendation

All users of Electerm must upgrade to version 3.3.8 immediately. The severity of the command injection flaw makes this a high-priority update for any security-conscious deployment.

---METADATA---
VENDOR: SUSE
PRODUCT: Rancher
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A flaw in the Rancher GitHub authentication provider causes incorrect caching of team memberships, allowing unauthorized users to gain principal access.

Executive Summary:
A critical authentication caching vulnerability in SUSE Rancher allows logged-in users to potentially escalate privileges and gain unauthorized principal access.

Vulnerability Details

CVE-ID: CVE-2026-41053

Affected Software: SUSE Rancher

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability involves incorrect authentication caching within the team membership expansion logic of the GitHub authentication provider. It allows any authenticated user to potentially inherit or be granted unauthorized principal-level access to the system.

Business Impact

The ability for a standard user to gain principal-level access poses a severe risk to organizational security, potentially leading to full administrative compromise of the Rancher platform. Given the CVSS score of 8.8, this flaw represents a High severity risk that could result in unauthorized data access, configuration tampering, and total loss of confidentiality and integrity within managed container environments.

Remediation Plan

Immediate Action: Identify and apply the security patches provided by SUSE as soon as they are released for your specific Rancher version.

Proactive Monitoring: Review authentication logs for anomalous account behavior, specifically looking for users performing administrative actions beyond their expected scope.

Compensating Controls: Restrict access to the Rancher management interface to trusted networks or via a VPN to minimize the attack surface until patches are applied.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of July 1, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw and the potential for privilege escalation, the potential for exploitation is high.

Analyst Recommendation

The severity of this authentication bypass necessitates prompt attention from all security administrators managing Rancher deployments. Organizations should prioritize the deployment of vendor-supplied patches and conduct a thorough audit of account permissions to ensure no unauthorized principal access has been granted while the vulnerability was active.

---METADATA---
VENDOR: GitHub
PRODUCT: goshs
AFFECTED_VERSIONS: Prior to 2.0.0-beta.6
---END_METADATA---

Description Summary:
The goshs SimpleHTTPServer is affected by an ArtiPACKED vulnerability that can lead to the unauthorized leakage of GITHUB_TOKEN credentials via workflow artifacts.

Executive Summary:
A credential leakage vulnerability in goshs allows unauthorized access to sensitive GITHUB_TOKEN credentials through workflow artifacts.

Vulnerability Details

CVE-ID: CVE-2026-40903

Affected Software: GitHub goshs

Affected Versions: Prior to 2.0.0-beta.6

Vulnerability: The "ArtiPACKED" vulnerability allows for the inadvertent exposure of sensitive environment tokens, even if those tokens are not explicitly stored in the source code repository.

Business Impact

Leakage of the GITHUB_TOKEN can provide attackers with unauthorized access to private repositories, workflow secrets, and deployment environments. Given the CVSS score of 9.1, this vulnerability poses a significant risk to the entire software supply chain and organizational development security.

Remediation Plan

Immediate Action: Upgrade goshs to version 2.0.0-beta.6 or later and immediately rotate any GITHUB_TOKENs that were accessible by the affected versions.

Proactive Monitoring: Audit CI/CD logs for unauthorized access and review artifact storage for potential data leakage.

Compensating Controls: Implement strict permissions on repository artifacts and enforce the use of short-lived tokens where possible.

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 sensitive nature of the leaked information, the potential for exploitation is high.

Analyst Recommendation

Security teams must treat this as a high-priority incident. Beyond applying the software update, it is critical to assume that existing tokens may have been compromised and to perform a full credential rotation across all affected workflows.

---METADATA---
VENDOR: Emissary
PRODUCT: Emissary
AFFECTED_VERSIONS: Prior to 8.39.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A shell injection vulnerability in Emissary workflow files allows attackers with repository write access to execute arbitrary commands, leading to supply chain compromise.

Executive Summary:
A critical shell injection vulnerability in the Emissary workflow engine allows attackers with repository write access to execute arbitrary commands and compromise downstream users.

Vulnerability Details

CVE-ID: CVE-2026-35580

Affected Software: Emissary Emissary

Affected Versions: Prior to 8.39.0

Vulnerability: The vulnerability exists due to the insecure interpolation of user-controlled workflow_dispatch inputs directly into shell commands via ${{ }} syntax within workflow files. This allows an authenticated attacker with repository write access to inject malicious shell commands.

Business Impact

This flaw facilitates supply chain attacks, potentially allowing an attacker to poison build artifacts and impact all users downstream of the affected workflow. The CVSS score of 9.1 reflects the high potential for widespread disruption and unauthorized code execution within the software development lifecycle.

Remediation Plan

Immediate Action: Upgrade the Emissary workflow engine to version 8.39.0 or later to ensure proper sanitization of inputs.

Proactive Monitoring: Inspect existing workflow files for suspicious ${{ }} expressions and review audit logs for unexpected shell commands executed by the workflow engine.

Compensating Controls: Restrict repository write access to trusted personnel only and implement strict peer review processes for all changes to workflow configuration files.

Exploitation Status

Public Exploit Available: Not specified.

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

Supply chain security is paramount; failure to remediate this vulnerability could result in the compromise of downstream development pipelines. Organizations should prioritize updating to version 8.39.0 and reviewing repository access permissions to mitigate the risk of malicious command injection.

---METADATA---
VENDOR: wenxian
PRODUCT: wenxian
AFFECTED_VERSIONS: Versions 0.3.1 and prior
---END_METADATA---

Description Summary:
The wenxian GitHub Actions workflow is vulnerable to command injection via untrusted user input in issue comments, allowing arbitrary code execution on the GitHub runner.

Executive Summary:
An unauthenticated attacker can execute arbitrary code on a GitHub Actions runner by simply posting a crafted comment on a repository using the wenxian tool.

Vulnerability Details

CVE-ID: CVE-2026-34243

Affected Software: wenxian (GitHub Actions workflow)

Affected Versions: Versions 0.3.1 and prior

Vulnerability: The workflow uses issue_comment.body directly inside a shell command without sanitization. An unauthenticated attacker can post a comment containing shell metacharacters to trigger command injection and execute arbitrary code within the context of the GitHub Actions runner.

Business Impact

A successful exploit allows an attacker to hijack the CI/CD pipeline. This can lead to the theft of GitHub secrets (e.g., API keys, cloud credentials), the injection of malicious code into the software supply chain, or unauthorized access to the repository. The CVSS score of 9.8 highlights the extreme risk of supply chain compromise.

Remediation Plan

Immediate Action: Disable the affected GitHub Actions workflow immediately. Since no patch is currently available, manually sanitize the workflow file to use environment variables for user input instead of direct shell interpolation.

Proactive Monitoring: Review GitHub Actions run history for suspicious activity and audit all secrets used by the affected repository for potential compromise.

Compensating Controls: Use "Restrict repository permissions" in GitHub to ensure that the GITHUB_TOKEN has minimal permissions (read-only) for workflows triggered by external users.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of March 31, 2026, there are no publicly available patches. This vulnerability is particularly dangerous as it can be triggered by any GitHub user by simply commenting on an issue.

Analyst Recommendation

The lack of a vendor patch makes this a critical "zero-day" risk for users of wenxian. Immediate manual intervention is required to secure the GitHub Actions workflow. Ensure that all user-supplied data is treated as untrusted and never passed directly to a shell.

---METADATA---
VENDOR: Langflow
PRODUCT: Langflow
AFFECTED_VERSIONS: Prior to version 1.9.0
---END_METADATA---

Description Summary:
Unauthenticated remote shell injection in Langflow's GitHub Actions workflows allows attackers to execute arbitrary commands and exfiltrate CI secrets via malicious branch names.

Executive Summary:
Langflow is vulnerable to unauthenticated remote shell injection in its CI/CD pipelines, allowing attackers to steal sensitive secrets and compromise the software supply chain.

Vulnerability Details

CVE-ID: CVE-2026-33475

Affected Software: Langflow

Affected Versions: Prior to version 1.9.0

Vulnerability: This is a shell injection vulnerability in GitHub Actions workflows. It occurs because unsanitized GitHub context variables (like github.head_ref) are directly interpolated into run: shell commands, allowing an unauthenticated attacker to execute commands by submitting a pull request with a malicious branch name.

Business Impact

An attacker can exfiltrate sensitive CI secrets, such as GITHUB_TOKEN, and potentially push malicious code or images to production repositories. This could lead to a massive supply chain compromise affecting all users of the Langflow product. The CVSS score of 9.1 reflects the critical risk to the integrity of the development lifecycle.

Remediation Plan

Immediate Action: Update Langflow to version 1.9.0 or later, which refactors workflows to use environment variables instead of direct interpolation.

Proactive Monitoring: Audit GitHub Actions logs for suspicious activity, such as unusual curl commands or unauthorized access to secrets in workflows triggered by external forks.

Compensating Controls: Restrict GitHub Actions permissions and require manual approval for all workflows triggered by pull requests from external contributors.

Exploitation Status

Public Exploit Available: Yes

Analyst Notes: As of Mar 24, 2026, a proof-of-concept (PoC) is publicly available demonstrating how to exfiltrate secrets via a malicious branch name. Active exploitation is highly likely given the public nature of the PoC.

Analyst Recommendation

This is a critical supply chain vulnerability. We strongly recommend that all organizations using Langflow immediately update to version 1.9.0 and rotate any secrets that may have been exposed in their CI/CD environments.

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

Description Summary:
LibreChat, an open-source ChatGPT clone, contains a high-severity vulnerability that could impact the security of the AI interface and user data.

Executive Summary:
LibreChat is affected by a high-severity security vulnerability that could allow attackers to compromise the application environment or gain unauthorized access to user sessions.

Vulnerability Details

CVE-ID: CVE-2026-31945

Affected Software: LibreChat

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists in the LibreChat application, a platform for interfacing with various AI models. With a CVSS score of 7.7, the flaw likely involves improper input validation or a session management issue that could be exploited by an attacker to intercept data or perform actions on behalf of users.

Business Impact

Exploitation of this vulnerability could lead to the exposure of sensitive AI prompts, API keys, and private conversations. In a corporate environment, this represents a significant data leak risk. The High severity rating (7.7) reflects the potential for attackers to disrupt the service or compromise the privacy of all users on the platform.

Remediation Plan

Immediate Action: Administrators of LibreChat instances should pull the latest Docker images or update the source code to the most recent patched version immediately.

Proactive Monitoring: Review application logs for suspicious API calls or unauthorized attempts to access the administrative dashboard.

Compensating Controls: Implement a reverse proxy with strong authentication (e.g., OAuth or SAML) to protect the LibreChat interface from direct public exposure.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 29, 2026, there is no public information indicating active exploitation. However, open-source AI tools are currently high-interest targets for researchers and malicious actors alike.

Analyst Recommendation

Given the increasing use of AI clones in business workflows, this vulnerability should be treated with high priority. Administrators must ensure their LibreChat deployments are updated to the latest version to protect user data and maintain the integrity of the AI environment.

---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.

Executive Summary:
A critical vulnerability exists in the Eclipse Theia Website's automated software build process that could allow an attacker to execute malicious code. By submitting a specially crafted pull request, an unauthorized user could gain extensive control over the project's environment, enabling them to steal sensitive secrets, modify the official website, and inject malicious code into the repository. This flaw represents a complete compromise of the affected system's integrity and confidentiality.

Vulnerability Details

CVE-ID: CVE-2026-1699

Affected Software: In the Eclipse Theia Website Multiple Products

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability lies within a GitHub Actions workflow file (.github/workflows/preview.yml) which improperly uses the pull_request_target trigger. This trigger is designed to run workflows with access to the base repository's secrets and a privileged GITHUB_TOKEN, even for pull requests from forked repositories. The workflow dangerously combines this trigger with steps that check out and execute code from the untrusted pull request, creating a code injection vector. An attacker can exploit this by submitting a pull request containing malicious commands, which are then executed within the trusted CI/CD environment, granting them access to repository secrets and write permissions to packages, pages, and the repository itself.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 10, indicating the highest possible risk. Successful exploitation could lead to severe business consequences, including a full-scale supply chain attack where malicious packages are published under the trusted Eclipse Theia organization name, impacting downstream users. An attacker could also deface the official website, causing significant reputational damage, or inject backdoors into the source code, compromising the integrity of the product. The exfiltration of repository secrets could lead to further compromise of related infrastructure and services, resulting in significant data breaches and financial loss.

Remediation Plan

Immediate Action: Update In the Eclipse Theia Website Multiple Products to the latest version immediately to apply the necessary security patch that corrects the flawed GitHub Actions workflow. After patching, conduct a thorough review of access logs and GitHub audit logs for any signs of exploitation attempts that may have occurred prior to remediation.

Proactive Monitoring: Monitor GitHub Actions workflow logs for any unusual commands, unexpected script executions, or outbound network connections to suspicious endpoints. Implement alerts for pull requests submitted by new or unknown contributors that modify workflow files. Regularly scan public package repositories for any unauthorized or malicious packages published under the organization's name.

Compensating Controls: If immediate patching is not feasible, temporarily disable the vulnerable .github/workflows/preview.yml workflow to close the attack vector. Rotate all secrets stored in the repository's GitHub secrets configuration as they should be considered compromised. Implement a policy requiring manual review and approval by a trusted maintainer before any workflows are run on external pull requests.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of the published date, Jan 30, 2026, there are no known public exploits or active exploitation campaigns targeting this vulnerability. However, the attack pattern involving the misuse of pull_request_target is well-documented, and proof-of-concept exploits can be developed with minimal effort by skilled threat actors.

Analyst Recommendation

Given the critical CVSS score of 10 and the potential for a complete compromise of the CI/CD pipeline and repository, organizations must treat this vulnerability with the highest urgency. The primary recommendation is to apply the vendor-supplied patches immediately. Following the update, a comprehensive security audit is crucial to identify any signs of historical compromise, including unauthorized code commits, malicious package publications, or secret exfiltration. Although not currently on the CISA KEV list, the severity of this vulnerability warrants immediate and decisive action to prevent a potentially devastating security incident.

---METADATA---
VENDOR: ClusterLabs
PRODUCT: Pacemaker
AFFECTED_VERSIONS: A flaw was found in Pacemaker. An unauthenticated remote attacker can exploit an integer overflow vulnerability in the remote message decompression process.
---END_METADATA---

Description Summary:
An integer overflow vulnerability in the Pacemaker CIB remote listener allows unauthenticated remote attackers to trigger memory corruption and denial of service.

Executive Summary:
An integer overflow flaw in the Pacemaker CIB remote listener poses a critical risk of denial of service from unauthenticated remote attackers.

Vulnerability Details

CVE-ID: CVE-2026-10649

Affected Software: ClusterLabs Pacemaker

Affected Versions: A flaw was found in Pacemaker. An unauthenticated remote attacker can exploit an integer overflow vulnerability in the remote message decompression process.

Vulnerability: This vulnerability involves an integer overflow in the remote message decompression process. An unauthenticated remote attacker can leverage this flaw to cause memory corruption and a denial of service (DoS) in the CIB remote listener.

Business Impact

With a CVSS score of 8.6, this vulnerability represents a significant risk to cluster availability. Successful exploitation results in the disruption of critical cluster management services, leading to potential system downtime and operational instability. While remote code execution is currently considered unlikely, the memory corruption aspect necessitates urgent remediation to prevent service outages.

Remediation Plan

Immediate Action: Apply the security patches provided by the vendor at https://github.com/clusterLabs/pacemaker/pull/4128.

Proactive Monitoring: Monitor the CIB remote listener logs for unusual traffic patterns or service crashes that may indicate exploitation attempts.

Compensating Controls: Implement network access controls to restrict access to the CIB remote listener port to only authorized management nodes.

Exploitation Status

Public Exploit Available: false

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

Given the high CVSS score and the potential for service disruption, administrators should prioritize the application of the vendor-provided patches. Immediate deployment of these updates is required to mitigate the risk of denial-of-service attacks against critical cluster infrastructure.

Executive Summary:
A critical remote code execution vulnerability, identified as CVE-2026-0756, has been discovered in github-kanban-mcp-server. This flaw allows an unauthenticated remote attacker to execute arbitrary commands on the server, potentially leading to a complete system compromise. Due to the lack of required authentication and the high severity score, this vulnerability poses a significant and immediate risk to affected organizations.

Vulnerability Details

CVE-ID: CVE-2026-0756

Affected Software: Multiple Products (specifically the github-kanban-mcp-server component)

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is a command injection flaw within the github-kanban-mcp-server. The specific weakness exists in how the application processes the create_issue parameter. An attacker can send a specially crafted request containing malicious commands within this parameter. The server fails to properly sanitize this user-supplied input before using it to execute a system call, allowing the injected commands to be executed on the underlying operating system with the privileges of the service account.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.8. Successful exploitation could lead to a complete compromise of the affected server. Potential consequences include theft or modification of sensitive data, deployment of ransomware, service disruption, and using the compromised server as a pivot point for further attacks within the internal network. The business risks include significant data breaches, reputational damage, financial loss, and potential regulatory fines.

Remediation Plan

Immediate Action: Organizations must prioritize the deployment of vendor-supplied patches. Update all affected instances of products containing the github-kanban-mcp-server component to the latest secure version immediately. After patching, review server access logs and application logs for any signs of compromise or exploitation attempts that may have occurred before the patch was applied.

Proactive Monitoring: Implement enhanced monitoring on affected systems. Security teams should look for unusual process execution initiated by the service account, unexpected outbound network connections from the server, and review web server access logs for requests to the vulnerable endpoint containing shell metacharacters (e.g., |, &, ;, $()) within the create_issue parameter.

Compensating Controls: If immediate patching is not feasible, consider implementing the following controls:

• Deploy a Web Application Firewall (WAF) with rules specifically designed to block command injection attempts targeting the create_issue parameter.
• Restrict network access to the affected application, allowing connections only from trusted IP addresses.
• If possible, run the service in a sandboxed or containerized environment with minimal privileges to limit the impact of a potential compromise.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of the publication date of January 23, 2026, there are no known public exploits available for this vulnerability. However, command injection vulnerabilities are typically straightforward to exploit once the technical details are understood. Threat actors are likely to develop exploit code rapidly.

Analyst Recommendation

Given the critical CVSS score of 9.8 and the fact that no authentication is required for exploitation, this vulnerability represents a severe and urgent threat. We strongly recommend that organizations identify all affected assets and apply the vendor-provided patches with the highest priority. Although this CVE is not currently on the CISA KEV list, its characteristics make it a prime candidate for future inclusion and active exploitation. Treat this vulnerability as an active threat and remediate it without delay.

Executive Summary:
A critical command injection vulnerability has been identified in the MCP Watch security scanner. This flaw allows an unauthenticated attacker to execute arbitrary commands on the underlying server by sending a maliciously crafted URL. Successful exploitation could result in a complete system compromise, leading to data theft, service disruption, or further network intrusion.

Vulnerability Details

CVE-ID: CVE-2025-66401

Affected Software: MCP Watch is a comprehensive security scanner for Model Context Protocol Multiple Products

Affected Versions: 0.1.2 and earlier

Vulnerability: The vulnerability exists within the cloneRepo method of the MCPScanner class. The application accepts a user-provided URL, githubUrl, and passes it directly to a system shell command (execSync) without proper input sanitization or validation. An attacker can exploit this by appending shell metacharacters (e.g., ;, |, &&, $(command)) to the URL, which allows them to inject and execute arbitrary commands with the privileges of the running application.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.8, reflecting the ease of exploitation and the potential for severe impact. A successful attack grants the adversary remote code execution (RCE) on the host machine, effectively giving them full control. This could lead to the theft of sensitive data, deployment of ransomware, complete disruption of services running on the server, or the use of the compromised system as a pivot point to attack other internal network resources.

Remediation Plan

Immediate Action: Update MCP Watch is a comprehensive security scanner for Model Context Protocol Multiple Products to the latest version. The vendor has released a patch that addresses this vulnerability by properly sanitizing the user-supplied URL before it is passed to the system shell. After patching, monitor for any signs of exploitation attempts and review historical access logs for indicators of compromise.

Proactive Monitoring: Security teams should monitor application and system logs for any requests to the cloneRepo method containing unusual URL formats or shell metacharacters (e.g., ;, |, &, $, (, )). Monitor for unexpected outbound network connections or processes being spawned by the MCP Watch application, such as sh, bash, curl, wget, or nc.

Compensating Controls: If immediate patching is not feasible, implement a Web Application Firewall (WAF) rule to block requests containing common shell metacharacters in the githubUrl parameter. Additionally, ensure the MCP Watch application is running with the lowest possible user privileges to limit the potential damage of a successful exploit.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Dec 1, 2025, there are no known public exploits or proof-of-concept code available for this vulnerability. However, given the straightforward nature of command injection flaws, it is highly likely that threat actors can independently develop an exploit with minimal effort.

Analyst Recommendation

Due to the critical CVSS score of 9.8 and the risk of unauthenticated remote code execution, this vulnerability poses a significant threat to the organization. Although it is not currently listed in the CISA KEV catalog, its severity demands immediate attention. We strongly recommend that all instances of the affected software be patched or taken offline immediately to prevent a potential compromise.

---METADATA---
VENDOR: GitHub
PRODUCT: Copilot
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability has been identified in GitHub Copilot 1. Further details regarding the specific nature of the flaw remain under investigation.

Executive Summary:
A high-severity security vulnerability has been identified in GitHub Copilot 1, posing a potential risk to the security of developer workflows and integrated environments.

Vulnerability Details

CVE-ID: CVE-2025-66389

Affected Software: GitHub Copilot

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability impacts GitHub Copilot 1. The specific mechanism of the flaw and the required level of user or service authentication to trigger the vulnerability are currently pending further vendor clarification.

Business Impact

A CVSS score of 7.5 indicates a high risk to software development integrity. If exploited, an attacker could potentially influence development environments or gain unauthorized insights into proprietary codebases, leading to significant intellectual property risk and potential supply chain compromise.

Remediation Plan

Immediate Action: Monitor official GitHub security advisories and promptly update all instances of the Copilot extension or service to the latest patched version.

Proactive Monitoring: Review developer environment logs and access patterns for any unusual behavior originating from the Copilot service integrations.

Compensating Controls: Enforce strict access control policies for developer accounts and utilize secure coding practices to limit the potential impact of tool-based vulnerabilities.

Exploitation Status

Public Exploit Available: false

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

Development teams should treat this advisory with high urgency. Ensure that all IDEs and server-side integrations utilizing GitHub Copilot are updated immediately upon the release of a vendor patch to maintain the integrity of the software development lifecycle.

Executive Summary:
A critical remote command injection vulnerability exists in the Apache bRPC software. This flaw allows a remote, unauthenticated attacker to execute arbitrary commands on the server by sending a specially crafted request to the built-in heap profiler service. Successful exploitation can lead to a complete compromise of the affected system, including data theft, service disruption, and further network intrusion.

Vulnerability Details

CVE-ID: CVE-2025-60021

Affected Software: Apache bRPC

Affected Versions: All versions prior to 1.15.0

Vulnerability: The bRPC heap profiler built-in service, accessible via the /pprof/heap endpoint, is vulnerable to remote command injection. The service improperly validates the extra_options parameter, passing user-supplied input directly to a command-line execution. An unauthenticated remote attacker can exploit this by crafting a request to the /pprof/heap endpoint with malicious shell commands embedded within the extra_options parameter, resulting in arbitrary code execution with the permissions of the bRPC service.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.8. A successful exploit allows an unauthenticated attacker to gain full control over the affected server. Potential consequences include the exfiltration of sensitive data, deployment of ransomware or other malware, complete service disruption, and the ability for an attacker to use the compromised system as a pivot point for further attacks within the organization's network. The ease of exploitation combined with the high impact poses a significant and immediate risk to business operations, data confidentiality, and system integrity.

Remediation Plan

Immediate Action: Organizations must immediately upgrade affected instances of Apache bRPC to version 1.15.0 or later to remediate this vulnerability. If an immediate upgrade is not feasible, the patch available at https://github.com/apache/brpc/pull/3101 should be applied manually. After patching, administrators should monitor for any signs of exploitation attempts by reviewing application and network access logs.

Proactive Monitoring: Security teams should actively monitor web server and application logs for any requests to the /pprof/heap endpoint. Specifically, look for requests containing suspicious or unexpected characters and commands within the extra_options parameter. Monitor system process tables for any unusual child processes being spawned by the bRPC service, which could indicate a successful compromise.

Compensating Controls: If patching or upgrading is not immediately possible, access to the bRPC built-in services, particularly the /pprof/ path, should be restricted at the network level. Use a firewall, reverse proxy, or other network access control lists (ACLs) to ensure that these diagnostic endpoints are only accessible from trusted internal IP addresses. If the heap profiler is not required for production use, it should be disabled entirely as a security best practice.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Jan 16, 2026, there are no known public exploits or active exploitation campaigns targeting this vulnerability. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. However, due to the critical severity and simplicity of exploitation, it is highly likely that proof-of-concept exploits will be developed and used by threat actors in the near future.

Analyst Recommendation

Given the critical CVSS score of 9.8 and the potential for complete system compromise from an unauthenticated attacker, this vulnerability represents a severe risk. We strongly recommend that all organizations using affected versions of Apache bRPC prioritize the deployment of the vendor-supplied patch or upgrade to version 1.15.0 immediately. The lack of current exploitation should not diminish the urgency, as high-severity vulnerabilities like this are attractive targets for attackers. Proactive patching is the most effective defense against potential future exploitation.

Executive Summary:
A critical command injection vulnerability has been identified in the Coolify management tool, rated 9.9 out of 10. This flaw allows a regular user to execute arbitrary commands on the server by entering malicious text into the "Git Repository" field when creating a project. Successful exploitation can lead to a complete compromise of the underlying server, including data theft, service disruption, and unauthorized access to the network.

Vulnerability Details

CVE-ID: CVE-2025-59157

Affected Software: Coolify

Affected Versions: All versions prior to 4.0.0-beta.420.7

Vulnerability: The vulnerability is a command injection flaw within the project creation workflow. The "Git Repository" input field fails to properly sanitize user-supplied data before passing it to a system shell for execution, likely during a git clone operation. An authenticated attacker with standard user privileges can craft a malicious payload (e.g., https://github.com/user/repo.git; id) and submit it as the repository URL. The server will execute the injected command (id) with the permissions of the Coolify application process, leading to remote code execution (RCE) on the host system.

Business Impact

This vulnerability is of critical severity with a CVSS score of 9.9, posing a significant threat to the organization. A successful exploit grants an attacker full control over the server hosting Coolify, enabling them to steal sensitive data such as application source code, database credentials, and API keys. The attacker could also disrupt services, install persistent backdoors, use the compromised server to attack other systems within the internal network (lateral movement), or deploy ransomware. The fact that a low-privileged user can trigger this vulnerability significantly increases the risk profile.

Remediation Plan

Immediate Action: Immediately upgrade all instances of Coolify to the patched version 4.0.0-beta.420.7 or newer. After patching, it is crucial to review server and application logs for any signs of past exploitation attempts, such as unusual commands or outbound network connections originating from the Coolify process.

Proactive Monitoring: Security teams should monitor application logs for project creation events containing malformed Git repository URLs, specifically those with shell metacharacters (e.g., ;, |, &&, $(), `). Monitor system processes for unexpected child processes being spawned by the Coolify service user. Implement network monitoring to detect anomalous outbound traffic from the Coolify server to unknown destinations.

Compensating Controls: If immediate patching is not feasible, implement a Web Application Firewall (WAF) with rules designed to detect and block common command injection patterns in HTTP requests to the Coolify application. Further restrict the operating system user account running the Coolify service by applying the principle of least privilege, limiting its ability to read/write files and execute system commands. Restrict all outbound network connectivity from the server except to explicitly approved endpoints.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of the publication date, January 5, 2026, there is no known public proof-of-concept exploit code, and the vulnerability is not being actively exploited in the wild. However, due to the critical CVSS score and the low complexity of exploitation, it is highly probable that threat actors will develop and deploy exploits in the near future. The vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog.

Analyst Recommendation

Given the critical severity (CVSS 9.9) and the risk of complete system compromise by a low-privileged user, this vulnerability represents an immediate and severe threat. We strongly recommend that all organizations using affected versions of Coolify apply the security update to version 4.0.0-beta.420.7 or later with the highest priority. Do not wait for evidence of active exploitation or for its addition to the CISA KEV catalog; the risk of compromise is too high to delay remediation.

Executive Summary:
A critical vulnerability has been discovered in the PLY (Python Lex-Yacc) library, allowing for remote code execution. The flaw stems from an undocumented and unsafe feature that deserializes user-supplied data without validation, enabling an attacker to run arbitrary code and completely compromise the affected system. Due to its high severity and the stealthy nature of the undocumented feature, this vulnerability poses a significant risk to organizations.

Vulnerability Details

CVE-ID: CVE-2025-56005

Affected Software: PLY (Python Lex-Yacc) library

Affected Versions: Version 3.11. See vendor advisory for a complete list of affected products utilizing this library.

Vulnerability: The vulnerability exists within the yacc() function of the PLY library, which contains an undocumented parameter named picklefile. This parameter accepts a path to a file which is then deserialized using Python's pickle.load() function. As pickle.load() does not validate the data it processes, an attacker can craft a malicious pickle file (.pkl) containing embedded code. By controlling the input to the picklefile parameter, an attacker can trick the application into loading this malicious file, resulting in Remote Code Execution (RCE) on the host system.

Business Impact

This vulnerability is rated as critical with a CVSS score of 9.8, reflecting the ease of exploitation and the potential for complete system compromise. A successful attack would grant an adversary full control over the affected application server, leading to severe consequences such as theft of sensitive data, deployment of ransomware, or using the compromised system to launch further attacks against the internal network. The undocumented nature of the feature introduces a significant risk of a persistent and difficult-to-detect backdoor, potentially leading to long-term compromise, reputational damage, and major business disruption.

Remediation Plan

Immediate Action: Immediately apply the security update provided by the vendor to patch the PLY library to the latest version. After patching, review system and application access logs for any signs of exploitation, such as unexpected file operations involving .pkl files or unusual process execution.

Proactive Monitoring:

• Log Analysis: Scrutinize application logs for any usage of the yacc() function where the picklefile parameter is present. Monitor file system audit logs for the creation or modification of .pkl files in unexpected locations.
• Network Monitoring: Watch for unusual outbound connections from servers running applications with the PLY library, as this could indicate a successful compromise and communication with a command-and-control server.
• Endpoint Detection: Use endpoint security tools to detect suspicious process execution originating from the application process, which could signal that the RCE vulnerability has been exploited.

Compensating Controls: If immediate patching is not feasible, implement the following controls:

• Input Sanitization: Strictly validate and sanitize all user-controlled input that could potentially be passed to the vulnerable function.
• Web Application Firewall (WAF): Deploy WAF rules to block requests containing patterns indicative of this attack, such as file paths ending in .pkl.
• Principle of Least Privilege: Run the affected application with the minimum permissions necessary to function, thereby limiting the potential impact of a successful code execution exploit.

Exploitation Status

Public Exploit Available: True

Analyst Notes: As of January 20, 2026, proof-of-concept (PoC) exploit code is publicly available. The vulnerability relies on insecure deserialization using Python's pickle module, which is a well-understood and easily exploitable flaw. The primary risk factor is that the vulnerable parameter is undocumented, meaning developers are likely unaware of its existence and the associated danger. While there are no confirmed reports of widespread exploitation in the wild, the availability of a PoC makes targeted attacks highly probable.

Analyst Recommendation

Given the critical CVSS score of 9.8 and the direct path to remote code execution, this vulnerability requires immediate attention. We strongly recommend that all affected systems be patched on an emergency basis. Due to the ease of exploitation, organizations should assume they are being targeted and hunt for evidence of compromise. Although this vulnerability is not currently on the CISA KEV list, its severity and the availability of a public exploit warrant treating it with the highest priority.

Executive Summary:
A critical vulnerability has been identified in the react-native-bottom-tabs library, affecting versions 0.9.2 and below. The flaw resides within a GitHub Actions workflow, which can be manipulated by an attacker to inject malicious code into the software build process. This could lead to a supply chain attack, where applications using this library are unknowingly distributed with malicious code, potentially compromising end-user data and systems.

Vulnerability Details

CVE-ID: CVE-2025-54594

Affected Software: react-native-bottom-tabs (and by extension, multiple downstream products that use this library)

Affected Versions: Versions 0.9.2 and below

Vulnerability: The vulnerability exists in the github/workflows/release-canary.yml GitHub Actions workflow. This workflow improperly handles context from pull requests, allowing for command injection. An unauthenticated attacker can craft a malicious pull request with specially formatted branch names or commit messages. When the workflow is triggered, these malicious strings are used in a script or command line environment without proper sanitization, leading to arbitrary code execution on the build runner. This compromise allows an attacker to alter the release artifacts, embedding malware or backdoors into the compiled library that is then published for developers to use.

Business Impact

This vulnerability is rated critical with a CVSS score of 9.1, reflecting its severe potential impact. Successful exploitation would result in a supply chain compromise, a highly effective attack vector. If your organization's applications use the vulnerable library, they could be trojanized to steal sensitive corporate or customer data, deploy ransomware, or use your infrastructure for further attacks. The consequences include significant reputational damage, loss of customer trust, regulatory fines for data breaches, and substantial financial costs associated with incident response and remediation.

Remediation Plan

Immediate Action:

• Identify all applications and systems within your environment that utilize the react-native-bottom-tabs library.
• Update the dependency to the latest patched version (above 0.9.2) in all affected projects.
• Rebuild and redeploy all applications that were built using the vulnerable library version to ensure they are free from any potential compromise.
• Review access logs for build systems and artifact repositories for any signs of unauthorized access or modification around the time of vulnerable builds.

Proactive Monitoring:

• Monitor build server logs for unusual commands, network connections to unknown endpoints, or unexpected script executions during the CI/CD process.
• Implement integrity checks and binary analysis on all third-party libraries and release artifacts to detect anomalies or malicious code.
• Monitor deployed applications for anomalous behavior, such as unexpected network traffic or high resource consumption, which could indicate a compromise.

Compensating Controls:

• If immediate patching is not feasible, temporarily disable the automated release-canary.yml workflow in your fork of the repository to prevent exploitation.
• Implement a strict Software Bill of Materials (SBOM) to maintain visibility and control over all software dependencies.
• Enforce code signing for all release artifacts and verify signatures upon deployment to ensure their integrity has not been compromised.
• Harden CI/CD pipelines by limiting permissions, requiring manual approvals for sensitive workflows, and scanning workflow configurations for vulnerabilities.

Exploitation Status

Public Exploit Available: false

Analyst Notes:
As of August 6, 2025, there are no known public exploits or active exploitation campaigns targeting this vulnerability. However, vulnerabilities in CI/CD pipelines are highly valued by threat actors for supply chain attacks. Due to the straightforward nature of the likely attack vector (e.g., a malicious pull request), proof-of-concept (PoC) code could be developed and released quickly. Any exploitation would result in a compromised version of the library, making it difficult to detect without deep binary analysis.

Analyst Recommendation
Given the critical severity (CVSS 9.1) and the potential for a high-impact supply chain attack, this vulnerability requires immediate attention. We strongly recommend that all teams immediately initiate the remediation plan. The highest priority is to identify all instances of the react-native-bottom-tabs library and update them to a patched version. Although this CVE is not currently on the CISA KEV list, its critical nature warrants treating it with the same level of urgency as a known exploited vulnerability. A post-remediation audit of CI/CD security practices and dependency management is also advised to prevent similar issues in the future.

---METADATA---
VENDOR: Docusaurus
PRODUCT: docusaurus-plugin-content-gists
AFFECTED_VERSIONS: Prior to 4.0.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A critical information disclosure vulnerability in the docusaurus-plugin-content-gists plugin allows unauthorized access to private or sensitive GitHub Gists.

Executive Summary:
Docusaurus users are at risk of sensitive information disclosure due to a flaw in the docusaurus-plugin-content-gists plugin versions prior to 4.0.0.

Vulnerability Details

CVE-ID: CVE-2025-53624

Affected Software: Docusaurus (docusaurus-plugin-content-gists)

Affected Versions: Prior to 4.0.0

Vulnerability: The vulnerability involves an improper data exposure flaw where the plugin inadvertently displays sensitive or private GitHub Gists on public-facing pages. This is an unauthenticated vulnerability where any visitor to the site could potentially view content not intended for public consumption.

Business Impact

With a CVSS score of 10.0, this represents a maximum-severity risk. Exposure of private Gists could lead to the leakage of proprietary code, API keys, credentials, or other sensitive configuration data, resulting in severe reputational damage and potential downstream security breaches.

Remediation Plan

Immediate Action: Upgrade the docusaurus-plugin-content-gists package to version 4.0.0 or later immediately.

Proactive Monitoring: Review existing public pages to ensure no unintended sensitive data is currently being exposed; conduct a search for leaked credentials within previously indexed Gists.

Compensating Controls: Temporarily disable the plugin if an immediate upgrade is not feasible to prevent further unauthorized data exposure.

Exploitation Status

Public Exploit Available: Not specified

Analyst Notes: As of Jul 9, 2025, 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 classified as critical due to the high likelihood of sensitive data exposure. All Docusaurus instances utilizing this plugin must be updated to version 4.0.0 or higher immediately to close the information disclosure vector.

---METADATA---
VENDOR: RSSNext
PRODUCT: Folo
AFFECTED_VERSIONS: RSSNext Folo: < 585c6a591440cd39f92374230ac5d65d7dd23d6a
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
RSSNext Folo is vulnerable to remote code execution via insecure GitHub Actions workflow configuration using pull_request_target.

Executive Summary:
An insecure GitHub Actions workflow configuration in RSSNext Folo allows unauthenticated attackers to execute arbitrary code, posing a critical risk to the development environment.

Vulnerability Details

CVE-ID: CVE-2025-53546

Affected Software: RSSNext Folo

Affected Versions: RSSNext Folo: < 585c6a591440cd39f92374230ac5d65d7dd23d6a

Vulnerability: This vulnerability involves the inclusion of functionality from an untrusted control sphere (CWE-829). By utilizing pull_request_target in the auto-fix-lint-format-commit.yml workflow, the application improperly executes untrusted code submitted via pull requests.

Business Impact

With a CVSS score of 9.1, this vulnerability represents a critical risk. Successful exploitation could lead to full compromise of the GitHub repository, potential exfiltration of secrets, or the introduction of malicious code into the software supply chain, resulting in severe reputational damage and operational disruption.

Remediation Plan

Immediate Action: Update the RSSNext Folo repository to the commit hash 585c6a591440cd39f92374230ac5d65d7dd23d6a or later to secure the workflow configuration.

Proactive Monitoring: Audit GitHub repository workflows for usage of pull_request_target and monitor CI/CD logs for unexpected execution patterns or unauthorized modifications.

Compensating Controls: Restrict GitHub Actions permissions to the minimum necessary level and implement branch protection rules that require manual approval for workflows triggered by external contributors.

Exploitation Status

Public Exploit Available: Yes

Analyst Notes: As of Jul 9, 2025, proof-of-concept exploit code is available for this vulnerability. Given the ease of automation, organizations should prioritize patching to prevent unauthorized repository access.

Analyst Recommendation

Due to the critical severity and the availability of exploit code, immediate remediation is mandatory. Developers must apply the referenced commit and review all CI/CD pipeline configurations to ensure that untrusted input cannot trigger privileged execution environments.

---METADATA---
VENDOR: Dräger
PRODUCT: Infinity Explorer C700
AFFECTED_VERSIONS: Dräger Infinity Explorer C700
---END_METADATA---

Description Summary:
Dräger Infinity Explorer C700 contains a privilege escalation vulnerability that allows attackers to break out of kiosk mode to access the underlying operating system.

Executive Summary:
A high-severity privilege escalation vulnerability in the Dräger Infinity Explorer C700 allows attackers to bypass kiosk mode and gain unauthorized access to the underlying operating system.

Vulnerability Details

CVE-ID: CVE-2019-25718

Affected Software: Dräger Infinity Explorer C700

Affected Versions: Dräger Infinity Explorer C700

Vulnerability: This vulnerability involves a breakout of kiosk mode via specific dialog interactions. Successful exploitation grants the attacker control over the underlying operating system, which can disrupt services and reporting for connected Delta Family patient monitors.

Business Impact

The CVSS score of 8.4 reflects the danger of this privilege escalation, which could result in the loss of integrity and availability of critical medical monitoring data. Unauthorized access to the underlying OS may allow attackers to manipulate patient information or cause device downtime, creating significant operational and clinical safety risks.

Remediation Plan

Immediate Action: Apply the available patch from the GitHub Advisory (GHSA-gv7p-xf8g-c233) immediately to resolve the kiosk mode breakout.

Proactive Monitoring: Review user permissions and access control logs for unauthorized attempts to interact with system dialogs or administrative functions.

Compensating Controls: Isolate affected devices on a restricted network segment and disable unnecessary input interfaces to limit the attack surface.

Exploitation Status

Public Exploit Available: false

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

Analyst Recommendation

This vulnerability presents a critical threat to medical device integrity. Organizations utilizing the Dräger Infinity Explorer C700 must prioritize applying the provided patch to prevent unauthorized system access and ensure the continued reliability of patient monitoring systems.