---METADATA---
VENDOR: Wavlink
PRODUCT: WL-WN579A3
AFFECTED_VERSIONS: 220323
---END_METADATA---

Description Summary:
A command injection vulnerability in the SetName/GuestWifi function of Wavlink WL-WN579A3 firmware allows remote attackers to execute arbitrary commands via POST requests.

Executive Summary:
Wavlink WL-WN579A3 routers are vulnerable to a critical remote command injection flaw that allows attackers to take full control of the device.

Vulnerability Details

CVE-ID: CVE-2026-4163

Affected Software: Wavlink WL-WN579A3

Affected Versions: 220323

Vulnerability: The vulnerability is located in the SetName/GuestWifi function within /cgi-bin/wireless.cgi. By manipulating POST requests, a remote attacker can bypass input validation and execute arbitrary system commands on the device.

Business Impact

A successful exploit allows an attacker to intercept network traffic, change DNS settings, or enlist the device into a botnet. Given the CVSS score of 9.8, the impact is Critical, as it compromises the gateway of the local network, potentially exposing all connected devices to further attacks.

Remediation Plan

Immediate Action: Upgrade the Wavlink WL-WN579A3 firmware to the latest available version immediately.

Proactive Monitoring: Check router logs for suspicious POST requests directed at /cgi-bin/wireless.cgi and monitor for unauthorized changes to Wi-Fi configurations.

Compensating Controls: Disable remote management interfaces and ensure that the administrative interface is not accessible from the public internet.

Exploitation Status

Public Exploit Available: Yes

Analyst Notes: As of March 16, 2026, a public exploit is available. This significantly increases the risk of active exploitation, as the barrier to entry for attackers is now minimal.

Analyst Recommendation

Because a public exploit exists, this vulnerability must be remediated with the highest urgency. Administrators should flash the updated firmware immediately and verify that the device has not already been compromised by checking for unauthorized persistent scripts.

---METADATA---
VENDOR: Microsoft
PRODUCT: Authenticator
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A vulnerability in Microsoft Authenticator allows an unauthorized attacker to disclose sensitive information over the network.

Executive Summary:
A critical information disclosure vulnerability in Microsoft Authenticator allows unauthorized attackers to access sensitive data over the network.

Vulnerability Details

CVE-ID: CVE-2026-41615

Affected Software: Microsoft Authenticator

Affected Versions: See vendor advisory

Vulnerability: An unauthorized attacker can exploit a flaw in the application's communication handling to access sensitive information, potentially compromising authentication security.

Business Impact

The compromise of information within the Microsoft Authenticator application could lead to the exposure of multi-factor authentication secrets or user identity data. With a CVSS score of 9.6, this vulnerability poses a severe risk to the entire identity security posture of an organization.

Remediation Plan

Immediate Action: Check the official Microsoft security advisory and update the Authenticator application to the latest available version immediately.

Proactive Monitoring: Monitor authentication logs for anomalous access patterns or unexpected device registration events that could indicate an attempt to exploit this information disclosure.

Compensating Controls: Enforce additional layers of identity protection, such as Conditional Access policies and FIDO2-based hardware security keys, to reduce reliance on vulnerable software-based MFA.

Exploitation Status

Public Exploit Available: No

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

Analyst Recommendation

Given the critical role of Microsoft Authenticator in securing enterprise access, this patch must be treated with high urgency. Organizations should ensure all users update their applications to the latest version to prevent unauthorized data exposure.

---METADATA---
VENDOR: Microsoft
PRODUCT: Visual Studio Code
AFFECTED_VERSIONS: 1.0.0 up to 1.119.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A session fixation and OS command injection vulnerability in Microsoft Visual Studio Code allows remote attackers to elevate privileges via network-based exploitation.

Executive Summary:
A critical session fixation and OS command injection flaw in Microsoft Visual Studio Code permits unauthorized attackers to achieve privilege escalation over a network.

Vulnerability Details

CVE-ID: CVE-2026-41613

Affected Software: Microsoft Visual Studio Code

Affected Versions: 1.0.0 up to 1.119.1

Vulnerability: This vulnerability combines session fixation (CWE-384) and OS command injection (CWE-78), allowing an attacker to manipulate session states and execute arbitrary commands on the underlying host. The vulnerability requires user interaction (UI:R) but does not require prior authentication (PR:N).

Business Impact

The ability to execute arbitrary OS commands leads to a total compromise of the affected system, including full unauthorized access and potential lateral movement within the network. The CVSS score of 8.8 reflects the high potential for system-wide impact, making this a critical priority for security teams.

Remediation Plan

