OpenClaw versions 2026
Description
OpenClaw versions 2026
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Search and filter 21745 vulnerabilities with AI analyst insights
OpenClaw versions 2026
OpenClaw versions 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw versions from 2026
OpenClaw versions from 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw versions 2026
OpenClaw versions 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw before 2026
OpenClaw before 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Unauthenticated Broken Authentication in CloudSecure WP Security <= 1
Unauthenticated Broken Authentication in CloudSecure WP Security <= 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability exists in BIG-IP and BIG-IQ systems where a highly privileged, authenticated attacker with at least the Certificate Manager role can m...
A vulnerability exists in BIG-IP and BIG-IQ systems where a highly privileged, authenticated attacker with at least the Certificate Manager role can modify configuration objects that allow running arbitrary commands
---METADATA---
VENDOR: F5
PRODUCT: BIG-IP, BIG-IQ
AFFECTED_VERSIONS: F5 BIG-IP: 21.0.0 up to 21.0.0.2, 17.5.0 up to 17.5.1.6, 17.1.0 up to 17.1.3.2, 16.1.0 and later; F5 BIG-IQ: 8.4.0 and later
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A privilege management vulnerability in F5 BIG-IP and BIG-IQ allows a highly privileged authenticated user with the Certificate Manager role to execute arbitrary commands via configuration modifications.
Executive Summary:
A critical privilege management vulnerability in F5 BIG-IP and BIG-IQ enables authenticated users with specific administrative roles to execute arbitrary system commands.
Vulnerability Details
CVE-ID: CVE-2026-42406
Affected Software: F5 BIG-IP and BIG-IQ
Affected Versions: F5 BIG-IP: 21.0.0 up to 21.0.0.2, 17.5.0 up to 17.5.1.6, 17.1.0 up to 17.1.3.2, 16.1.0 and later; F5 BIG-IQ: 8.4.0 and later
Vulnerability: This is a privilege management flaw (CWE-267) where the "Certificate Manager" role is granted unsafe permissions. An authenticated attacker with this role can manipulate configuration objects to achieve command execution.
Business Impact
Successful exploitation grants an attacker the ability to execute arbitrary commands on the system, leading to a complete compromise of the F5 appliance. With a CVSS score of 8.7, this risk is severe, as it could result in full administrative control over critical network security infrastructure.
Remediation Plan
Immediate Action: Apply the vendor-supplied security updates immediately, specifically upgrading to versions 21.1.0 or later as specified by F5.
Proactive Monitoring: Audit the activity of users assigned the "Certificate Manager" role and review system configuration logs for unauthorized changes.
Compensating Controls: Restrict access to administrative interfaces to trusted management subnets and enforce the principle of least privilege for all administrative accounts.
Exploitation Status
Public Exploit Available: Unknown.
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 vulnerability is restricted to users who have already gained access to a highly privileged role.
Analyst Recommendation
Administrators must prioritize patching these F5 systems to mitigate the risk of privilege escalation. Given the potential for full system compromise, verify that all administrative accounts are strictly managed and monitored until the software updates are successfully applied.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Apache Neethi does not properly detect circular references in policy definitions
Apache Neethi does not properly detect circular references in policy definitions
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Apache Neethi is vulnerable to a Denial of Service attack through algorithmic complexity in policy normalization
Apache Neethi is vulnerable to a Denial of Service attack through algorithmic complexity in policy normalization
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in YITH YITH WooCommerce Product Add-Ons allows Bli...
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in YITH YITH WooCommerce Product Add-Ons allows Blind SQL Injection
---METADATA---
VENDOR: YITH
PRODUCT: WooCommerce Product Add-Ons
AFFECTED_VERSIONS: up to and including 4.29.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A Blind SQL injection vulnerability in the YITH WooCommerce Product Add-Ons plugin allows an authenticated administrator to inject malicious SQL commands.
Executive Summary:
An authenticated SQL injection vulnerability in the YITH WooCommerce Product Add-Ons plugin could allow an administrator to compromise database integrity.
Vulnerability Details
CVE-ID: CVE-2026-42383
Affected Software: YITH WooCommerce Product Add-Ons
Affected Versions: up to and including 4.29.0
Vulnerability: The plugin fails to properly neutralize special elements in SQL commands (CWE-89), allowing an attacker with administrative privileges to execute blind SQL injection attacks.
Business Impact
Exploitation of this vulnerability could allow an attacker to extract sensitive information from the WordPress database or modify data, leading to severe confidentiality and integrity impacts. Although the CVSS score is 7.6, the requirement for administrative privileges mitigates the risk for unauthenticated users, though it remains a critical concern for compromised administrative accounts.
Remediation Plan
Immediate Action: Update the YITH WooCommerce Product Add-Ons plugin to version 4.29.1 or later immediately.
Proactive Monitoring: Review database query logs for suspicious activity, specifically focusing on unexpected or malformed SQL statements originating from administrative sessions.
Compensating Controls: Implement a Web Application Firewall (WAF) with rules configured to detect and block SQL injection patterns to provide a layer of protection while updates are being staged.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of May 21, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability’s reliance on high-level administrative privileges significantly constrains the attack surface.
Analyst Recommendation
Administrators must update the plugin to the latest version to close this injection vector. Given the sensitive nature of database interactions in e-commerce environments, ensuring the plugin is patched is essential to protecting customer data and maintaining site integrity against potential administrative account compromise.
Apply vendor patches immediately. Review database access controls and enable query logging.
Unauthenticated Local File Inclusion in Audrey <= 1
Unauthenticated Local File Inclusion in Audrey <= 1
---METADATA---
VENDOR: Elated-Themes
PRODUCT: Audrey
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
An unauthenticated Local File Inclusion (LFI) vulnerability in the Audrey theme allows remote attackers to read arbitrary files from the server's filesystem.
Executive Summary:
A critical Local File Inclusion vulnerability in the Elated-Themes Audrey theme allows unauthenticated attackers to access sensitive server files, threatening overall system integrity.
Vulnerability Details
CVE-ID: CVE-2026-42382
Affected Software: Elated-Themes Audrey
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability consists of a Local File Inclusion (LFI) flaw that can be triggered by unauthenticated users. The vulnerability allows an attacker to access files outside the intended web directory, potentially exposing sensitive application logic or environment variables.
Business Impact
The ability for an unauthenticated user to read arbitrary files presents a significant security risk, including the compromise of sensitive credentials and configuration data. With a CVSS score of 8.1, the potential for unauthorized data disclosure and subsequent escalation of privileges warrants immediate attention to protect business assets.
Remediation Plan
Immediate Action: Update the Audrey theme to the latest version provided by Elated-Themes to patch the underlying file inclusion vulnerability.
Proactive Monitoring: Monitor server logs for suspicious URL patterns, specifically those attempting to navigate the file system using path traversal characters.
Compensating Controls: Utilize a Web Application Firewall (WAF) to filter and block requests that exhibit signs of path traversal or unauthorized file access attempts.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of July 3, 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 high-risk entry point into the server environment. It is imperative that security teams prioritize updating the affected theme to the most recent version to mitigate the risk of unauthorized file access and potential further exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Insertion of Sensitive Information Into Sent Data vulnerability in WPDeveloper Templately allows Retrieve Embedded Sensitive Data
Insertion of Sensitive Information Into Sent Data vulnerability in WPDeveloper Templately allows Retrieve Embedded Sensitive Data
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
D-Link DIR-456U Hardware Revision A1 (End-of-Life, EOL) contains a hardcoded telnet backdoor. The device starts a telnet daemon at boot via /etc/init0...
D-Link DIR-456U Hardware Revision A1 (End-of-Life, EOL) contains a hardcoded telnet backdoor. The device starts a telnet daemon at boot via /etc/init0.d/S80telnetd.sh with the username "Alphanetworks" and the static password "whdrv01_dlob_dir456U" read from /etc/config/image_sign. The custom telnetd binary accepts a -u user:password flag, and the custom login binary uses strcmp() to validate credentials. Successful authentication grants an unauthenticated attacker on the local network a root shell with full administrative control. The device has reached End-of-Life (EOL) and will not receive patches.
---METADATA---
VENDOR: D-Link
PRODUCT: DIR-456U
AFFECTED_VERSIONS: Hardware Revision A1 (End-of-Life)
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
D-Link DIR-456U Rev A1 contains a hardcoded telnet backdoor, allowing unauthenticated attackers on the local network to gain full root administrative control.
Executive Summary:
A critical hardcoded backdoor in the D-Link DIR-456U allows unauthorized remote attackers to gain full root-level administrative access to the device.
Vulnerability Details
CVE-ID: CVE-2026-42376
Affected Software: D-Link DIR-456U
Affected Versions: Hardware Revision A1 (End-of-Life)
Vulnerability: The device features a hardcoded telnet backdoor utilizing a static username and password combination. This allows an unauthenticated attacker on the local network to bypass authentication mechanisms and execute commands with root privileges.
Business Impact
This vulnerability carries a CVSS score of 9.8, indicating a critical risk of full system compromise. Because the device has reached End-of-Life (EOL), it will not receive security updates, leaving the network permanently exposed to potential lateral movement, data interception, or the use of the device as a persistent foothold for attackers within the internal network.
Remediation Plan
Immediate Action: As this product is EOL and no patch will be provided, the only effective remediation is to retire and decommission the affected D-Link DIR-456U device immediately.
Proactive Monitoring: Monitor network traffic for unauthorized telnet connections (port 23) originating from or directed toward the device.
Compensating Controls: If immediate replacement is not possible, place the device on an isolated, restricted VLAN and disable all telnet access via firewall rules to block unauthorized inbound connections.
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—a hardcoded credential accessible to any local network user—the potential for exploitation is extremely high.
Analyst Recommendation
Given that the vendor has declared this device End-of-Life, there is no path to remediation through patching. Organizations must prioritize the replacement of this hardware with a supported product to eliminate the risk of unauthorized administrative access and potential network-wide compromise.
Update D-Link DIR to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
D-Link DIR-600L Hardware Revision A1 (End-of-Life) contains a hardcoded telnet backdoor. The device starts a telnet daemon at boot via /bin/telnetd.sh...
D-Link DIR-600L Hardware Revision A1 (End-of-Life) contains a hardcoded telnet backdoor. The device starts a telnet daemon at boot via /bin/telnetd.sh with the username "Alphanetworks" and the static password "wrgn35_dlwbr_dir600l" read from /etc/alpha_config/image_sign. The custom telnetd binary accepts a -u user:password flag, and the custom login binary uses strcmp() to validate credentials. Successful authentication grants an unauthenticated attacker on the local network a root shell with full administrative control. The device has reached End-of-Life (EOL) and will not receive patches.
---METADATA---
VENDOR: D-Link
PRODUCT: DIR-600L
AFFECTED_VERSIONS: Hardware Revision A1 (End-of-Life)
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
D-Link DIR-600L Rev A1 contains a hardcoded telnet backdoor, allowing unauthenticated attackers on the local network to gain full root administrative control.
Executive Summary:
A critical hardcoded backdoor in the D-Link DIR-600L allows unauthorized remote attackers to gain full root-level administrative access to the device.
Vulnerability Details
CVE-ID: CVE-2026-42375
Affected Software: D-Link DIR-600L
Affected Versions: Hardware Revision A1 (End-of-Life)
Vulnerability: The device features a hardcoded telnet backdoor utilizing a static username and password combination. This allows an unauthenticated attacker on the local network to bypass authentication mechanisms and execute commands with root privileges.
Business Impact
This vulnerability carries a CVSS score of 9.8, indicating a critical risk of full system compromise. Because the device has reached End-of-Life (EOL), it will not receive security updates, leaving the network permanently exposed to potential lateral movement, data interception, or the use of the device as a persistent foothold for attackers within the internal network.
Remediation Plan
Immediate Action: As this product is EOL and no patch will be provided, the only effective remediation is to retire and decommission the affected D-Link DIR-600L device immediately.
Proactive Monitoring: Monitor network traffic for unauthorized telnet connections (port 23) originating from or directed toward the device.
Compensating Controls: If immediate replacement is not possible, place the device on an isolated, restricted VLAN and disable all telnet access via firewall rules to block unauthorized inbound connections.
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—a hardcoded credential accessible to any local network user—the potential for exploitation is extremely high.
Analyst Recommendation
Given that the vendor has declared this device End-of-Life, there is no path to remediation through patching. Organizations must prioritize the replacement of this hardware with a supported product to eliminate the risk of unauthorized administrative access and potential network-wide compromise.
Update D-Link DIR to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
D-Link DIR-600L Hardware Revision B1 (End-of-Life) contains a hardcoded telnet backdoor. The device starts a telnet daemon at boot via /bin/telnetd.sh...
D-Link DIR-600L Hardware Revision B1 (End-of-Life) contains a hardcoded telnet backdoor. The device starts a telnet daemon at boot via /bin/telnetd.sh with the username "Alphanetworks" and the static password "wrgn61_dlwbr_dir600L" read from /etc/alpha_config/image_sign. The custom telnetd binary accepts a -u user:password flag, and the custom login binary uses strcmp() to validate credentials. Successful authentication grants an unauthenticated attacker on the local network a root shell with full administrative control. The device has reached End-of-Life (EOL) and will not receive patches.
---METADATA---
VENDOR: D-Link
PRODUCT: DIR-600L
AFFECTED_VERSIONS: Hardware Revision B1 (End-of-Life)
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
D-Link DIR-600L Rev B1 contains a hardcoded telnet backdoor, allowing unauthenticated attackers on the local network to gain full root administrative control.
Executive Summary:
A critical hardcoded backdoor in the D-Link DIR-600L allows unauthorized remote attackers to gain full root-level administrative access to the device.
Vulnerability Details
CVE-ID: CVE-2026-42374
Affected Software: D-Link DIR-600L
Affected Versions: Hardware Revision B1 (End-of-Life)
Vulnerability: The device features a hardcoded telnet backdoor utilizing a static username and password combination. This allows an unauthenticated attacker on the local network to bypass authentication mechanisms and execute commands with root privileges.
Business Impact
This vulnerability carries a CVSS score of 9.8, indicating a critical risk of full system compromise. Because the device has reached End-of-Life (EOL), it will not receive security updates, leaving the network permanently exposed to potential lateral movement, data interception, or the use of the device as a persistent foothold for attackers within the internal network.
Remediation Plan
Immediate Action: As this product is EOL and no patch will be provided, the only effective remediation is to retire and decommission the affected D-Link DIR-600L device immediately.
Proactive Monitoring: Monitor network traffic for unauthorized telnet connections (port 23) originating from or directed toward the device.
Compensating Controls: If immediate replacement is not possible, place the device on an isolated, restricted VLAN and disable all telnet access via firewall rules to block unauthorized inbound connections.
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—a hardcoded credential accessible to any local network user—the potential for exploitation is extremely high.
Analyst Recommendation
Given that the vendor has declared this device End-of-Life, there is no path to remediation through patching. Organizations must prioritize the replacement of this hardware with a supported product to eliminate the risk of unauthorized administrative access and potential network-wide compromise.
Update D-Link DIR to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
D-Link DIR-605L Hardware Revision B2 (End-of-Life, EOL) contains a hardcoded telnet backdoor. The device starts a telnet daemon at boot via /bin/telne...
D-Link DIR-605L Hardware Revision B2 (End-of-Life, EOL) contains a hardcoded telnet backdoor. The device starts a telnet daemon at boot via /bin/telnetd.sh with the username "Alphanetworks" and the static password "wrgn76_dlwbr_dir605L" read from /etc/alpha_config/image_sign. The custom telnetd binary accepts a -u user:password flag, and the custom login binary uses strcmp() to validate credentials. Successful authentication grants an unauthenticated attacker on the local network a root shell with full administrative control. The device has reached End-of-Life (EOL) and will not receive patches.
---METADATA---
VENDOR: D-Link
PRODUCT: DIR-605L
AFFECTED_VERSIONS: Hardware Revision B2 (End-of-Life)
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
D-Link DIR-605L revision B2 contains a hardcoded telnet backdoor, allowing unauthenticated attackers on the local network to gain full administrative root access.
Executive Summary:
A critical hardcoded backdoor in the D-Link DIR-605L router exposes the device to complete administrative compromise by unauthenticated attackers.
Vulnerability Details
CVE-ID: CVE-2026-42373
Affected Software: D-Link DIR-605L
Affected Versions: Hardware Revision B2 (End-of-Life)
Vulnerability: The device features a hardcoded telnet backdoor with static credentials, enabling an unauthenticated attacker on the local network to obtain a root shell via the telnet daemon.
Business Impact
This vulnerability carries a CVSS score of 9.8, reflecting its critical severity. Successful exploitation grants an attacker full administrative control over the network gateway, potentially leading to total network interception, internal reconnaissance, and the deployment of persistent malware within the infrastructure.
Remediation Plan
Immediate Action: Given the device has reached End-of-Life (EOL) and will not receive a patch, the only effective remediation is to retire and replace the hardware immediately.
Proactive Monitoring: Monitor network traffic for unexpected telnet (port 23) connections and audit logs for successful logins originating from unauthorized internal IP addresses.
Compensating Controls: If immediate replacement is impossible, disable the telnet service via the device management interface or use an access control list (ACL) to strictly limit network access to the router’s management ports.
Exploitation Status
Public Exploit Available: Unknown
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 and the lack of vendor support, the potential for exploitation is high.
Analyst Recommendation
The presence of a hardcoded backdoor in network infrastructure represents an unacceptable security risk. We strongly recommend decommissioning all affected D-Link DIR-605L units immediately to eliminate this vector of compromise.
Update D-Link DIR to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
D-Link DIR-605L Hardware Revision A1 (End-of-Life, EOL) contains a hardcoded telnet backdoor
D-Link DIR-605L Hardware Revision A1 (End-of-Life, EOL) contains a hardcoded telnet backdoor
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A stack overflow in the WebCam Server Login functionality of GeoVision GV-VMS 20.0.2 allows unauthenticated remote attackers to achieve arbitrary code...
A stack overflow in the WebCam Server Login functionality of GeoVision GV-VMS 20.0.2 allows unauthenticated remote attackers to achieve arbitrary code execution.
---METADATA---
VENDOR: GeoVision
PRODUCT: GV-VMS
AFFECTED_VERSIONS: 20.0.2
---END_METADATA---
Description Summary:
A stack overflow in the WebCam Server Login functionality of GeoVision GV-VMS 20.0.2 allows unauthenticated remote attackers to achieve arbitrary code execution.
Executive Summary:
A critical stack overflow vulnerability in the GeoVision GV-VMS WebCam Server allows unauthenticated attackers to execute arbitrary code via a crafted HTTP request.
Vulnerability Details
CVE-ID: CVE-2026-42370
Affected Software: GeoVision GV-VMS
Affected Versions: 20.0.2
Vulnerability: This is a stack overflow vulnerability found in the WebCam Server's login process. An attacker can send a malicious, unauthenticated HTTP request that triggers the overflow, leading to potential code execution.
Business Impact
A CVSS score of 9.0 confirms the critical nature of this flaw. Successful exploitation allows an attacker to gain control over the GV-VMS system, which could result in unauthorized surveillance access, system disruption, or lateral movement into the network.
Remediation Plan
Immediate Action: Upgrade to the latest version of GeoVision GV-VMS to remediate the stack overflow vulnerability.
Proactive Monitoring: Monitor for abnormal traffic patterns targeting the WebCam Server login page and check for service instability or unexpected process restarts.
Compensating Controls: Use a WAF to restrict access to the WebCam Server interface and block requests containing unusually large payloads.
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
Given the ability for unauthenticated remote code execution, this vulnerability poses a severe risk. Organizations should prioritize updating their GV-VMS deployments and ensure that management interfaces are not exposed to untrusted networks.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
A flaw has been found in itsourcecode Free Hotel Reservation System 1
A flaw has been found in itsourcecode Free Hotel Reservation System 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A stack-based buffer overflow in the GV-VMS WebCam Server gvapi endpoint allows remote attackers to gain SYSTEM-level code execution via a specially c...
A stack-based buffer overflow in the GV-VMS WebCam Server gvapi endpoint allows remote attackers to gain SYSTEM-level code execution via a specially crafted HTTP Authorization header.
---METADATA---
VENDOR: GeoVision
PRODUCT: GV-VMS
AFFECTED_VERSIONS: V20
---END_METADATA---
Description Summary:
A stack-based buffer overflow in the GV-VMS WebCam Server gvapi endpoint allows remote attackers to gain SYSTEM-level code execution via a specially crafted HTTP Authorization header.
Executive Summary:
A critical stack-based buffer overflow in GeoVision GV-VMS allows unauthenticated remote attackers to achieve full code execution as SYSTEM due to the absence of ASLR.
Vulnerability Details
CVE-ID: CVE-2026-42369
Affected Software: GeoVision GV-VMS
Affected Versions: V20
Vulnerability: The vulnerability occurs in the gvapi endpoint, which fails to perform bounds checking when processing base64-decoded strings from the HTTP Authorization header. This allows an attacker to overwrite the stack, leading to arbitrary code execution.
Business Impact
Given the CVSS score of 10, this is a maximum-severity vulnerability. Exploitation allows an attacker to gain full control over the host running the GV-VMS service with SYSTEM privileges, enabling data theft, lateral movement, and complete compromise of the surveillance network.
Remediation Plan
Immediate Action: Apply the vendor-provided security update for GV-VMS V20 immediately.
Proactive Monitoring: Monitor for anomalous spikes in traffic to the gvapi endpoint and review host logs for unauthorized binary execution or service crashes.
Compensating Controls: If a patch cannot be applied, disable the "WebCam Server" feature if it is not strictly required for business operations.
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
This vulnerability requires urgent remediation. The lack of ASLR in the affected component makes exploitation highly reliable; therefore, administrators must prioritize updating the GV-VMS software to prevent potential system-wide compromise.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
A privilege escalation vulnerability in the GeoVision LPC2011/LPC2211 web interface allows an attacker to execute privileged operations via a crafted...
A privilege escalation vulnerability in the GeoVision LPC2011/LPC2211 web interface allows an attacker to execute privileged operations via a crafted HTTP request.
---METADATA---
VENDOR: GeoVision
PRODUCT: LPC2011/LPC2211
AFFECTED_VERSIONS: 1.10
---END_METADATA---
Description Summary:
A privilege escalation vulnerability in the GeoVision LPC2011/LPC2211 web interface allows an attacker to execute privileged operations via a crafted HTTP request.
Executive Summary:
A critical privilege escalation vulnerability in GeoVision LPC2011/LPC2211 devices allows unauthorized users to perform administrative actions, potentially leading to full device compromise.
Vulnerability Details
CVE-ID: CVE-2026-42368
Affected Software: GeoVision LPC2011/LPC2211
Affected Versions: 1.10
Vulnerability: This is a privilege escalation flaw in the web interface. By sending a specially crafted HTTP request, an attacker can bypass standard access controls to execute administrative or privileged functions.
Business Impact
With a CVSS score of 9.9, this vulnerability presents a critical risk. If exploited, an attacker could change device settings, disable security features, or gain unauthorized administrative access, compromising the integrity of the surveillance feed and the device itself.
Remediation Plan
Immediate Action: Update the firmware for the GeoVision LPC2011/LPC2211 to the latest version to address the privilege escalation flaw.
Proactive Monitoring: Review access logs for unauthorized administrative requests and monitor for changes to device configurations that were not performed by authorized personnel.
Compensating Controls: Limit access to the device web management interface to internal, trusted networks and implement multi-factor authentication where supported.
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
Administrators must treat this privilege escalation vulnerability with high urgency. Patching the device firmware is the only reliable way to ensure that administrative functions remain protected from unauthorized access.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Multiple reflected cross-site scripting (xss) vulnerabilities exist in the Web Interface / ssi
Multiple reflected cross-site scripting (xss) vulnerabilities exist in the Web Interface / ssi
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A guessable session cookie vulnerability exists in the Web Interface functionality of GeoVision LPC2011/LPC2211 1
A guessable session cookie vulnerability exists in the Web Interface functionality of GeoVision LPC2011/LPC2211 1
---METADATA---
VENDOR: GeoVision
PRODUCT: LPC2011/LPC2211
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---
Description Summary:
A guessable session cookie vulnerability in the GeoVision LPC2011/LPC2211 web interface allows unauthorized access to administrative sessions.
Executive Summary:
A high-severity session management flaw in GeoVision LPC2011/LPC2211 devices allows attackers to hijack administrative sessions, potentially leading to complete device compromise.
Vulnerability Details
CVE-ID: CVE-2026-42365
Affected Software: GeoVision LPC2011/LPC2211
Affected Versions: See vendor advisory for affected versions
Vulnerability: The web interface employs guessable session cookies, which can be exploited by an attacker to bypass authentication mechanisms and impersonate an active administrative user.
Business Impact
With a CVSS score of 8.6, this vulnerability poses a high risk to organizational security. Successful session hijacking grants the attacker full control over the device configuration, allowing them to manipulate settings and compromise the device's intended function.
Remediation Plan
Immediate Action: Update the firmware for the affected GeoVision devices to the latest version to address the session management weakness.
Proactive Monitoring: Review web access logs for unusual session cookie patterns or multiple logins from the same session ID.
Compensating Controls: Restrict access to the web interface to trusted management networks and, where possible, use a WAF to monitor for suspicious cookie activity.
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
Administrators should act promptly to update their GeoVision devices. Session hijacking is a common attack vector, and remediating this flaw is essential to ensuring that administrative sessions remain secure and private.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
An OS command injection vulnerability in the DdnsSetting.cgi functionality of GeoVision LPC2011/LPC2211 allows arbitrary command execution via crafted...
An OS command injection vulnerability in the DdnsSetting.cgi functionality of GeoVision LPC2011/LPC2211 allows arbitrary command execution via crafted DDNS configuration.
---METADATA---
VENDOR: GeoVision
PRODUCT: LPC2011/LPC2211
AFFECTED_VERSIONS: 1.10
---END_METADATA---
Description Summary:
An OS command injection vulnerability in the DdnsSetting.cgi functionality of GeoVision LPC2011/LPC2211 allows arbitrary command execution via crafted DDNS configuration.
Executive Summary:
A critical OS command injection vulnerability in GeoVision LPC2011/LPC2211 devices allows unauthenticated attackers to execute arbitrary commands, potentially leading to full system compromise.
Vulnerability Details
CVE-ID: CVE-2026-42364
Affected Software: GeoVision LPC2011/LPC2211
Affected Versions: 1.10
Vulnerability: This vulnerability is an OS command injection flaw located within the DdnsSetting.cgi script. By providing a specially crafted DDNS configuration value, an attacker can bypass input validation to execute system-level commands.
Business Impact
Successful exploitation of this vulnerability grants the attacker the ability to execute arbitrary commands on the affected hardware, which can result in full system takeover, data exfiltration, or the inclusion of the device into a botnet. Given the CVSS score of 9.9, this represents an extreme risk to network integrity and operational continuity, as compromised surveillance equipment can serve as an entry point into the wider corporate network.
Remediation Plan
Immediate Action: Upgrade the GeoVision LPC2011/LPC2211 firmware to the latest version provided by the vendor to patch the injection vector.
Proactive Monitoring: Inspect system and web access logs for unusual requests directed at DdnsSetting.cgi or unexpected shell execution commands.
Compensating Controls: Implement strict network segmentation for IoT and surveillance devices and utilize a Web Application Firewall (WAF) to filter malicious input strings from configuration requests.
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
The severity of this vulnerability necessitates immediate attention. Organizations utilizing these GeoVision devices must prioritize firmware updates to close the command injection vector and prevent unauthorized remote code execution.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
GeoVision GV-IP Device Utility 9.0.5 uses insufficient encryption for administrative credentials, allowing attackers to intercept and decrypt sensitiv...
GeoVision GV-IP Device Utility 9.0.5 uses insufficient encryption for administrative credentials, allowing attackers to intercept and decrypt sensitive data over local broadcast traffic.
---METADATA---
VENDOR: GeoVision
PRODUCT: GV-IP Device Utility
AFFECTED_VERSIONS: 9.0.5
---END_METADATA---
Description Summary:
GeoVision GV-IP Device Utility 9.0.5 uses insufficient encryption for administrative credentials, allowing attackers to intercept and decrypt sensitive data over local broadcast traffic.
Executive Summary:
An insufficient encryption flaw in the GeoVision GV-IP Device Utility allows local network attackers to intercept and decrypt administrative credentials, potentially leading to full unauthorized device control.
Vulnerability Details
CVE-ID: CVE-2026-42363
Affected Software: GeoVision GV-IP Device Utility
Affected Versions: 9.0.5
Vulnerability: The utility broadcasts administrative credentials over UDP using a weak, obfuscated cryptographic scheme where the symmetric key is transmitted within the same packet. An attacker on the same local network can capture this traffic and easily derive the credentials to gain unauthorized access to the device.
Business Impact
With a CVSS score of 9.3, this vulnerability poses a significant risk to the physical and logical security of the network. An attacker capturing these credentials gains full administrative access to GeoVision devices, enabling them to modify configurations, change network settings, or disable security monitoring, which directly impacts physical site security and system availability.
Remediation Plan
Immediate Action: Update the GV-IP Device Utility to the latest version provided by GeoVision and transition to more secure management protocols if available.
Proactive Monitoring: Monitor local network broadcast traffic for suspicious UDP packets directed toward or originating from management utilities.
Compensating Controls: Implement network segmentation to isolate devices and management workstations, limiting the ability of unauthorized entities to sniff traffic on the same LAN.
Exploitation Status
Public Exploit Available: unknown
Analyst Notes: As of April 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, because the flaw is easily reproducible by an attacker on the same network, the potential for exploitation is high.
Analyst Recommendation
The reliance on security through obscurity for credential transmission is a critical design failure. Administrators should immediately restrict access to the broadcast domain where these devices reside and apply the vendor’s security patches as soon as they are made available to protect administrative credentials from interception.
Update LG Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
A security vulnerability has been detected in itsourcecode Online Enrollment System 1
A security vulnerability has been detected in itsourcecode Online Enrollment System 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A bug in Apache Airflow's XCom PATCH endpoint `PATCH /api/v2/xcomEntries/{key}` allowed an authenticated UI/API user with XCom write permission on a D...
A bug in Apache Airflow's XCom PATCH endpoint `PATCH /api/v2/xcomEntries/{key}` allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e
---METADATA---
VENDOR: Apache
PRODUCT: Airflow
AFFECTED_VERSIONS: Apache Airflow versions from (including) 3.2.0 up to (excluding) 3.2.2.
---END_METADATA---
Description Summary:
A deserialization vulnerability in the Apache Airflow XCom PATCH endpoint allows authenticated users to achieve remote code execution by bypassing key validation.
Executive Summary:
An authenticated remote code execution vulnerability in Apache Airflow 3.2.x requires immediate patching to prevent unauthorized code execution on the triggerer service.
Vulnerability Details
CVE-ID: CVE-2026-42359
Affected Software: Apache Airflow
Affected Versions: Apache Airflow versions from (including) 3.2.0 up to (excluding) 3.2.2.
Vulnerability: This is a deserialization flaw in the PATCH /api/v2/xcomEntries/{key} endpoint. An authenticated user with XCom write permissions can inject reserved key names, bypassing validation to trigger remote code execution on the Airflow triggerer.
Business Impact
The CVSS score of 8.8 reflects the high risk of this vulnerability. As an RCE, it allows a malicious user with legitimate but restricted access to escalate their privileges and execute arbitrary commands on the system. This can lead to the theft of workflow secrets, manipulation of data pipelines, and total compromise of the Airflow environment, which is often a central point of control in data infrastructure.
Remediation Plan
Immediate Action: Upgrade to Apache Airflow version 3.2.2 or later immediately to resolve the deserialization flaw.
Proactive Monitoring: Review API access logs for attempts to call the xcomEntries endpoint with reserved keys and monitor the triggerer service for anomalous child processes or unexpected execution patterns.
Compensating Controls: Restrict access to the Airflow API to only trusted identities and network segments, and implement strict RBAC to ensure only necessary users have XCom write permissions.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 3, 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 a fix-bypass for a previous issue, highlighting the need for a robust and updated Airflow installation. Organizations should prioritize updating to 3.2.2 as soon as possible to mitigate the risk of RCE and protect their data pipeline infrastructure.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Sentry's SAML SSO implementation is vulnerable to an account takeover flaw when using a malicious SAML Identity Provider.
Sentry's SAML SSO implementation is vulnerable to an account takeover flaw when using a malicious SAML Identity Provider.
---METADATA---
VENDOR: Sentry
PRODUCT: Sentry
AFFECTED_VERSIONS: 21.12.0 to 26.4.0
---END_METADATA---
Description Summary:
Sentry's SAML SSO implementation is vulnerable to an account takeover flaw when using a malicious SAML Identity Provider.
Executive Summary:
A critical vulnerability in Sentry's SAML SSO implementation allows attackers to take over user accounts by exploiting cross-organization trust.
Vulnerability Details
CVE-ID: CVE-2026-42354
Affected Software: Sentry
Affected Versions: 21.12.0 through 26.4.0
Vulnerability: The SAML SSO logic fails to properly isolate organizations, allowing a malicious SAML Identity Provider to impersonate users from another organization on the same instance.
Business Impact
With a CVSS score of 9.1, this allows attackers to gain unauthorized access to sensitive Sentry data, including API keys and performance metrics. This is a severe threat to the confidentiality of organizational data stored within Sentry.
Remediation Plan
Immediate Action: Update Sentry to version 26.4.1 or later immediately.
Proactive Monitoring: Audit SAML configuration and review logs for suspicious SSO login events, particularly those involving multiple organizations.
Compensating Controls: If immediate patching is not possible, temporarily disable SAML SSO and enforce strong multi-factor authentication for all users.
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
Account takeover vulnerabilities in SSO providers are high-impact events. Organizations should prioritize this update to ensure the integrity of their identity and access management.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
i18next-http-middleware is a middleware to be used with Node
i18next-http-middleware is a middleware to be used with Node
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
pygeoapi is a Python server implementation of the OGC API suite of standards
pygeoapi is a Python server implementation of the OGC API suite of standards
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
pygeoapi is a Python server implementation of the OGC API suite of standards
pygeoapi is a Python server implementation of the OGC API suite of standards
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A weakness has been identified in itsourcecode Online Enrollment System 1
A weakness has been identified in itsourcecode Online Enrollment System 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
FastGPT is an AI Agent building platform
FastGPT is an AI Agent building platform
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
FOSSBilling contains an unauthenticated payment bypass vulnerability in the IPN callback endpoint, allowing attackers to mark invoices as paid without...
FOSSBilling contains an unauthenticated payment bypass vulnerability in the IPN callback endpoint, allowing attackers to mark invoices as paid without actual payment.
---METADATA---
VENDOR: FOSSBilling
PRODUCT: FOSSBilling
AFFECTED_VERSIONS: >= 0.6.0, < 0.8.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
FOSSBilling contains an unauthenticated payment bypass vulnerability in the IPN callback endpoint, allowing attackers to mark invoices as paid without actual payment.
Executive Summary:
An unauthenticated payment bypass vulnerability in FOSSBilling allows attackers to manipulate invoice statuses and credit accounts without completing financial transactions.
Vulnerability Details
CVE-ID: CVE-2026-42341
Affected Software: FOSSBilling FOSSBilling
Affected Versions: >= 0.6.0, < 0.8.0
Vulnerability: This is a critical authentication bypass and validation error in the IPN callback endpoint. The vulnerability allows an unauthenticated remote attacker to send a crafted HTTP request to mark invoices as paid when the Custom payment adapter is enabled.
Business Impact
The CVSS score of 9.2 highlights the severe financial and operational impact of this vulnerability. Attackers can gain services or products without payment, leading to direct financial loss and potential manipulation of client account records, which could undermine the integrity of the billing and customer management system.
Remediation Plan
Immediate Action: Upgrade FOSSBilling to version 0.8.0 or later to implement the necessary authentication checks for payment callbacks.
Proactive Monitoring: Monitor invoice payment logs for anomalies or batches of payments marked as "paid" that lack corresponding transaction records from legitimate payment gateways.
Compensating Controls: Disable the "Custom" payment gateway if it is not strictly required, or restrict access to the /ipn.php endpoint via web server rules to trusted IP addresses only.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of Jul 6, 2026, there is no public information indicating active exploitation of this vulnerability. However, the simplicity of the attack vector makes it an attractive target for financial fraud.
Analyst Recommendation
This vulnerability represents a significant financial risk to any organization using FOSSBilling for revenue collection. Immediate application of the 0.8.0 update is required to prevent unauthorized service provisioning and financial fraud.
Update FOSSBilling FOSSBilling to the latest version. Check the vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
FOSSBilling is a free, open-source billing and client management system
FOSSBilling is a free, open-source billing and client management system
---METADATA---
VENDOR: FOSSBilling
PRODUCT: FOSSBilling
AFFECTED_VERSIONS: < 0.8.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
FOSSBilling is susceptible to missing authentication and incorrect authorization vulnerabilities, potentially allowing unauthenticated attackers to manipulate critical system functions.
Executive Summary:
A critical authentication and authorization flaw in FOSSBilling versions prior to 0.8.0 exposes the billing and client management system to unauthorized administrative actions by unauthenticated users.
Vulnerability Details
CVE-ID: CVE-2026-42331
Affected Software: FOSSBilling FOSSBilling
Affected Versions: < 0.8.0
Vulnerability: This vulnerability involves missing authentication for critical functions (CWE-306) and incorrect authorization (CWE-863). These flaws allow unauthenticated remote attackers to perform sensitive operations within the billing system that should be restricted to authorized users.
Business Impact
The ability for unauthenticated users to bypass security controls poses a significant risk to the integrity of client data and billing operations. With a CVSS score of 7.7, this high-severity vulnerability could lead to unauthorized administrative modifications, potentially resulting in financial discrepancies, data exfiltration, or complete loss of control over the application environment.
Remediation Plan
Immediate Action: Upgrade FOSSBilling to version 0.8.0 or later immediately to address these security defects.
Proactive Monitoring: Review application access logs for unusual administrative activity or unauthorized requests originating from unknown IP addresses.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block suspicious requests targeting administrative endpoints until the patch is applied.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of July 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
The severity of this vulnerability necessitates immediate attention to prevent unauthorized administrative access. Administrators should prioritize upgrading to version 0.8.0 to ensure the security and integrity of the FOSSBilling platform.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability was determined in Tiandy Integrated Management Platform 7
A vulnerability was determined in Tiandy Integrated Management Platform 7
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
pyLoad is a free and open-source download manager written in Python
pyLoad is a free and open-source download manager written in Python
---METADATA---
VENDOR: pyload
PRODUCT: pyload
AFFECTED_VERSIONS: < 0.5.0b3.dev100
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
pyLoad is vulnerable to path traversal, allowing authenticated users to read or write files outside of the intended directories.
Executive Summary:
An authenticated path traversal vulnerability in pyLoad versions prior to 0.5.0b3.dev100 permits unauthorized file system access and manipulation.
Vulnerability Details
CVE-ID: CVE-2026-42315
Affected Software: pyload pyload
Affected Versions: < 0.5.0b3.dev100
Vulnerability: This vulnerability involves Improper Limitation of a Pathname (CWE-22) and Absolute Path Traversal (CWE-36). Exploitation requires low-privileged authentication (PR:L) and allows an attacker to impact file integrity and system availability (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H).
Business Impact
With a CVSS score of 8.1, this vulnerability presents a High risk to system integrity. An authenticated attacker can overwrite critical application files or system components, potentially leading to a denial of service or further escalation of privileges, which could disrupt business operations.
Remediation Plan
Immediate Action: Upgrade to pyLoad version 0.5.0b3.dev100 or later to resolve the path traversal flaw.
Proactive Monitoring: Monitor application logs for unusual file write or access attempts that deviate from standard user behavior.
Compensating Controls: Restrict access to the pyLoad web interface via VPN or IP-based access control lists (ACLs) to ensure only authorized personnel can interact with the management console.
Exploitation Status
Public Exploit Available: No (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 requirement for low-level authentication slightly limits the attack surface but does not negate the high impact of the flaw.
Analyst Recommendation
Given the capability for file manipulation, this vulnerability should be patched promptly. Organizations should enforce strict access controls on the management interface while performing the necessary version upgrades to mitigate the risk of unauthorized system modification.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
pyLoad is a free and open-source download manager written in Python
pyLoad is a free and open-source download manager written in Python
---METADATA---
VENDOR: pyLoad
PRODUCT: pyLoad
AFFECTED_VERSIONS: < 0.5.0b3.dev100
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
pyLoad is vulnerable to Server-Side Request Forgery (SSRF) and authorization bypass due to unintended intermediary proxy behavior, allowing authenticated attackers to perform unauthorized actions.
Executive Summary:
A vulnerability in pyLoad allows authenticated attackers to perform unauthorized actions and Server-Side Request Forgery (SSRF), posing a significant risk to internal network security.
Vulnerability Details
CVE-ID: CVE-2026-42313
Affected Software: pyLoad pyLoad
Affected Versions: < 0.5.0b3.dev100
Vulnerability: This issue encompasses multiple weaknesses including SSRF, incorrect authorization, and a "confused deputy" scenario, requiring an attacker to have authenticated (low-privileged) access to the application.
Business Impact
Successful exploitation allows an attacker to bypass intended access controls and potentially interact with internal services that are not exposed to the internet. With a CVSS score of 8.3, this represents a high-severity risk that could lead to data exfiltration or unauthorized internal network reconnaissance, impacting the confidentiality and integrity of the hosting environment.
Remediation Plan
Immediate Action: Update pyLoad to version 0.5.0b3.dev100 or later to resolve the underlying authorization and SSRF flaws.
Proactive Monitoring: Monitor network egress traffic for unusual requests originating from the pyLoad server and review application access logs for suspicious administrative activity.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SSRF patterns and unauthorized API calls directed at the pyLoad backend.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of May 13, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is inherently exploitable by any user with low-level authenticated access.
Analyst Recommendation
Given the high CVSS score and the existence of a proof-of-concept, organizations should prioritize patching pyLoad instances immediately. Ensure that the application is isolated within the network to minimize the potential impact of any successful SSRF attempts.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability was found in vanna-ai vanna up to 2
A vulnerability was found in vanna-ai vanna up to 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Dulwich is a pure-Python implementation of the Git file formats and protocols
Dulwich is a pure-Python implementation of the Git file formats and protocols
---METADATA---
VENDOR: Jelmer Vernooij (Dulwich)
PRODUCT: Dulwich
AFFECTED_VERSIONS: 0.20.15-1 (bullseye), 0.21.2-1 (bookworm), 0.22.7-1 (trixie), 1.2.1-1 (forky)
---END_METADATA---
Description Summary:
Dulwich contains an arbitrary file write vulnerability via NTFS-hostile tree entries, enabling remote code execution when checking out malicious Git repositories.
Executive Summary:
A high-severity arbitrary file write vulnerability in the Dulwich library allows for remote code execution when processing untrusted Git repositories on Windows.
Vulnerability Details
CVE-ID: CVE-2026-42305
Affected Software: Dulwich (Python Git implementation)
Affected Versions: 0.20.15-1 (bullseye), 0.21.2-1 (bookworm), 0.22.7-1 (trixie), 1.2.1-1 (forky)
Vulnerability: The vulnerability is an arbitrary file write caused by improper handling of NTFS-hostile tree entries. An unauthenticated attacker can achieve remote code execution when a user performs a clone, fetch, or checkout of a malicious Git repository.
Business Impact
With a CVSS score of 8.8, this vulnerability represents a significant risk to developers and build systems. Exploitation can lead to full system compromise, as arbitrary code execution allows an attacker to install backdoors, steal source code, or exfiltrate sensitive environment credentials.
Remediation Plan
Immediate Action: Update the Dulwich library to version 1.2.5-1 or later across all affected development environments and CI/CD pipelines.
Proactive Monitoring: Audit Git repository cloning activities and monitor for unusual file system modifications in directory paths associated with version control operations.
Compensating Controls: Avoid cloning or checking out repositories from untrusted or unverified sources, especially when using Windows-based development environments.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of June 11, 2026, a public exploit is available for this vulnerability. Organizations should consider this an active and high-priority threat.
Analyst Recommendation
Given the existence of a public exploit, the risk of exploitation is immediate. Development teams must prioritize updating the Dulwich package to version 1.2.5-1. Any system currently utilizing older versions to process external Git repositories should be considered at risk of remote code execution.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
An unauthenticated RCE vulnerability in FastGPT's agent-sandbox component stems from insecure default configurations in the startup script.
An unauthenticated RCE vulnerability in FastGPT's agent-sandbox component stems from insecure default configurations in the startup script.
---METADATA---
VENDOR: FastGPT
PRODUCT: FastGPT
AFFECTED_VERSIONS: 4.14.10 to 4.14.12
---END_METADATA---
Description Summary:
An unauthenticated RCE vulnerability in FastGPT's agent-sandbox component stems from insecure default configurations in the startup script.
Executive Summary:
An unauthenticated remote code execution vulnerability in the FastGPT agent-sandbox allows attackers to gain full control over the host environment.
Vulnerability Details
CVE-ID: CVE-2026-42302
Affected Software: FastGPT
Affected Versions: 4.14.10 through 4.14.12
Vulnerability: The entrypoint.sh script incorrectly initializes code-server with --auth none and binds it to all network interfaces, allowing unauthenticated remote access to the sandbox environment.
Business Impact
With a CVSS score of 9.8, this vulnerability allows for complete system compromise, enabling attackers to execute arbitrary code, steal sensitive data, or pivot into internal infrastructure. This poses a catastrophic risk to confidentiality, integrity, and availability of the platform.
Remediation Plan
Immediate Action: Upgrade FastGPT to version 4.14.13 or later to ensure proper authentication is enforced on the agent-sandbox.
Proactive Monitoring: Review system and network access logs for unauthorized connections to port 8080 or suspicious process execution originating from the sandbox.
Compensating Controls: Immediately restrict network access to the sandbox port (8080) via firewall rules to allow only authorized administrative IPs.
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
The ease of exploitation for this RCE makes it a priority for immediate remediation. Administrators should treat this as a high-urgency update to prevent unauthorized code execution and complete system takeover.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
pyp2spec generates working Fedora RPM spec file for Python projects
pyp2spec generates working Fedora RPM spec file for Python projects
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A "Pwn Request" vulnerability in Postiz allows unauthenticated users to execute arbitrary code via malicious pull requests, leading to credential exfi...
A "Pwn Request" vulnerability in Postiz allows unauthenticated users to execute arbitrary code via malicious pull requests, leading to credential exfiltration.
---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.
Update GitHub Multiple Products to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes
---METADATA---
VENDOR: Argo
PRODUCT: Workflows
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
Argo Workflows contains a high-severity vulnerability that could impact the security of container-native job orchestration on Kubernetes.
Executive Summary:
A security vulnerability in Argo Workflows may allow attackers to compromise the integrity of containerized job orchestration on Kubernetes clusters.
Vulnerability Details
CVE-ID: CVE-2026-42296
Affected Software: Argo Workflows
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability affects Argo Workflows, an engine used for orchestrating parallel jobs on Kubernetes. The exact technical nature of the exploit is currently being detailed by the vendor.
Business Impact
With a CVSS score of 8.1, this vulnerability presents a high risk to Kubernetes-based operations. Compromise of the workflow engine could allow an attacker to execute arbitrary jobs, steal secrets from the cluster, or disrupt critical business processes that rely on parallel job execution.
Remediation Plan
Immediate Action: Apply vendor security updates immediately to the Argo Workflows controller and associated components.
Proactive Monitoring: Review Kubernetes audit logs for suspicious job submissions, unexpected container executions, or unauthorized access attempts to the Argo API.
Compensating Controls: Implement Kubernetes Network Policies to restrict the communication capabilities of the Argo Workflows pods and minimize the blast radius of a potential compromise.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of May 10, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Given the critical role of Argo Workflows in orchestrating containerized jobs, this vulnerability must be treated with high priority. Administrators should monitor vendor channels for patches and prepare for an urgent deployment to secure their Kubernetes environments.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A flaw has been found in vanna-ai vanna up to 2
A flaw has been found in vanna-ai vanna up to 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
ChurchCRM is an open-source church management system
ChurchCRM is an open-source church management system
---METADATA---
VENDOR: ChurchCRM
PRODUCT: CRM
AFFECTED_VERSIONS: < 7.3.2
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
ChurchCRM before 7.3.2 is susceptible to multiple vulnerabilities including improper privilege management, missing authentication for critical functions, and CSRF, potentially leading to system compromise.
Executive Summary:
Multiple security flaws in ChurchCRM, including missing authentication and privilege management issues, allow remote attackers to compromise the application integrity and confidentiality.
Vulnerability Details
CVE-ID: CVE-2026-42289
Affected Software: ChurchCRM CRM
Affected Versions: < 7.3.2
Vulnerability: The application suffers from a combination of missing authentication for critical functions (CWE-306), improper privilege management (CWE-269), and Cross-Site Request Forgery (CWE-352). These flaws allow unauthenticated or low-privileged attackers to perform sensitive actions.
Business Impact
The combined impact of these vulnerabilities is severe, with a CVSS score of 8.8. An attacker could gain unauthorized administrative access, modify sensitive church management data, or perform unauthorized actions, leading to significant reputational damage and loss of trust.
Remediation Plan
Immediate Action: Upgrade ChurchCRM to version 7.3.2 or later immediately to address these security gaps.
Proactive Monitoring: Review application logs for unauthorized administrative actions or suspicious requests that could indicate exploitation attempts.
Compensating Controls: Deploy a Web Application Firewall (WAF) to mitigate potential CSRF attacks and block suspicious traffic patterns targeting administrative endpoints.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of May 14, 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 presence of multiple chained vulnerabilities makes this system highly attractive for automated exploitation.
Analyst Recommendation
ChurchCRM users should treat this advisory with high urgency and perform the recommended upgrade to version 7.3.2. Because the vulnerability includes missing authentication for critical functions, the application is at high risk of unauthorized manipulation by remote parties.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
---METADATA---
VENDOR: CloudSecure
PRODUCT: CloudSecure WP Security
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A broken authentication vulnerability in the CloudSecure WP Security plugin allows unauthenticated attackers to bypass security controls.
Executive Summary:
An unauthenticated broken authentication vulnerability in the CloudSecure WP Security plugin poses a critical risk of unauthorized administrative access.
Vulnerability Details
CVE-ID: CVE-2026-42411
Affected Software: CloudSecure WP Security
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The plugin suffers from a broken authentication mechanism that can be exploited by unauthenticated users. This flaw allows attackers to bypass standard login requirements, potentially gaining administrative or elevated privileges within the WordPress environment.
Business Impact
With a CVSS score of 8.1, this vulnerability presents a high risk of total site compromise. An attacker gaining administrative access can exfiltrate sensitive data, inject malicious code, or take full control of the website, leading to significant financial and reputational loss.
Remediation Plan
Immediate Action: Apply the latest security patch or update provided by the vendor for the CloudSecure WP Security plugin.
Proactive Monitoring: Review user account creation logs and login attempts for suspicious activity, particularly from unknown or unauthorized IP addresses.
Compensating Controls: Implement multi-factor authentication (MFA) and restrict administrative access to known IP addresses via server configuration.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 16, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Broken authentication is a severe security failure. All administrators using the CloudSecure WP Security plugin must ensure the software is updated to a patched version immediately to prevent unauthorized access and maintain the integrity of their WordPress installation.