Immediate Action: Update Microsoft Visual Studio Code to version 1.119.1 or later as soon as the update becomes available via the vendor's release channel.

Proactive Monitoring: Monitor system and process logs for anomalous command execution or unexpected child processes originating from the Visual Studio Code application.

Compensating Controls: Restrict network access to development environments and ensure that Visual Studio Code instances are executed with the minimum necessary system privileges to limit the potential impact of command injection.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of May 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The combination of command injection and session fixation makes this a high-risk vector for persistent compromise.

Analyst Recommendation

The criticality of this vulnerability cannot be overstated, as it provides a path for full remote code execution and privilege escalation. Administrators must ensure all Visual Studio Code installations are updated to the secure version immediately upon release to mitigate the risk of system-wide compromise.

---METADATA---
VENDOR: Charm
PRODUCT: Wish
AFFECTED_VERSIONS: 2.0.0 to 2.0.1 (exclusive)
---END_METADATA---

Description Summary:
A path traversal vulnerability in the SCP middleware of the Wish SSH server allows unauthorized file access and modification.

Executive Summary:
A path traversal vulnerability in Wish (versions 2.0.0-2.0.1) allows attackers to read or write arbitrary files on the server, requiring an immediate update.

Vulnerability Details

CVE-ID: CVE-2026-41589

Affected Software: Charm Wish

Affected Versions: 2.0.0 to 2.0.1 (exclusive)

Vulnerability: The SCP middleware fails to properly sanitize filenames, allowing attackers to use ../ sequences to escape the intended directory and manipulate server files.

Business Impact

With a CVSS score of 9.6, this vulnerability permits an attacker to compromise the integrity and confidentiality of the server. By writing arbitrary files, an attacker could gain persistent access or execute code, leading to complete server takeover.

Remediation Plan

Immediate Action: Update to Wish version 2.0.1 or later immediately.

Proactive Monitoring: Audit file system logs for unauthorized changes or attempts to access files outside of the configured root directory.

Compensating Controls: Run the SSH server in a containerized or chroot environment to minimize the impact of a potential path traversal.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 7, 2026, there is no public information indicating active exploitation. However, the nature of the flaw makes it a high-value target for automated scanners.

Analyst Recommendation

Upgrade to version 2.0.1 immediately. Given the risk of remote file system manipulation, this should be treated as a critical maintenance task.

---METADATA---
VENDOR: Zcash Foundation
PRODUCT: Zebra
AFFECTED_VERSIONS: zebrad prior to 4.3.1, zebra-script prior to 5.0.2
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Zebra node software fails to properly validate consensus rules for V5 and V4 transaction sighash types, potentially leading to a consensus split between Zebra and zcashd nodes.

Executive Summary:
A critical consensus validation flaw in the Zebra node software allows for transaction handling discrepancies that can lead to network splits and potential service disruption.

Vulnerability Details

CVE-ID: CVE-2026-41583

Affected Software: Zcash Foundation Zebra

Affected Versions: zebrad prior to 4.3.1 and zebra-script prior to 5.0.2

Vulnerability: This is a consensus logic error where the software fails to correctly validate sighash hash types for V5 and V4 transactions. The vulnerability is triggered by network-level transaction processing and does not require specific user authentication to manifest as a consensus split.

Business Impact

The vulnerability poses a severe risk to the integrity and availability of the Zcash network for nodes running Zebra. A successful exploitation creates a consensus split, effectively causing a fork in the blockchain where Zebra nodes accept transactions that zcashd nodes reject, leading to significant financial and operational instability. Given the CVSS score of 9.1, this is classified as a critical infrastructure risk.

Remediation Plan

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

Proactive Monitoring: Monitor node logs for synchronization errors, block validation failures, or unexpected forks compared to the primary zcashd network.

Compensating Controls: Ensure nodes are isolated within secure network segments and restrict peer-to-peer connections to trusted, verified nodes to mitigate the risk of malicious transaction propagation.

Exploitation Status

Public Exploit Available: Not specified

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

Operators of Zebra nodes must prioritize the update to the patched versions to restore consensus alignment with the broader Zcash network. Failure to apply these updates may result in nodes becoming desynchronized and unable to process valid network transactions.

---METADATA---
VENDOR: Note Mark
PRODUCT: Note Mark
AFFECTED_VERSIONS: 0.19.2
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A critical authentication bypass vulnerability in Note Mark 0.19.2 allows unauthenticated attackers to gain valid sessions by submitting a hard-coded password string.

Executive Summary:
Note Mark version 0.19.2 contains a critical authentication bypass vulnerability that allows unauthorized attackers to hijack user sessions without interaction.

Vulnerability Details

CVE-ID: CVE-2026-41571

Affected Software: Note Mark

Affected Versions: 0.19.2

Vulnerability: This vulnerability stems from an insecure fallback mechanism in the IsPasswordMatch function, where OIDC-registered users with empty passwords can be bypassed by submitting the string "null". This allows an unauthenticated attacker to successfully authenticate as any user who has not set a custom password.

Business Impact

The ability for an unauthenticated attacker to gain full access to user accounts poses a severe risk of data breach and unauthorized information disclosure. Given the CVSS score of 9.4, this vulnerability represents a critical threat to the confidentiality and integrity of all stored notes within the application.

Remediation Plan

Immediate Action: Upgrade the Note Mark application to version 0.19.3 or later to remove the insecure password fallback logic.

Proactive Monitoring: Review authentication logs for anomalous login attempts, specifically searching for the string "null" being used in password fields.

Compensating Controls: If immediate patching is not feasible, restrict access to the internal login endpoint at the network or Web Application Firewall (WAF) level.

Exploitation Status

Public Exploit Available: Not specified

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

This vulnerability is highly severe due to its ease of exploitation and the lack of required authentication. Organizations utilizing Note Mark 0.19.2 must prioritize the upgrade to version 0.19.3 immediately to prevent unauthorized access and potential data exfiltration.

---METADATA---
VENDOR: ChargePoint
PRODUCT: Home Flex
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A remote code execution (RCE) vulnerability exists in the ChargePoint Home Flex revssh service via command injection.

Executive Summary:
A command injection vulnerability in the ChargePoint Home Flex revssh service allows for remote code execution, posing a high security risk.

Vulnerability Details

CVE-ID: CVE-2026-4157

Affected Software: ChargePoint Home Flex

Affected Versions: See vendor advisory

Vulnerability: The revssh service on the ChargePoint Home Flex device is susceptible to command injection, which can be exploited to achieve remote code execution.

Business Impact

With a CVSS score of 7.5, this vulnerability presents a high risk. Successful exploitation allows an attacker to execute arbitrary commands on the charging station, potentially leading to unauthorized control of the device or lateral movement into the local network.

Remediation Plan

Immediate Action: Immediately apply security patches for internet-facing systems as provided by ChargePoint.

Proactive Monitoring: Monitor network traffic to and from the charging station for suspicious SSH-related activity or unauthorized command execution.

Compensating Controls: Restrict access to the charging station’s management interfaces and ensure it is isolated from the main corporate network where possible.

Exploitation Status

Public Exploit Available: False

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

Analyst Recommendation

Given the potential for remote code execution, it is imperative to apply security updates provided by the vendor immediately. Ensure that all internet-exposed devices are properly secured and monitored.

---METADATA---
VENDOR: Apache Software Foundation
PRODUCT: Apache Kvrocks
AFFECTED_VERSIONS: 2.8.0
---END_METADATA---

Description Summary:
Apache Kvrocks version 2.8.0 contains a vulnerability involving the improper handling of permissions, which could lead to unauthorized privilege escalation.

Executive Summary:
Apache Kvrocks version 2.8.0 is susceptible to an improper permission handling vulnerability that may allow attackers to bypass security controls and gain elevated privileges.

Vulnerability Details

CVE-ID: CVE-2026-41566

Affected Software: Apache Software Foundation Apache Kvrocks

Affected Versions: 2.8.0

Vulnerability: This vulnerability involves the improper enforcement of permissions or privileges within the software. It allows an attacker to perform actions that should be restricted, effectively bypassing intended security boundaries.

Business Impact

With a CVSS score of 9.4, this vulnerability presents a severe risk to data confidentiality and integrity. If exploited, an attacker could gain unauthorized administrative control over the database, leading to the exfiltration of sensitive information or unauthorized modification of stored data.

Remediation Plan

Immediate Action: Upgrade to Apache Kvrocks version 2.16.0 to remediate the permission handling deficiency.

Proactive Monitoring: Review administrative access logs and audit trails for unauthorized changes or attempts to perform restricted database operations.

Compensating Controls: Implement strict identity and access management (IAM) controls and ensure that the database service is not exposed to the public internet.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of June 25, 2026, there is no public information indicating active exploitation of this vulnerability. Despite the lack of active exploitation, the high CVSS score warrants immediate remediation to prevent potential privilege escalation.

Analyst Recommendation

This vulnerability represents a significant security weakness that could lead to full database compromise. Security teams should prioritize the update to version 2.16.0 to ensure that proper privilege enforcement is restored and that the environment remains protected against unauthorized access.

---METADATA---
VENDOR: ChargePoint
PRODUCT: Home Flex
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A stack-based buffer overflow vulnerability exists in the ChargePoint Home Flex OCPP getpreq function, leading to RCE.

Executive Summary:
A stack-based buffer overflow in the ChargePoint Home Flex OCPP service creates a high risk of remote code execution.

Vulnerability Details

CVE-ID: CVE-2026-4156

Affected Software: ChargePoint Home Flex

Affected Versions: See vendor advisory

Vulnerability: The OCPP getpreq function is affected by a stack-based buffer overflow, which can be leveraged by an attacker to overwrite memory and achieve remote code execution on the device.

Business Impact

The CVSS score of 7.5 underscores the high severity of this vulnerability. Successful exploitation could grant an attacker control over the charging station, potentially leading to device disruption or use as a foothold for further network attacks.

Remediation Plan

Immediate Action: Apply the vendor-provided security patches immediately, especially for devices exposed to the internet.

Proactive Monitoring: Review system logs for signs of abnormal service crashes or unexpected behavior in the OCPP communication interface.

Compensating Controls: Use network-level segmentation to isolate the charging station from critical business systems and restrict access to the device management interfaces.

Exploitation Status

Public Exploit Available: False

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

Analyst Recommendation

Given the risk of remote code execution via buffer overflow, administrators must prioritize the application of security patches. Ensure that ChargePoint Home Flex devices are updated to the latest firmware to mitigate this high-severity risk.

---METADATA---
VENDOR: ROS#
PRODUCT: ROS#
AFFECTED_VERSIONS: All versions < V2.2.2
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A path traversal vulnerability in ROS# versions prior to V2.2.2 allows remote attackers to access arbitrary files on the host device due to insufficient input sanitization.

Executive Summary:
ROS# versions prior to V2.2.2 are vulnerable to a critical path traversal flaw, enabling remote attackers to read unauthorized files from the host system.

Vulnerability Details

CVE-ID: CVE-2026-41551

Affected Software: ROS#

Affected Versions: All versions < V2.2.2

Vulnerability: This is a path traversal vulnerability caused by the failure to properly sanitize user-supplied input. This flaw allows a remote, unauthenticated attacker to escape intended directory boundaries and access sensitive files on the underlying filesystem.

Business Impact

The ability to perform arbitrary file reads can lead to the exposure of sensitive configuration files, credentials, or proprietary source code. With a CVSS score of 9.1, this vulnerability poses a severe risk of data exfiltration and credential theft, which could be leveraged for further lateral movement within the network.

Remediation Plan

Immediate Action: Update the ROS# software to version V2.2.2 or later to resolve the input sanitization defect.

Proactive Monitoring: Review system and application access logs for attempts to traverse directories (e.g., sequences like "../") in file-related requests.

Compensating Controls: Deploy a Web Application Firewall (WAF) or filesystem monitor configured to block or alert on directory traversal patterns targeting the application.

Exploitation Status

Public Exploit Available: Unknown

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

This path traversal vulnerability represents a significant security risk to any deployment of ROS#. Administrators must prioritize the transition to version V2.2.2 to prevent unauthorized file access and potential system-wide compromise.

---METADATA---
VENDOR: vLLM
PRODUCT: vLLM Inference Engine
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability exists within the vLLM inference and serving engine, potentially impacting the stability or security of LLM deployments.

Executive Summary:
A high-severity vulnerability in the vLLM inference engine could expose organizations to significant operational risk or unauthorized system interaction.

Vulnerability Details

CVE-ID: CVE-2026-41523

Affected Software: vLLM Inference Engine

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists within the inference and serving logic of the vLLM engine. Without further technical details from the vendor, it is treated as a high-risk component flaw requiring immediate attention to ensure the integrity of LLM model serving.

Business Impact

The vLLM engine is a critical component for large language model deployments. Successful exploitation could lead to service disruption, unauthorized model manipulation, or potential data leakage, justifying the CVSS score of 7.5. The business impact is substantial for organizations relying on these engines for production AI services.

Remediation Plan

Immediate Action: Update the vLLM engine to the latest stable release as specified in the official vendor security advisory.

Proactive Monitoring: Monitor vLLM logs for abnormal API requests or unexpected resource consumption that could indicate an attempt to exploit the inference engine.

Compensating Controls: Restrict network access to the vLLM inference API to trusted internal services only, minimizing the attack surface.

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

Security teams must prioritize updating the vLLM framework to mitigate this high-severity risk. Given the critical role of inference engines in AI infrastructure, failure to patch could lead to severe operational consequences; immediate verification of installed versions is advised.

---METADATA---
VENDOR: Neutrinolabs
PRODUCT: xrdp
AFFECTED_VERSIONS: < 0.10.6.1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A vulnerability exists in the xrdp open source RDP server where an integer overflow or wraparound flaw can be exploited by an unauthenticated attacker.

Executive Summary:
A critical integer overflow vulnerability in the xrdp RDP server allows unauthenticated attackers to potentially access sensitive information or cause service instability.

Vulnerability Details

CVE-ID: CVE-2026-41521

Affected Software: Neutrinolabs xrdp

Affected Versions: < 0.10.6.1

Vulnerability: This vulnerability is caused by an integer overflow or wraparound condition (CWE-190) within the xrdp service. It is remotely exploitable by an unauthenticated attacker, requiring no user interaction or prior system privileges.

Business Impact

The exploitation of this vulnerability poses a significant risk to organizational infrastructure, as it allows for unauthorized data disclosure and potential service disruption. With a CVSS score of 8.2, this high-severity flaw threatens the confidentiality of sessions established via RDP and could lead to system availability issues, impacting remote access operations.

Remediation Plan

Immediate Action: Update the xrdp package to version 0.10.6.1 or later immediately to incorporate the necessary security fixes.

Proactive Monitoring: Review RDP access logs and system resource utilization for unusual spikes or unexpected service crashes that may indicate exploitation attempts.

Compensating Controls: Restrict access to the RDP service using VPNs or IP whitelisting to ensure that only authorized networks can reach the server.

Exploitation Status

Public Exploit Available: No (unknown)

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

Analyst Recommendation

The high CVSS score reflects the significant risk posed by this vulnerability to remote access services. Organizations relying on xrdp should prioritize upgrading to version 0.10.6.1 to address the integer overflow flaw and prevent potential remote exploitation.

---METADATA---
VENDOR: NVIDIA
PRODUCT: garak
AFFECTED_VERSIONS: 1.0.0 to 1.4.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A remote code execution vulnerability exists in the NVIDIA garak AI scanner via JavaScript injection within the BrowserAutomation::PlaywrightService component.

Executive Summary:
A critical remote code execution vulnerability in NVIDIA garak allows unauthenticated attackers to execute arbitrary code via JavaScript injection.

Vulnerability Details

CVE-ID: CVE-2026-41512

Affected Software: NVIDIA garak

Affected Versions: 1.0.0 through 1.4.0

Vulnerability: The vulnerability exists in the BrowserAutomation::PlaywrightService component, which improperly handles input, allowing for JavaScript injection. This flaw can be triggered remotely without authentication, leading to full system compromise.

Business Impact

With a CVSS score of 9.9, this vulnerability represents an extreme risk to any environment deploying the garak AI scanner. Successful exploitation grants an attacker the ability to execute arbitrary code with the privileges of the garak service, leading to full system compromise, exfiltration of sensitive AI model data, or lateral movement within the network.

Remediation Plan

Immediate Action: Update the NVIDIA garak installation to version 1.4.1 or later immediately.

Proactive Monitoring: Monitor system logs for unusual process execution, unauthorized network connections originating from the scanner, or unexpected JavaScript execution errors in the Playwright service.

Compensating Controls: Deploy a Web Application Firewall (WAF) or equivalent inspection tool to filter malicious payloads targeting browser automation services. Restrict network access to the scanner to authorized internal subnets only.

Exploitation Status

Public Exploit Available: Not specified

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

Due to the remote code execution nature of this vulnerability and its near-maximum CVSS score, immediate patching is mandatory. Organizations must ensure that any instance of garak is updated to version 1.4.1 to eliminate the injection vector.

---METADATA---
VENDOR: math-codegen
PRODUCT: math-codegen
AFFECTED_VERSIONS: Prior to 0.4.3
---END_METADATA---

Description Summary:
The math-codegen library is vulnerable to RCE because it injects unsanitized string literals into a new Function body.

Executive Summary:
A critical RCE vulnerability in the math-codegen library allows attackers to execute arbitrary system commands through malicious mathematical expressions.

Vulnerability Details

CVE-ID: CVE-2026-41507

Affected Software: math-codegen

Affected Versions: Prior to version 0.4.3

Vulnerability: The cg.parse() function fails to sanitize user-controlled string input, allowing the injection of arbitrary code that is executed within the context of the application.

Business Impact

With a CVSS score of 9.8, this vulnerability allows for full RCE on any application utilizing the library for mathematical evaluation. This could lead to total server compromise, data theft, or the installation of malicious software within the application environment.

Remediation Plan

Immediate Action: Upgrade math-codegen to version 0.4.3 or later.

Proactive Monitoring: Audit applications for endpoints that pass user input into mathematical parsers and monitor for unusual child processes being spawned.

Compensating Controls: Implement strict input validation and sanitization for all user-provided mathematical expressions before passing them to the library.

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

Developers should immediately check their dependencies and update math-codegen. This is a classic injection vulnerability that can be easily exploited if not addressed.

---METADATA---
VENDOR: electerm
PRODUCT: electerm
AFFECTED_VERSIONS: Prior to 3.3.8
---END_METADATA---

Description Summary:
A command injection vulnerability exists in electerm prior to version 3.3.8, where remote version strings are unsafely passed to system commands.

Executive Summary:
A critical command injection vulnerability in electerm allows attackers to execute arbitrary system commands by manipulating remote version data.

Vulnerability Details

CVE-ID: CVE-2026-41501

Affected Software: electerm

Affected Versions: Prior to 3.3.8

Vulnerability: The runLinux() function in install.js improperly concatenates attacker-controlled remote version strings into a system rm -rf command. This lack of input validation allows for arbitrary command injection on the host system.

Business Impact

With a CVSS score of 9.8, this vulnerability allows for remote code execution with the privileges of the application. This could lead to a complete system compromise, including the deletion of files, installation of malware, or exfiltration of sensitive configuration data stored within the terminal client environment.

Remediation Plan

Immediate Action: Upgrade the electerm application to version 3.3.8 or later to resolve the unsafe command execution logic.

Proactive Monitoring: Monitor system logs for unauthorized file deletion attempts or unexpected child processes initiated by the electerm application.

Compensating Controls: Restrict the permissions of the user account running the terminal client to the minimum necessary level to contain the potential impact of an exploit.

Exploitation Status

Public Exploit Available: Unknown

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

Given the potential for full system compromise via command injection, organizations should prioritize updating electerm to version 3.3.8. Immediate remediation is necessary to prevent attackers from leveraging this vulnerability to gain control over local systems.

---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: PraisonAI
PRODUCT: PraisonAI
AFFECTED_VERSIONS: Prior to 4.6.9
---END_METADATA---

Description Summary:
PraisonAI fails to validate commands in parse_mcp_command(), allowing unauthenticated attackers to execute arbitrary system commands via subprocesses.

Executive Summary:
A critical vulnerability in PraisonAI allows unauthenticated remote attackers to achieve arbitrary code execution by exploiting improper command and argument validation.

Vulnerability Details

CVE-ID: CVE-2026-41497

Affected Software: PraisonAI PraisonAI

Affected Versions: Prior to 4.6.9

Vulnerability: The application lacks an allowlist or argument validation for the parse_mcp_command() function, enabling the execution of arbitrary system binaries such as bash or python. This flaw allows an unauthenticated attacker to inject malicious code via subprocess execution.

Business Impact

The exploitation of this vulnerability grants attackers full control over the underlying host system, leading to complete data exfiltration, service disruption, and potential lateral movement within the network. With a CVSS score of 9.8, this represents a critical risk that could result in total system compromise and severe reputational damage.

Remediation Plan

Immediate Action: Upgrade PraisonAI to version 4.6.9 or later to implement necessary command allowlisting and argument validation.

Proactive Monitoring: Inspect system process logs for anomalous subprocess invocations, specifically those originating from the application user context involving shell execution flags.

Compensating Controls: Deploy a Web Application Firewall (WAF) with strict input filtering to block requests containing suspicious command-line sequences or shell-related characters.

Exploitation Status

Public Exploit Available: false

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

Given the critical nature of this remote code execution vulnerability, immediate patching is required. Organizations should prioritize updating their PraisonAI deployment to version 4.6.9 to eliminate the underlying command injection vector and secure the environment against potential unauthorized access.

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

Description Summary:
Dgraph exposes sensitive process command-line arguments, including admin tokens, via an unauthenticated /debug/vars endpoint, allowing unauthorized administrative access.

Executive Summary:
A critical vulnerability in Dgraph allows unauthenticated attackers to steal administrative credentials through an exposed debug endpoint, leading to full system compromise.

Vulnerability Details

CVE-ID: CVE-2026-41492

Affected Software: Dgraph

Affected Versions: Prior to 25.3.3

Vulnerability: The vulnerability involves an information disclosure flaw where the process command line, containing sensitive security tokens, is exposed via the unauthenticated /debug/vars endpoint. An unauthenticated attacker can retrieve these tokens and replay them to gain administrative control over the database.

Business Impact

The ability for an unauthenticated user to retrieve administrative tokens poses a severe risk to data integrity and confidentiality. With a CVSS score of 9.8, this flaw facilitates complete unauthorized administrative access, potentially leading to total database exfiltration, unauthorized configuration changes, and severe operational disruption.

Remediation Plan

Immediate Action: Upgrade Dgraph instances to version 25.3.3 or later immediately to restrict access to the /debug/vars endpoint.

Proactive Monitoring: Review access logs for unusual requests to the /debug/vars path and monitor for unauthorized use of administrative tokens.

Compensating Controls: If immediate patching is not possible, implement network-level access controls to restrict access to the Alpha node's administrative ports to trusted management IPs only.

Exploitation Status

Public Exploit Available: Unknown

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

Analyst Recommendation

This vulnerability represents a critical security oversight that allows for trivial credential theft. Organizations must prioritize the upgrade to 25.3.3 to close the unauthorized access vector provided by the debug interface.

---METADATA---
VENDOR: Sonos
PRODUCT: Era 300
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
The Sonos Era 300 is vulnerable to remote code execution due to an out-of-bounds memory access issue within SMB response handling.

Executive Summary:
A critical remote code execution vulnerability in the Sonos Era 300 allows unauthenticated attackers to execute arbitrary code at the kernel level.

Vulnerability Details

CVE-ID: CVE-2026-4149

Affected Software: Sonos Era 300

Affected Versions: See vendor advisory

Vulnerability: This is an out-of-bounds memory access vulnerability in the handling of the DataOffset field within SMB responses. The flaw permits unauthenticated remote attackers to execute code in the kernel context.

Business Impact

With a CVSS score of 10.0, this is a critical-severity issue. An attacker could achieve full control over the device, potentially using it as a beachhead for further network exploitation, data interception, or denial-of-service against the local environment.

Remediation Plan

Immediate Action: Update the Sonos Era 300 firmware to the latest version provided by the manufacturer.

Proactive Monitoring: Monitor network traffic for unusual SMB protocol activity or unauthorized connection attempts targeting Sonos devices.

Compensating Controls: Isolate Sonos devices on a restricted, non-critical VLAN to limit the potential impact of a device-level compromise.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of April 11, 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 kernel-level impact and the potential for device control, immediate firmware updates are essential. Network administrators should ensure these devices are appropriately segmented.

---METADATA---
VENDOR: Pi-hole
PRODUCT: Pi-hole
AFFECTED_VERSIONS: >= 6.0, < 6.4.2
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Pi-hole contains vulnerabilities related to incorrect permission assignment and privilege management, potentially allowing low-privileged local users to escalate privileges or modify system configurations.

Executive Summary:
A critical privilege management vulnerability in Pi-hole allows authenticated local users to potentially gain unauthorized control over system configurations and resources.

Vulnerability Details

CVE-ID: CVE-2026-41489

Affected Software: Pi-hole Pi-hole

Affected Versions: >= 6.0, < 6.4.2

Vulnerability: This vulnerability involves incorrect permission assignment and improper privilege management, which can be leveraged by an authenticated local user to manipulate critical system settings.

Business Impact

With a CVSS score of 8.8, this vulnerability poses a severe threat to the integrity and availability of the DNS sinkhole. An attacker who successfully exploits these permissions could modify DNS responses, redirect traffic, or compromise the underlying host, leading to a complete loss of system security.

Remediation Plan

Immediate Action: Update Pi-hole to version 6.4.2 or later to address the privilege management and permission flaws.

Proactive Monitoring: Audit system logs for unexpected configuration changes or unauthorized attempts to access restricted file paths and system resources.

Compensating Controls: Apply the principle of least privilege to the underlying operating system and restrict local login access to the server hosting Pi-hole.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 13, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The flaw is inherently dangerous due to the potential for full system compromise.

Analyst Recommendation

The severity of this issue necessitates an immediate update to the patched version. Administrators should also review current user access rights on the host machine to ensure that no unauthorized users have the ability to execute code or modify configurations within the Pi-hole environment.

---METADATA---
VENDOR: Saltcorn
PRODUCT: Saltcorn
AFFECTED_VERSIONS: Prior to 1.4.6, 1.5.6, and 1.6.0-beta.5
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A SQL injection vulnerability in Saltcorn's mobile-sync routes allows authenticated low-privilege users to execute arbitrary queries, leading to potential full database exfiltration.

Executive Summary:
A critical SQL injection flaw in Saltcorn allows low-privilege authenticated users to extract sensitive database content and compromise system configuration.

Vulnerability Details

CVE-ID: CVE-2026-41478

Affected Software: Saltcorn

Affected Versions: Prior to 1.4.6, 1.5.6, and 1.6.0-beta.5

Vulnerability: The vulnerability is a SQL injection flaw located within mobile-sync routes. An authenticated user with read access to at least one table can leverage unsanitized sync parameters to inject malicious SQL commands, which are then executed by the backend database.

Business Impact

With a CVSS score of 9.9, this vulnerability carries an extremely high risk of data breach. An attacker can extract administrative credentials, configuration secrets, and proprietary business data, or perform destructive database operations, resulting in significant reputational and operational damage.

Remediation Plan

Immediate Action: Update Saltcorn to version 1.4.6, 1.5.6, or 1.6.0-beta.5 depending on your deployment branch.

Proactive Monitoring: Monitor database query logs for anomalous or high-frequency query patterns originating from the mobile-sync endpoints.

Compensating Controls: Deploy a Web Application Firewall (WAF) with SQL injection protection rules to inspect and filter malicious traffic directed at sync routes.

Exploitation Status

Public Exploit Available: Unknown

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

Analyst Recommendation

Given the ease with which this vulnerability can be exploited by an authenticated user, patching is mandatory. Administrators should verify their current version and apply the appropriate update immediately to prevent unauthorized data access.

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

Description Summary:
Deskflow, an application for sharing keyboards and mice across computers, is vulnerable to a high-severity security flaw that could lead to unauthorized access.

Executive Summary:
A vulnerability in the Deskflow keyboard and mouse sharing software presents a high-severity risk to cross-computer security and user session integrity.

Vulnerability Details

CVE-ID: CVE-2026-41477

Affected Software: Deskflow

Affected Versions: See vendor advisory for affected versions

Vulnerability: This vulnerability affects Deskflow, which enables input sharing between multiple machines. A CVSS score of 7.8 suggests the potential for unauthorized access or session hijacking, likely due to weak authentication or insecure data transmission between the connected client and server machines.

Business Impact

The CVSS score of 7.8 indicates a high risk to workstations and connected environments. Exploitation could allow an attacker to hijack a user's mouse and keyboard inputs across multiple machines, potentially leading to unauthorized data entry or command execution on systems the attacker should not control.

Remediation Plan

Immediate Action: Update the Deskflow application to the latest version immediately to patch potential input-sharing vulnerabilities.

Proactive Monitoring: Observe connected workstations for unexpected mouse/keyboard activity or connection attempts from unknown sources.

Compensating Controls: Use encrypted connections and restrict Deskflow communication to trusted, authenticated networks only.

Exploitation Status

Public Exploit Available: false

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

Analyst Recommendation

Organizations using keyboard/mouse sharing software should treat this vulnerability seriously. Update all Deskflow instances to ensure that input streams remain secure and authenticated between devices.

---METADATA---
VENDOR: ProjeQtor
PRODUCT: ProjeQtor
AFFECTED_VERSIONS: 7.0 through 12.4.3
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
An unauthenticated SQL injection vulnerability in ProjeQtor's login functionality allows remote attackers to execute arbitrary SQL commands via the username field.

Executive Summary:
ProjeQtor versions 7.0 through 12.4.3 are vulnerable to a critical unauthenticated SQL injection flaw that could lead to full system compromise.

Vulnerability Details

CVE-ID: CVE-2026-41462

Affected Software: ProjeQtor ProjeQtor

Affected Versions: 7.0 through 12.4.3

Vulnerability: This is an unauthenticated SQL injection vulnerability (CWE-89) located in the login function. Because the application fails to sanitize the username input before concatenating it into a database query, an unauthenticated remote attacker can inject malicious SQL payloads.

Business Impact

Successful exploitation allows an attacker to bypass authentication, create unauthorized administrative accounts, exfiltrate sensitive database contents, and potentially execute OS-level commands. Given the CVSS score of 9.8, this flaw poses an extreme risk to data confidentiality, integrity, and availability, effectively granting an attacker total control over the affected instance.

Remediation Plan

Immediate Action: Update ProjeQtor to version 12.4.4 or later immediately to apply the required input sanitization and parameterization fixes.

Proactive Monitoring: Review web server and database logs for suspicious authentication attempts, specifically looking for SQL syntax patterns or unexpected character sequences in login requests.

Compensating Controls: Deploy a Web Application Firewall (WAF) with updated rulesets designed to detect and block common SQL injection patterns targeting authentication endpoints.

Exploitation Status

Public Exploit Available: Yes — a public proof-of-concept exists on GitHub.

Analyst Notes: As of April 27, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The flaw is highly accessible as it requires no prior authentication to trigger.

Analyst Recommendation

The critical nature of this vulnerability, combined with the availability of public proof-of-concept code, necessitates immediate patching. Administrators should prioritize upgrading to version 12.4.4 across all instances to prevent potential unauthorized access and complete system takeover.