---METADATA---
VENDOR: IBM
PRODUCT: Langflow OSS
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A high-severity security vulnerability has been identified in IBM Langflow OSS 1 that may pose a risk to system integrity.

Executive Summary:
IBM Langflow OSS 1 contains a high-severity security flaw that necessitates urgent remediation to protect against potential exploitation.

Vulnerability Details

CVE-ID: CVE-2026-10129

Affected Software: IBM Langflow OSS

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects IBM Langflow OSS 1 and potentially allows for unauthorized operations within the platform. Users should assume that the vulnerability could be leveraged to gain unauthorized access or execute arbitrary commands depending on the deployment configuration.

Business Impact

Exploitation of this vulnerability could result in the compromise of data processed by the Langflow platform, leading to severe operational and reputational damage. The CVSS score of 8.5 highlights the high severity, indicating that an attacker could potentially achieve significant control over the affected system.

Remediation Plan

Immediate Action: Identify all instances of Langflow OSS 1 and apply the latest security updates provided by IBM.

Proactive Monitoring: Review system and application logs for anomalous traffic, unexpected authentication attempts, or unauthorized access to the Langflow interface.

Compensating Controls: Isolate the Langflow instance behind a network-level firewall or VPN to restrict access to authorized personnel only, significantly reducing the attack surface.

Exploitation Status

Public Exploit Available: false

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

Analyst Recommendation

Due to the critical role of orchestration and automation tools like Langflow, this vulnerability should be treated with high priority. Security teams must verify their current versioning against vendor recommendations and apply necessary patches to prevent unauthorized system manipulation.

---METADATA---
VENDOR: Edimax
PRODUCT: BR-6478AC
AFFECTED_VERSIONS: Edimax BR-6478AC 1.23
---END_METADATA---

Description Summary:
A buffer overflow vulnerability exists in the Edimax BR-6478AC router, allowing remote code execution via a crafted POST request.

Executive Summary:
A critical buffer overflow vulnerability in the Edimax BR-6478AC router poses a significant risk of remote code execution and system compromise.

Vulnerability Details

CVE-ID: CVE-2026-10126

Affected Software: Edimax BR-6478AC

Affected Versions: Edimax BR-6478AC 1.23

Vulnerability: This is a buffer overflow vulnerability located in the formQoS function of the /goform/formQoS component. The flaw is exploitable via the selSSID argument through a POST request, likely requiring no authentication to trigger.

Business Impact

Successful exploitation of this vulnerability allows an attacker to execute arbitrary code on the affected router. Given the CVSS score of 8.8 (High), this represents a severe risk that could lead to full device takeover, unauthorized network access, and potential interception of sensitive traffic, resulting in significant reputational and operational damage.

Remediation Plan

Immediate Action: Check the official Edimax support portal for firmware updates addressing this vulnerability. If no patch is available, isolate the device from public-facing networks.

Proactive Monitoring: Review device access logs for unusual POST requests directed at /goform/formQoS. Monitor network traffic for anomalous patterns indicative of buffer overflow attempts.

Compensating Controls: Implement a Web Application Firewall (WAF) or ingress filtering to block malicious POST requests targeting the identified vulnerable URL parameters.

Exploitation Status

Public Exploit Available: True

Analyst Notes: As of May 31, 2026, there is public proof-of-concept information available for this vulnerability. Given the availability of exploit code, the potential for active exploitation is high.

Analyst Recommendation

The high severity of this vulnerability, combined with the presence of public exploit code, necessitates immediate action. Organizations should prioritize patching or replacing affected devices to prevent unauthorized access. If a patch is unavailable, the device must be removed from the perimeter or strictly firewalled to mitigate exposure.

---METADATA---
VENDOR: Edimax
PRODUCT: BR-6478AC
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A high-severity vulnerability has been identified in the Edimax BR-6478AC router, potentially allowing unauthorized system access.

Executive Summary:
A high-severity vulnerability in the Edimax BR-6478AC router requires immediate firmware remediation to prevent potential unauthorized access.

Vulnerability Details

CVE-ID: CVE-2026-10125

Affected Software: Edimax BR-6478AC

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability was identified in the Edimax BR-6478AC router. It may allow an attacker to bypass security controls or gain unauthorized access to the device, which could lead to a compromise of the connected network.

Business Impact

With a CVSS score of 8.8, this vulnerability poses a significant risk. Compromise of this router could lead to unauthorized network access, data interception, and the potential for a complete loss of control over the local network gateway.

Remediation Plan

Immediate Action: Apply the latest firmware update provided by Edimax.

Proactive Monitoring: Monitor for unusual traffic and unauthorized management access attempts on the router.

Compensating Controls: Restrict administrative access to the router and ensure it is not exposed directly to the internet.

Exploitation Status

Public Exploit Available: False

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

Analyst Recommendation

Organizations using the Edimax BR-6478AC must treat this as a high-priority update. Ensure that all security patches are applied promptly to protect the integrity of the network and prevent potential exploitation of the router.

---METADATA---
VENDOR: Shibby
PRODUCT: Tomato
AFFECTED_VERSIONS: Up to 1
---END_METADATA---

Description Summary:
A high-severity vulnerability has been determined in Shibby Tomato firmware, potentially allowing unauthorized system access.

Executive Summary:
A high-severity vulnerability in Shibby Tomato firmware up to version 1 requires immediate attention to prevent unauthorized system access.

Vulnerability Details

CVE-ID: CVE-2026-10124

Affected Software: Shibby Tomato

Affected Versions: Up to 1

Vulnerability: This vulnerability affects Shibby Tomato firmware. It potentially allows an attacker to gain unauthorized access or control over the affected device, posing a significant risk to users relying on this firmware for their network routing.

Business Impact

With a CVSS score of 8.8, this vulnerability represents a high risk to the security of the network. Successful exploitation could allow an attacker to intercept traffic, modify device settings, or use the router as a gateway for further attacks on the internal network.

Remediation Plan

Immediate Action: Update to the latest available version of the firmware if a patch is available, or consider switching to a supported and secure alternative.

Proactive Monitoring: Monitor the router for unauthorized configuration changes or anomalous traffic patterns.

Compensating Controls: Place the device behind a more robust firewall or restrict management access to a secure, local-only connection.

Exploitation Status

Public Exploit Available: False

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

Analyst Recommendation

Users of Shibby Tomato firmware should verify their current version and update to the latest release if possible. Given the high severity, maintaining updated firmware is critical to ensuring the security of the routing environment.

---METADATA---
VENDOR: TRENDnet
PRODUCT: TEW-432BRP
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A vulnerability in the TRENDnet TEW-432BRP router could allow unauthorized access to the device.

Executive Summary:
A high-severity vulnerability in the TRENDnet TEW-432BRP router necessitates immediate firmware updates to prevent potential network compromise.

Vulnerability Details

CVE-ID: CVE-2026-10123

Affected Software: TRENDnet TEW-432BRP

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The TRENDnet TEW-432BRP router contains a vulnerability that could be exploited to compromise the device. This flaw may allow an attacker to bypass authentication or gain unauthorized control over router functions.

Business Impact

With a CVSS score of 8.8, this vulnerability is a high-severity risk. Compromising the router provides an attacker with a strategic position to perform man-in-the-middle attacks or gain unauthorized access to the organization's internal network infrastructure.

Remediation Plan

Immediate Action: Update the router to the latest firmware version released by TRENDnet.

Proactive Monitoring: Monitor for unusual administrative activity and ensure all management ports are secured.

Compensating Controls: Disable remote management features if they are not necessary for day-to-day operations.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of May 31, 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 quickly to patch the TRENDnet TEW-432BRP router. Maintaining current firmware is a fundamental security practice, particularly for edge devices that serve as the primary defense for the internal network.

---METADATA---
VENDOR: TRENDnet
PRODUCT: TEW-432BRP
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A vulnerability in the TRENDnet TEW-432BRP router could allow unauthorized access to the device.

Executive Summary:
An identified high-severity vulnerability in the TRENDnet TEW-432BRP router requires immediate remediation to safeguard network integrity.

Vulnerability Details

CVE-ID: CVE-2026-10122

Affected Software: TRENDnet TEW-432BRP

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the TRENDnet TEW-432BRP router and may allow an attacker to gain unauthorized access or influence the device's operation. Addressing this flaw is critical to maintaining the security of the network gateway.

Business Impact

With a CVSS score of 8.8, this vulnerability carries a high risk to the business. Unauthorized access to the router allows an attacker to pivot into the internal network, potentially resulting in data exfiltration or the deployment of malicious software across the organization.

Remediation Plan

Immediate Action: Apply the latest firmware update from the manufacturer to address the vulnerability.

Proactive Monitoring: Regularly audit router configuration and monitor for unexpected traffic spikes or unauthorized management access.

Compensating Controls: Implement strict access control lists (ACLs) to limit management interface access to trusted internal IP addresses.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of May 31, 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 utilizing the TRENDnet TEW-432BRP must prioritize patching this device. Given the potential for high-impact exploitation, failure to update the firmware could leave the network exposed to serious security threats.

---METADATA---
VENDOR: TRENDnet
PRODUCT: TEW-432BRP
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security flaw has been identified in the TRENDnet TEW-432BRP router, potentially allowing unauthorized actions on the device.

Executive Summary:
A high-severity flaw in the TRENDnet TEW-432BRP router requires immediate firmware remediation to prevent unauthorized system control.

Vulnerability Details

CVE-ID: CVE-2026-10121

Affected Software: TRENDnet TEW-432BRP

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: A flaw found in the TRENDnet TEW-432BRP router could enable an attacker to perform unauthorized operations. While technical details are pending, such flaws typically involve insufficient validation of administrative commands or memory safety issues.

Business Impact

With a CVSS score of 8.8, this vulnerability represents a high risk to business operations. Compromise of this router could result in the total exposure of internal network communications and facilitate further attacks against internal hosts.

Remediation Plan

Immediate Action: Update the router firmware to the most recent version provided by TRENDnet.

Proactive Monitoring: Review firewall logs and device management logs for any suspicious activity or unauthorized configuration changes.

Compensating Controls: Use network segmentation to ensure that the router is not directly exposed to the public internet where possible.

Exploitation Status

Public Exploit Available: False

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

Analyst Recommendation

Security teams must treat this high-severity vulnerability with urgency. Ensure that the device is updated and that all default credentials have been changed to reduce the attack surface while awaiting further vendor guidance.

---METADATA---
VENDOR: TRENDnet
PRODUCT: TEW-432BRP
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability has been identified in the TRENDnet TEW-432BRP router that may allow unauthorized system access.

Executive Summary:
An identified high-severity vulnerability in the TRENDnet TEW-432BRP router necessitates immediate attention to prevent potential unauthorized access to network infrastructure.

Vulnerability Details

CVE-ID: CVE-2026-10120

Affected Software: TRENDnet TEW-432BRP

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This is a security vulnerability detected in the TRENDnet TEW-432BRP router. The flaw potentially allows an attacker to bypass security mechanisms or execute unauthorized actions on the device, threatening the integrity of the network gateway.

Business Impact

With a CVSS score of 8.8, this vulnerability poses a high risk to organizational network security. Successful exploitation could grant an attacker the ability to monitor, modify, or disrupt traffic flowing through the device, leading to a loss of data confidentiality and potential service outages.

Remediation Plan

Immediate Action: Check the TRENDnet support portal for the latest firmware and apply the update immediately.

Proactive Monitoring: Monitor for unauthorized login attempts or configuration changes on the router.

Compensating Controls: Disable unnecessary services on the router and ensure remote management is disabled if not strictly required for business operations.

Exploitation Status

Public Exploit Available: False

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

Promptly apply all available vendor patches to the affected TRENDnet routers. Given the high CVSS score, the risk of exploitation is significant, and proactive maintenance is essential to protect the network perimeter from unauthorized access.

---METADATA---
VENDOR: TRENDnet
PRODUCT: TEW-432BRP
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A high-severity security vulnerability has been identified in the TRENDnet TEW-432BRP router, potentially exposing it to unauthorized access.

Executive Summary:
A high-severity vulnerability in the TRENDnet TEW-432BRP router could allow unauthorized access, posing a significant risk to network security.

Vulnerability Details

CVE-ID: CVE-2026-10119

Affected Software: TRENDnet TEW-432BRP

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability involves a security flaw in the TRENDnet TEW-432BRP router. While specific technical details are limited, such vulnerabilities in networking hardware often involve improper authentication or input validation, potentially allowing an attacker to gain unauthorized control of the device.

Business Impact

With a CVSS score of 8.8, this vulnerability is considered high risk. Compromise of a network router can lead to total interception of network traffic, redirection of DNS queries, and unauthorized access to internal network resources, significantly compromising the security of the organization's perimeter.

Remediation Plan

Immediate Action: Apply the latest firmware update provided by TRENDnet immediately.

Proactive Monitoring: Monitor network traffic for anomalous patterns or administrative access attempts on the router that do not originate from authorized internal management consoles.

Compensating Controls: Restrict management access to the router to a dedicated, isolated management network or a specific, trusted IP address range.

Exploitation Status

Public Exploit Available: False

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

Network devices are critical infrastructure. Administrators must prioritize the application of firmware updates for the affected TRENDnet hardware to mitigate the risk of network-wide compromise. If a patch is unavailable, the device should be isolated from the public internet until a resolution is provided.

---METADATA---
VENDOR: IBM
PRODUCT: Db2
AFFECTED_VERSIONS: 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4
---END_METADATA---

Description Summary:
IBM Db2 is vulnerable to remote code execution due to improper handling of the pre-authentication DRDA handshake process.

Executive Summary:
IBM Db2 contains a critical pre-authentication remote code execution vulnerability that may allow unauthenticated attackers to compromise the database server.

Vulnerability Details

CVE-ID: CVE-2026-10109

Affected Software: IBM Db2

Affected Versions: 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4

Vulnerability: The vulnerability exists within the DRDA (Distributed Relational Database Architecture) handshake process. Because the flaw is triggered during the pre-authentication phase, it allows for remote code execution without requiring valid credentials.

Business Impact

A CVSS score of 9.8 reflects the high probability of total database compromise. Successful exploitation results in unauthorized remote code execution, which could lead to complete loss of database confidentiality, integrity, and availability, impacting all critical business applications relying on the Db2 platform.

Remediation Plan

Immediate Action: Update IBM Db2 to the latest patched version as specified in the vendor's security bulletin.

Proactive Monitoring: Monitor network traffic for anomalous DRDA handshake patterns and review database logs for signs of unauthorized access or unexpected process execution.

Compensating Controls: Utilize network segmentation and firewalls to restrict access to the Db2 database port (50000/tcp) to known, trusted application servers only.

Exploitation Status

Public Exploit Available: No

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

Analyst Recommendation

This vulnerability is highly critical due to its pre-authentication nature, which significantly lowers the barrier for attackers. Organizations must prioritize applying the relevant patches for IBM Db2 immediately to prevent remote exploitation and secure their database environments against potential unauthorized access.

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

Description Summary:
The AVX2-optimized ML-KEM implementation in wolfSSL contains a comparison flaw during the decapsulation process that could lead to security compromises.

Executive Summary:
A cryptographic implementation flaw in wolfSSL’s ML-KEM decapsulation process creates a high-severity risk to the integrity of protected communications.

Vulnerability Details

CVE-ID: CVE-2026-10097

Affected Software: wolfSSL wolfSSL

Affected Versions: See vendor advisory for affected versions

Vulnerability: The vulnerability exists in the mlkem_cmp_avx2 function, where the implementation fails to compare the full length of the ciphertext during the Fujisaki-Okamoto re-encryption check. This incomplete comparison during ML-KEM-1024 decapsulation could potentially be exploited to facilitate cryptographic attacks.

Business Impact

With a CVSS score of 8.3, this flaw undermines the security guarantees of the ML-KEM implementation, potentially allowing an attacker to weaken encrypted sessions. This poses a significant threat to data confidentiality, as successful exploitation could lead to the exposure of sensitive information protected by the affected cryptographic protocols.

Remediation Plan

Immediate Action: Update the wolfSSL library to the latest version that contains the corrected ML-KEM implementation.

Proactive Monitoring: Monitor systems utilizing wolfSSL for unusual error rates or cryptographic failures that might indicate an attempt to exploit the decapsulation process.

Compensating Controls: Ensure that all cryptographic implementations are kept up to date and, where possible, utilize FIPS-validated modules that have been verified against such implementation flaws.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, given the complexity of the flaw, the potential for exploitation is high.

Analyst Recommendation

Security teams must prioritize patching all applications that incorporate the wolfSSL library. Given the technical nature of this cryptographic failure, immediate remediation is required to ensure the continued integrity and confidentiality of encrypted traffic within the enterprise network.

---METADATA---
VENDOR: Red Hat
PRODUCT: Advanced Cluster Management for Kubernetes
AFFECTED_VERSIONS: Red Hat Advanced Cluster Management for Kubernetes 2
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A privilege escalation vulnerability in the Red Hat Advanced Cluster Management Application Subscription controller allows authenticated users to gain cluster-admin privileges.

Executive Summary:
A critical privilege escalation vulnerability in Red Hat Advanced Cluster Management for Kubernetes allows authenticated users with limited privileges to achieve full cluster-admin access.

Vulnerability Details

CVE-ID: CVE-2026-10090

Affected Software: Red Hat Advanced Cluster Management for Kubernetes 2

Affected Versions: Red Hat Advanced Cluster Management for Kubernetes 2

Vulnerability: This flaw stems from improper capability checks within the Application Subscription controller, which fails to validate if an authenticated user possesses the subscription-admin role before processing Helm charts. This allows a user with namespace-scoped edit privileges to deploy malicious resources, including ClusterRoleBindings, which grant unauthorized administrative control over the cluster.

Business Impact

The vulnerability carries a CVSS score of 9.9, reflecting its ability to facilitate total compromise of the Kubernetes environment. Successful exploitation grants an attacker full administrative control, leading to unauthorized data access, potential lateral movement across the infrastructure, and total loss of system integrity.

Remediation Plan

Immediate Action: Update Red Hat Advanced Cluster Management for Kubernetes 2 to the latest patched version provided by Red Hat.

Proactive Monitoring: Review audit logs for suspicious activity, specifically monitoring for the creation of unexpected ClusterRoleBindings or modifications to cluster-scoped resources by non-privileged accounts.

Compensating Controls: Strictly enforce Role-Based Access Control (RBAC) policies and limit the ability of users to create or modify Channel and Subscription resources within the hub namespace until the patch is applied.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 5, 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 the elevated authority the controller uses to process user-supplied input.

Analyst Recommendation

Given the critical severity and the potential for full cluster takeover, immediate action is required. Administrators must prioritize applying the vendor-supplied update to remediate the underlying logic error in the Subscription controller.

Executive Summary:
A critical vulnerability has been identified in the Altium Forum component of multiple A stored products. This flaw allows an authenticated attacker to inject malicious code into a forum post, which can lead to the compromise of other users' accounts and the theft of sensitive workspace data, including design files, when they view the malicious post.

Vulnerability Details

CVE-ID: CVE-2026-1009

Affected Software: A stored Multiple Products

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: A stored cross-site scripting (XSS) vulnerability exists because the server fails to properly sanitize user-supplied content within forum posts. An authenticated attacker can create a forum post containing a malicious JavaScript payload. When another user views this post, the payload is executed by the victim's web browser in the context of their authenticated Altium 365 session, granting the attacker the same permissions as the victim.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9. Successful exploitation could lead to significant business consequences, including the compromise of user accounts, unauthorized access to and exfiltration of sensitive intellectual property such as proprietary design files, and the potential for unauthorized modification of critical workspace settings. The primary risks to the organization are data breaches, loss of competitive advantage through intellectual property theft, and reputational damage.

Remediation Plan

Immediate Action: Prioritize and apply the vendor-supplied security updates to all affected "A stored Multiple Products" instances immediately. After patching, review web server and application access logs for any signs of exploitation attempts that may have occurred before the update was applied.

Proactive Monitoring: Implement enhanced monitoring of the Altium Forum application logs. Specifically, search for submissions containing suspicious HTML tags (e.g., <script>, <iframe>, <img>) or JavaScript event handlers (e.g., onerror, onload). Monitor for unusual account activity, such as data access from anomalous IP addresses or atypical session times, which could indicate a compromised account.

Compensating Controls: If immediate patching is not feasible, consider implementing a Web Application Firewall (WAF) with a robust XSS detection rule set to block malicious payloads. Additionally, advise users to exercise caution when viewing forum posts from unknown or untrusted sources as a temporary mitigation measure.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Jan 15, 2026, there are no known public exploits or active, widespread exploitation campaigns targeting this vulnerability. However, the low complexity of exploitation means that targeted attacks by skilled adversaries are possible.

Analyst Recommendation
Given the critical CVSS score of 9 and the direct risk of intellectual property theft, it is imperative that the organization takes immediate action. We strongly recommend applying the vendor's patch to all affected systems without delay. Although this vulnerability is not currently on the CISA KEV list, its high severity warrants treating it with the highest priority for remediation to prevent potential data breaches and account compromise.

---METADATA---
VENDOR: GitLab
PRODUCT: GitLab EE
AFFECTED_VERSIONS: GitLab EE: all versions from 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2
---END_METADATA---

Description Summary:
A stored cross-site scripting (XSS) vulnerability in the Analytics Dashboard allows authenticated developers to execute malicious code in the context of other users.

Executive Summary:
A high-severity stored cross-site scripting vulnerability in GitLab EE allows authenticated attackers to execute arbitrary code, leading to potential account takeover.

Vulnerability Details

CVE-ID: CVE-2026-10087

Affected Software: GitLab, GitLab EE

Affected Versions: GitLab EE: all versions from 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2

Vulnerability: This vulnerability involves improper input sanitization within the Analytics Dashboard, which allows an authenticated user with developer-role permissions to inject malicious client-side code. This code executes in the context of a targeted user, facilitating session hijacking and unauthorized actions.

Business Impact

The vulnerability carries a CVSS score of 8.7, reflecting a high risk to organizational security. Successful exploitation could lead to full account takeover, unauthorized access to sensitive repository data, and potential privilege escalation within the development environment, resulting in significant reputational and operational damage.

Remediation Plan

Immediate Action: Upgrade all instances of GitLab EE to version 19.0.2, 18.11.5, or 18.10.8 as appropriate for your current deployment branch.

Proactive Monitoring: Review application access logs and audit trails for anomalous activity originating from the Analytics Dashboard or unexpected script executions by user accounts.

Compensating Controls: Implement a strict Content Security Policy (CSP) and ensure a Web Application Firewall (WAF) is configured to detect and block common XSS injection patterns.

Exploitation Status

Public Exploit Available: false

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

Given the potential for complete account compromise and lateral movement within the development pipeline, administrators must prioritize this patch. Apply the vendor-provided security updates immediately to mitigate the risk of malicious code injection and unauthorized session access.

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

Description Summary:
GitLab EE is affected by a security vulnerability requiring immediate remediation to prevent unauthorized system access.

Executive Summary:
GitLab EE contains a high-severity vulnerability in versions 16 and later that poses a significant risk to the security and integrity of the CI/CD pipeline.

Vulnerability Details

CVE-ID: CVE-2026-10086

Affected Software: GitLab GitLab EE

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the GitLab EE platform and requires authenticated access to exploit. It involves a security flaw that could lead to unauthorized actions within the GitLab environment.

Business Impact

The exploitation of this vulnerability could lead to unauthorized access to repositories, environment variables, and sensitive configuration data. With a CVSS score of 8.7, this vulnerability presents a significant risk to intellectual property and development workflows, potentially allowing an attacker to inject malicious code into software build pipelines.

Remediation Plan

Immediate Action: Apply the latest security patches provided by GitLab immediately to remediate the vulnerability.

Proactive Monitoring: Review audit logs for anomalous user activity, particularly unauthorized changes to repository settings or project configurations.

Compensating Controls: Enforce strict access control policies and ensure that multi-factor authentication (MFA) is enabled for all users to minimize the impact of credential-based exploitation.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of June 25, 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 GitLab in the software development lifecycle, it is imperative to apply the vendor-supplied security updates without delay. Security teams should verify that all GitLab instances are running the most recent patched version to ensure continued protection against unauthorized access.

---METADATA---
VENDOR: WordPress
PRODUCT: APCu Manager Plugin
AFFECTED_VERSIONS: Versions before 4
---END_METADATA---

Description Summary:
The APCu Manager WordPress plugin contains a vulnerability that may allow unauthorized actions due to insufficient security controls.

Executive Summary:
The APCu Manager WordPress plugin is affected by a high-severity vulnerability that could allow unauthorized actors to manipulate system cache or configuration settings.

Vulnerability Details

CVE-ID: CVE-2026-10083

Affected Software: WordPress APCu Manager Plugin

Affected Versions: Versions before 4

Vulnerability: This vulnerability involves a lack of sufficient access control or input validation within the plugin's functionality. An attacker could potentially exploit this to impact the APCu caching mechanism, leading to service degradation or unauthorized cache manipulation.

Business Impact

Exploitation of this flaw could lead to unauthorized modification of application cache, resulting in degraded performance or the injection of malicious content into cached data. Given the CVSS score of 7.5, this vulnerability represents a high risk to the availability and reliability of the WordPress environment.

Remediation Plan

Immediate Action: Update the APCu Manager plugin to version 4 or higher immediately to remediate the underlying security flaw.

Proactive Monitoring: Monitor server logs for unusual cache-related errors or attempts to access plugin administrative functions from unauthorized sources.

Compensating Controls: Utilize a Web Application Firewall (WAF) to filter requests directed at the plugin’s endpoints and ensure administrative interfaces are protected by multi-factor authentication.

Exploitation Status

Public Exploit Available: false

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

Analyst Recommendation

Administrators should apply the vendor-provided update to version 4 immediately. If the plugin is not currently required for site functionality, it is recommended to remove it to reduce the overall attack surface of the WordPress installation.

---METADATA---
VENDOR: WordPress
PRODUCT: Unlimited Elements For Elementor
AFFECTED_VERSIONS: 0 up to (excluding) 2.0.11
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The Unlimited Elements For Elementor WordPress plugin before 2.0.11 is vulnerable to cross-site scripting, which may allow attackers to execute arbitrary scripts in a user's browser.

Executive Summary:
A cross-site scripting vulnerability in the Unlimited Elements For Elementor WordPress plugin allows attackers to execute malicious scripts, potentially compromising user sessions and data.

Vulnerability Details

CVE-ID: CVE-2026-10081

Affected Software: WordPress Unlimited Elements For Elementor

Affected Versions: 0 up to (excluding) 2.0.11

Vulnerability: This plugin is affected by a cross-site scripting vulnerability, categorized as CWE-79. The vulnerability is triggered via user interaction and does not require authentication, allowing an unauthenticated attacker to impact the system.

Business Impact

With a CVSS score of 8.8, this vulnerability is critical for web-based applications. Exploitation can lead to session hijacking, defacement of the website, or the redirection of users to malicious third-party sites, causing significant reputational and operational damage.

Remediation Plan

Immediate Action: Update the Unlimited Elements For Elementor plugin to version 2.0.11 or later immediately.

Proactive Monitoring: Monitor site logs for unusual URL parameters or attempts to inject script tags into common input fields.

Compensating Controls: Utilize a Web Application Firewall (WAF) with updated rulesets to detect and block common XSS attack vectors targeted at WordPress plugins.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 21, 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 a proof-of-concept significantly elevates the urgency of this remediation.

Analyst Recommendation

Given the availability of a proof-of-concept and the high CVSS score, it is imperative to update the plugin to the patched version without delay. Failure to apply this update leaves the site vulnerable to automated exploitation attempts that could compromise administrative or user accounts.

---METADATA---
VENDOR: Red Hat
PRODUCT: Advanced Cluster Security for Kubernetes
AFFECTED_VERSIONS: See vendor advisory
CONFIDENCE: medium
MISSING: versions
---END_METADATA---

Description Summary:
A vulnerability in Red Hat Advanced Cluster Security for Kubernetes (RHACS) allows for insufficient verification of data authenticity.

Executive Summary:
A flaw in Red Hat Advanced Cluster Security for Kubernetes (RHACS) concerning data authenticity verification poses a high risk of integrity compromise.

Vulnerability Details

CVE-ID: CVE-2026-10079

Affected Software: Red Hat Advanced Cluster Security for Kubernetes

Affected Versions: See vendor advisory

Vulnerability: This vulnerability, identified as CWE-345, involves insufficient verification of data authenticity. It requires low-privileged authenticated access, allowing an attacker to manipulate data integrity within the cluster security environment.

Business Impact

The CVSS score of 8.5 indicates a high-severity risk, particularly due to the potential for cross-domain integrity compromise. Successful exploitation could allow an attacker to bypass security controls or inject malicious configurations into the Kubernetes cluster. This poses a significant threat to the overall security posture of containerized infrastructure.

Remediation Plan

Immediate Action: Consult the Red Hat Security Advisory (RHSA) for the specific patched version and apply the update immediately.

Proactive Monitoring: Monitor cluster audit logs for unauthorized configuration changes or unexpected data modifications in the security context.

Compensating Controls: Utilize Kubernetes network policies and admission controllers to restrict the impact of unauthorized data modifications while awaiting patch deployment.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 1, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherently dangerous due to the nature of the target, which is responsible for enforcing security policy across container clusters.

Analyst Recommendation

Security teams should treat this vulnerability with high urgency. Users must verify their current version against the Red Hat advisory and apply the necessary patches to prevent potential integrity loss within their Kubernetes environments.

---METADATA---
VENDOR: Interinfo
PRODUCT: DreamMaker
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
Interinfo's DreamMaker contains an arbitrary file upload vulnerability that allows unauthenticated remote attackers to execute web shells and achieve code execution.

Executive Summary:
An arbitrary file upload vulnerability in DreamMaker allows unauthenticated attackers to execute arbitrary code via web shells.

Vulnerability Details

CVE-ID: CVE-2026-10071

Affected Software: Interinfo DreamMaker

Affected Versions: See vendor advisory

Vulnerability: The application fails to properly validate file uploads, allowing unauthenticated remote attackers to upload malicious files, such as web shells. These files can then be executed on the server, resulting in Remote Code Execution (RCE).

Business Impact

The CVSS score of 9.8 confirms the critical severity of this flaw. Unauthenticated access significantly lowers the bar for exploitation, making this a prime target for attackers looking to gain an immediate foothold on the server to exfiltrate data or disrupt services.

Remediation Plan

Immediate Action: Check the vendor advisory for patch availability and apply the update immediately.

Proactive Monitoring: Monitor the web server for the presence of unexpected files in upload directories and review logs for suspicious requests pointing to new, unknown files.

Compensating Controls: Use a Web Application Firewall (WAF) to inspect and block suspicious file upload attempts and restrict execution permissions in upload directories.

Exploitation Status

Public Exploit Available: True

Analyst Notes: As of May 29, 2026, there is public information indicating that this vulnerability is exploitable. Given the availability of exploits, the risk is extremely high and immediate action is required.

Analyst Recommendation

The presence of a public exploit makes this a high-priority risk. Organizations using DreamMaker should assume that an exploit attempt is likely and must apply the vendor-provided security patches or mitigations immediately.

---METADATA---
VENDOR: Shibby
PRODUCT: Tomato
AFFECTED_VERSIONS: 1.28
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A stack-based buffer overflow vulnerability exists in Shibby Tomato 1.28, potentially allowing for memory corruption and arbitrary code execution.

Executive Summary:
A critical stack-based buffer overflow vulnerability in Shibby Tomato 1.28 poses a severe risk of memory corruption and potential system compromise.

Vulnerability Details

CVE-ID: CVE-2026-10067

Affected Software: Shibby Tomato

Affected Versions: 1.28

Vulnerability: This vulnerability (CWE-121, CWE-119) involves a stack-based buffer overflow that can lead to memory corruption when processing specific inputs, requiring a low-privileged authenticated attacker to trigger.

Business Impact

Successful exploitation of this memory corruption vulnerability can lead to system crashes or arbitrary code execution, resulting in full loss of confidentiality, integrity, and availability. With a CVSS score of 8.8, this vulnerability poses a major threat to network infrastructure relying on the affected firmware.

Remediation Plan

Immediate Action: Since no specific patch version is currently listed, users should restrict administrative access and monitor vendor channels for firmware security updates.

Proactive Monitoring: Review device logs for irregular service crashes or unexpected restarts which may indicate attempts to exploit buffer overflow conditions.

Compensating Controls: Disable unnecessary services and minimize the exposed management interface surface area via firewall rules to reduce the attack vector.

Exploitation Status

Public Exploit Available: No (Exploit available: false)

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Memory corruption flaws in firmware are highly sensitive and require immediate attention if a vendor patch is released.

Analyst Recommendation

This vulnerability is highly critical due to the potential for remote code execution. Because an official patch is currently unknown, organizations should prioritize isolating affected devices from the public internet and implementing strict access controls until a vendor-supplied firmware update is available.

---METADATA---
VENDOR: Shibby
PRODUCT: Tomato
AFFECTED_VERSIONS: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Shibby Tomato versions 1.0 through 1.7 are susceptible to a stack-based buffer overflow, potentially leading to memory corruption and unauthorized system impacts.

Executive Summary:
A critical stack-based buffer overflow vulnerability in multiple versions of Shibby Tomato allows for memory corruption, risking unauthorized system access.

Vulnerability Details

CVE-ID: CVE-2026-10066

Affected Software: Shibby Tomato

Affected Versions: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7

Vulnerability: The software is vulnerable to a stack-based buffer overflow (CWE-121) and memory corruption (CWE-119), which can be triggered by an authenticated attacker to cause system instability or potential code execution.

Business Impact

The ability to trigger memory corruption at the firmware level creates a high risk of total system failure or unauthorized control. Given the CVSS score of 8.8, this represents a significant risk to the availability and security of the network hardware impacted by this vulnerability.

Remediation Plan

Immediate Action: As no patch is currently available, users are advised to transition to a more secure or maintained firmware version if possible.

Proactive Monitoring: Closely monitor network device uptime and error logs for signs of anomalous behavior or service failure that could indicate exploit attempts.

Compensating Controls: Restrict access to the device management interface to trusted management IP addresses only and disable remote management features.

Exploitation Status

Public Exploit Available: No (Exploit available: false)

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. These legacy versions are likely end-of-life, increasing the urgency to migrate to supported hardware or firmware.

Analyst Recommendation

Given the lack of available patches for these specific versions, organizations should treat these devices as inherently insecure. The primary recommendation is to replace or upgrade hardware running these outdated firmware versions to eliminate the risk posed by this buffer overflow.

---METADATA---
VENDOR: Shibby
PRODUCT: Tomato
AFFECTED_VERSIONS: 1.28
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Shibby Tomato 1.28 is vulnerable to a stack-based buffer overflow, which could allow an authenticated attacker to execute arbitrary code or cause a system crash.

Executive Summary:
A stack-based buffer overflow in Shibby Tomato version 1.28 poses a high risk of remote code execution for authenticated users.

Vulnerability Details

CVE-ID: CVE-2026-10065

Affected Software: Shibby Tomato

Affected Versions: 1.28

Vulnerability: This vulnerability involves a stack-based buffer overflow (CWE-121) and memory corruption (CWE-119). Based on the CVSS vector (PR:L), the attacker must be authenticated to trigger the vulnerable function.

Business Impact

The vulnerability carries a CVSS score of 8.8, indicating a high severity. Successful exploitation allows an attacker to gain elevated control over the affected network device, potentially leading to total system compromise, unauthorized network access, and the ability to intercept or modify traffic passing through the router.

Remediation Plan

Immediate Action: Since a specific patch is not currently identified, users should restrict administrative access to the device to trusted users only and monitor for vendor updates.

Proactive Monitoring: Review system logs for unexpected reboots, segmentation faults, or unauthorized access attempts from internal user accounts.

Compensating Controls: Implement network segmentation to isolate the affected device from critical internal resources, limiting the lateral movement potential of an attacker.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of May 30, 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 its potential for memory corruption and code execution.

Analyst Recommendation

Given the high impact and the existence of a proof-of-concept, administrators should prioritize hardening the configuration of Shibby Tomato devices. Immediately limit administrative interface access and remain alert for official patches from the vendor to remediate the underlying memory corruption flaw.

---METADATA---
VENDOR: TRENDnet
PRODUCT: TEW-432BRP
AFFECTED_VERSIONS: 3.10B20
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The TRENDnet TEW-432BRP router, version 3.10B20, contains a stack-based buffer overflow vulnerability that may lead to memory corruption when triggered by an authenticated attacker.

Executive Summary:
A stack-based buffer overflow in TRENDnet TEW-432BRP firmware 3.10B20 exposes the device to memory corruption and potential system failure.

Vulnerability Details

CVE-ID: CVE-2026-10063

Affected Software: TRENDnet TEW-432BRP

Affected Versions: 3.10B20

Vulnerability: The vulnerability is a stack-based buffer overflow (CWE-121) and memory corruption (CWE-119). The CVSS vector indicates this requires low privileges (PR:L), meaning an attacker must already have authenticated access to the device management interface.

Business Impact

With a CVSS score of 8.8, this vulnerability presents a significant risk to network integrity. Exploitation could allow an attacker to crash the device, causing denial of service, or potentially execute arbitrary code, compromising the security of the entire local network connected to the router.

Remediation Plan

Immediate Action: As no patch is currently available, disable remote management interfaces and restrict access to the device's web management console to a specific, trusted management IP address.

Proactive Monitoring: Monitor device uptime and check system logs for signs of service crashes or unauthorized configuration changes.

Compensating Controls: Ensure that the router is not exposed to the public internet and utilize internal firewall rules to limit who can communicate with the management port.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The risk remains high due to the nature of buffer overflow vulnerabilities in network hardware.

Analyst Recommendation

Administrators should treat this device as high-risk until the vendor provides a firmware update. Restrict access to the management interface immediately to mitigate the risk of an attacker leveraging this vulnerability to compromise the router.

---METADATA---
VENDOR: TRENDnet
PRODUCT: TEW-432BRP
AFFECTED_VERSIONS: 3.10B20
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
TRENDnet TEW-432BRP version 3.10B20 contains a stack-based buffer overflow vulnerability, potentially allowing an authenticated attacker to cause memory corruption.

Executive Summary:
A critical stack-based buffer overflow in TRENDnet TEW-432BRP firmware 3.10B20 could result in memory corruption and unauthorized system impact.

Vulnerability Details

CVE-ID: CVE-2026-10062

Affected Software: TRENDnet TEW-432BRP

Affected Versions: 3.10B20

Vulnerability: This is a stack-based buffer overflow (CWE-121) and memory corruption (CWE-119) issue. The vulnerability requires low privileges (PR:L), meaning the attacker must be authenticated to the device.

Business Impact

The CVSS score of 8.8 reflects the high potential for system-level impact. Exploitation could lead to a complete denial of service or unauthorized code execution, threatening the confidentiality and integrity of traffic routed through the affected hardware.

Remediation Plan

Immediate Action: Until a firmware patch is released, ensure the management interface is not accessible from untrusted networks and restrict management access to authorized personnel only.

Proactive Monitoring: Watch for anomalous behavior in router performance and audit logs for unauthorized attempts to access management functions.

Compensating Controls: Use network-level access control lists (ACLs) to block all traffic to the device's management ports except from dedicated, secure administration workstations.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of May 30, 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. Buffer overflow vulnerabilities are highly dangerous in firmware environments where security controls are often limited.

Analyst Recommendation

Given the existence of a proof-of-concept and the nature of the vulnerability, it is imperative to isolate the affected hardware from all non-essential network access. Maintain close contact with the vendor for firmware updates and apply them immediately upon release.

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

Description Summary:
A security flaw has been identified in Eclipse Theia that could lead to unauthorized system impacts. Users are advised to await further guidance from the vendor.

Executive Summary:
A high-severity security flaw in Eclipse Theia could potentially be leveraged by attackers to compromise the underlying development framework.

Vulnerability Details

CVE-ID: CVE-2026-10055

Affected Software: Eclipse Theia

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the Eclipse Theia platform, representing a serious security risk within the application architecture. The specific entry point and authentication requirements remain under investigation, and administrators should assume a high risk of unauthorized access.

Business Impact

With a CVSS score of 8.5, this vulnerability represents a substantial threat to the stability and security of development infrastructure. Exploitation may result in the compromise of intellectual property, unauthorized access to build pipelines, and disruption of critical development workflows.

Remediation Plan

Immediate Action: Closely monitor the Eclipse security advisory page for the release of security patches and apply them immediately upon availability.

Proactive Monitoring: Review system access logs for anomalous behavior or unauthorized administrative actions within the Theia environment.

Compensating Controls: Utilize Web Application Firewalls (WAF) or ingress filtering to limit exposure of the Theia instance to untrusted network segments.

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

The severity of this vulnerability necessitates a proactive posture. Security teams must verify their current versioning against vendor disclosures and prepare to deploy updates immediately to prevent unauthorized exploitation of the development environment.

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

Description Summary:
A vulnerability in Eclipse Theia potentially allows for unauthorized system interaction. The exact nature of the flaw requires further clarification from the vendor.

Executive Summary:
A high-severity vulnerability in Eclipse Theia poses a significant risk to development environments, potentially allowing unauthorized access or execution.

Vulnerability Details

CVE-ID: CVE-2026-10054

Affected Software: Eclipse Theia

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability involves a security flaw within the Eclipse Theia framework. Based on the current disclosure, it is unclear if the vulnerability requires authentication, necessitating a cautious approach until full technical details are released.

Business Impact

The CVSS score of 8.8 indicates a high-severity risk that could lead to unauthorized code execution or sensitive information disclosure within integrated development environments. Successful exploitation could compromise source code integrity, facilitate lateral movement within the network, and cause significant operational downtime for development teams.

Remediation Plan

Immediate Action: Review the official Eclipse security portal for patch availability and apply updates as soon as they are released.

Proactive Monitoring: Monitor development server logs for unusual traffic patterns or unauthorized access attempts to the Theia service.

Compensating Controls: Implement strict network segmentation and ensure that development environments are not exposed to the public internet.

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 development framework, the potential for exploitation is high.

Analyst Recommendation

Given the high CVSS score, organizations utilizing Eclipse Theia should prioritize monitoring vendor communications for immediate patching instructions. Until a patch is available, restrict access to the application to trusted personnel and verify the integrity of the development environment.

---METADATA---
VENDOR: Eclipse Foundation
PRODUCT: Eclipse Jetty
AFFECTED_VERSIONS: 9.4.0 through 9.4.62, 10.0.0 through 10.0.30, 11.0.0 through 11.0.30, 12.0.0 through 12.0.35, 12.1.0 through 12.1.9
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Digest authentication component in Eclipse Jetty incorrectly uses ISO-8859-1 encoding for passwords, which can lead to authentication bypass or credential handling issues.

Executive Summary:
A flaw in the Eclipse Jetty Digest authentication mechanism regarding character encoding potentially undermines the security of user credentials and authentication processes.

Vulnerability Details

CVE-ID: CVE-2026-10050

Affected Software: Eclipse Foundation Eclipse Jetty

Affected Versions: 9.4.0 through 9.4.62, 10.0.0 through 10.0.30, 11.0.0 through 11.0.30, 12.0.0 through 12.0.35, 12.1.0 through 12.1.9

Vulnerability: The Digest authentication server-side component incorrectly uses ISO-8859-1 encoding to process password bytes. This vulnerability affects unauthenticated remote attackers who can leverage the encoding mismatch to potentially bypass authentication checks.

Business Impact

Successful exploitation of this authentication flaw could allow attackers to bypass security controls, resulting in unauthorized access to protected resources. With a CVSS score of 8.7, the risk of credential compromise is high, necessitating immediate attention to prevent potential data breaches.

Remediation Plan

Immediate Action: Update the Eclipse Jetty server to the latest version provided by the Eclipse Foundation to ensure the authentication component uses proper encoding standards.

Proactive Monitoring: Review authentication logs for anomalous patterns or failed login attempts that may suggest an attempt to exploit the Digest authentication mechanism.

Compensating Controls: If an immediate patch is not feasible, consider disabling Digest authentication in favor of stronger, alternative authentication methods until the update is applied.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 4, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The nature of the flaw requires specific knowledge of the encoding implementation, but it remains a high-risk vector.

Analyst Recommendation

Given the central role of Eclipse Jetty in many application architectures, this vulnerability presents a significant risk. Administrators must verify their current version and apply the vendor-provided patches as soon as they are made available to maintain a secure environment.

---METADATA---
VENDOR: Shenzhen Kangda Xin Intelligent Network Technology
PRODUCT: DR300 Router
AFFECTED_VERSIONS: Version 2.1.2.121
---END_METADATA---

Description Summary:
The Shenzhen Kangda Xin DR300 router contains hardcoded credentials and has Telnet enabled by default, allowing for full device compromise.

Executive Summary:
The Shenzhen Kangda Xin DR300 router is vulnerable to full device takeover due to hardcoded credentials and insecure default Telnet configurations.

Vulnerability Details

CVE-ID: CVE-2026-10045

Affected Software: Shenzhen Kangda Xin DR300 Router

Affected Versions: 2.1.2.121

Vulnerability: This vulnerability involves the use of hardcoded login credentials and the default enabling of the Telnet service on both WAN and LAN interfaces. These factors allow an unauthenticated attacker to gain remote access, read/write memory, modify firmware, and monitor network traffic.

Business Impact

With a CVSS score of 9.8, this device is effectively wide open to any attacker with network reach. Compromise of a router allows for persistent backdoor installation, interception of internal traffic, and use of the device as a pivot point for further attacks on the internal network, posing a critical risk to any environment where this device is deployed.

Remediation Plan

Immediate Action: Update the firmware to the latest available version; if no update is available, immediately disable Telnet and replace the device.

Proactive Monitoring: Scan for unauthorized Telnet connections and monitor for anomalous traffic patterns emanating from the router.

Compensating Controls: Place the router behind a robust firewall and ensure the WAN interface is not reachable from the public internet.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of June 9, 2026, there is no public information indicating active exploitation; however, the presence of hardcoded credentials makes this device highly susceptible to automated botnet recruitment.

Analyst Recommendation

Due to the nature of the vulnerabilities (hardcoded credentials and insecure services), this router is fundamentally insecure in its default state. Organizations should prioritize decommissioning these devices or ensuring they are entirely isolated from public-facing networks until a secure configuration or patch is applied.

---METADATA---
VENDOR: manga-image-translator
PRODUCT: API Server
AFFECTED_VERSIONS: See vendor advisory
---END_VERSIONS---
---END_METADATA---

Description Summary:
The manga-image-translator API server is vulnerable to remote code execution via unsafe deserialization of untrusted pickle data in the share.py module.

Executive Summary:
A critical remote code execution vulnerability in the manga-image-translator API allows attackers to compromise the host container by sending malicious pickle payloads.

Vulnerability Details

CVE-ID: CVE-2026-10042

Affected Software: manga-image-translator API Server

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The application uses pickle.loads() to deserialize attacker-controlled HTTP request bodies in the /execute/{method_name} and /simple_execute/{method_name} endpoints. An unauthenticated attacker can leverage this to execute arbitrary code within the server process, often resulting in full container compromise.

Business Impact

The CVSS score of 9.8 underscores the extreme danger of this vulnerability. Successful exploitation permits an attacker to gain full control over the container, which, if running with elevated privileges (root), could lead to complete host system compromise and lateral movement within the network.

Remediation Plan

Immediate Action: Update the application to the latest version provided by the vendor, which should remove reliance on insecure pickle deserialization.

Proactive Monitoring: Monitor network traffic for anomalous payloads directed at the /execute/ or /simple_execute/ endpoints and inspect container process logs for signs of arbitrary command execution.

Compensating Controls: Place the API behind a robust authentication gateway and use a WAF to filter out requests containing serialized Python object patterns or other suspicious binary data.

Exploitation Status

Public Exploit Available: No data available.

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

Analyst Recommendation

The use of insecure deserialization is a high-risk practice that must be remediated immediately. Organizations must update their deployment and ensure that the application is not running with unnecessary root privileges to limit the blast radius of potential exploits.

---METADATA---
VENDOR: Canonical
PRODUCT: Ubuntu
AFFECTED_VERSIONS: Ubuntu 26.04 LTS, 25.10, 24.04 LTS, 22.04 LTS
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A sandbox escape vulnerability in Ubuntu's OpenJDK packages allows arbitrary code execution outside the sandbox when the mailcap package is installed.

Executive Summary:
A high-severity sandbox escape vulnerability exists in Canonical Ubuntu OpenJDK packages that allows local attackers to execute arbitrary code outside of the intended sandbox environment.

Vulnerability Details

CVE-ID: CVE-2026-10037

Affected Software: Canonical Ubuntu

Affected Versions: Ubuntu 26.04 LTS resolute prior to mailcap 3.75ubuntu1.1, Ubuntu 25.10 questing prior to mailcap 3.74ubuntu1.1, Ubuntu 24.04 LTS noble prior to mailcap 3.70+nmu1ubuntu1.24.04.1, and Ubuntu 22.04 LTS jammy prior to mailcap 3.70+nmu1ubuntu1.22.04.1.

Vulnerability: This vulnerability occurs because .jar MIME handlers execute files marked as executable when the mailcap package is present. This flaw allows a compromised application running within a sandbox to bypass security controls and execute arbitrary code on the underlying host system.

Business Impact

With a CVSS score of 8.8, this vulnerability poses a significant risk to system integrity and confidentiality. Successful exploitation permits an attacker to escape containerized or sandboxed environments, potentially leading to full system compromise, unauthorized data access, and lateral movement within the network.

Remediation Plan

Immediate Action: Update the mailcap package to the patched versions: 3.75ubuntu1.1, 3.74ubuntu1.1, 3.70+nmu1ubuntu1.24.04.1, or 3.70+nmu1ubuntu1.22.04.1 depending on your Ubuntu release.

Proactive Monitoring: Review system access logs for anomalous process execution patterns originating from sandboxed Java applications.

Compensating Controls: If patching is delayed, restrict the use of MIME handlers for .jar files and limit the execution permissions of untrusted applications within the environment.

Exploitation Status

Public Exploit Available: false

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

Analyst Recommendation

The severity of this sandbox escape necessitates immediate action. Administrators should prioritize the deployment of the specified mailcap security updates across all affected Ubuntu instances to prevent potential host-level compromise.

---METADATA---
VENDOR: WordPress
PRODUCT: EventON Action User
AFFECTED_VERSIONS: 0 through 2.5.14
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
The EventON Action User plugin for WordPress contains an authorization bypass vulnerability, potentially allowing unauthenticated attackers to perform unauthorized actions.

Executive Summary:
A high-severity authorization bypass vulnerability exists in the EventON Action User plugin for WordPress that could allow unauthenticated attackers to perform unauthorized operations.

Vulnerability Details

CVE-ID: CVE-2026-10033

Affected Software: WordPress EventON Action User

Affected Versions: 0 through 2.5.14

Vulnerability: This is a missing authorization flaw (CWE-862) within the plugin, which fails to adequately verify user permissions during certain AJAX requests. The vulnerability is accessible to unauthenticated attackers, as indicated by the CVSS vector.

Business Impact

Successful exploitation allows unauthorized actors to execute administrative or user-level functions without proper authentication. This could lead to sensitive data exposure, unauthorized modification of event data, or other service disruptions, posing a significant risk to site integrity. The CVSS score of 7.3 reflects the high potential for impact on Confidentiality, Integrity, and Availability.

Remediation Plan

Immediate Action: Update the EventON Action User plugin to version 2.5.15 or later immediately to resolve the missing authorization flaw.

Proactive Monitoring: Review web server access logs for unusual patterns or spikes in AJAX request activity directed at the plugin, which may indicate attempted exploitation.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block suspicious or unauthorized requests targeting the plugin's AJAX endpoints.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of July 26, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently exploitable due to the lack of access control checks on critical functions.

Analyst Recommendation

Given the ease of exploitation and the potential for unauthorized administrative actions, immediate patching is essential. Administrators should prioritize upgrading the EventON Action User plugin to the latest version to neutralize this risk and prevent potential compromise of their WordPress environment.

---METADATA---
VENDOR: IBM
PRODUCT: QRadar
AFFECTED_VERSIONS: 7.6.0.0 through 7.6.0.1, 7.5.0 through 7.5.0 UP 15 Interim Fix 005
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
IBM QRadar is susceptible to XML External Entity (XXE) injection, which may allow an unauthenticated attacker to read arbitrary files from the server.

Executive Summary:
An unauthenticated XML External Entity (XXE) vulnerability in IBM QRadar versions 7.6.0 and 7.5.0 allows attackers to access sensitive system files.

Vulnerability Details

CVE-ID: CVE-2026-10025

Affected Software: IBM QRadar

Affected Versions: 7.6.0.0 through 7.6.0.1, 7.5.0 through 7.5.0 UP 15 Interim Fix 005

Vulnerability: This is an XXE vulnerability (CWE-611) that occurs due to improper restriction of XML external entity references. It is remotely exploitable by an unauthenticated attacker.

Business Impact

The ability for an unauthenticated attacker to perform file disclosure poses a high risk to organizational data. The CVSS score of 8.2 reflects the severity, as this could lead to the exposure of configuration files, credentials, or sensitive system information, significantly undermining the security of the SIEM platform.

Remediation Plan

Immediate Action: Apply the specific patches provided by IBM: update to 7.6.0.2 for version 7.6.0, or apply the 7.5.0 UP15 IF05 Hotfix 20260715231428 for version 7.5.0.

Proactive Monitoring: Monitor network traffic and server logs for XML-based payloads or anomalous requests aimed at system files.

Compensating Controls: Utilize a WAF to block requests containing DOCTYPE declarations or external entity references that are characteristic of XXE attacks.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. XXE vulnerabilities are inherently dangerous due to their potential for remote, unauthenticated file access.

Analyst Recommendation

Given the lack of authentication requirements for this exploit, it represents a high-priority risk. Security teams should expedite the deployment of the specified hotfixes and patches to ensure the integrity and confidentiality of the QRadar deployment.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome 148.0.7778.216
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A type confusion vulnerability exists in the V8 JavaScript engine within Google Chrome, potentially allowing for arbitrary code execution.

Executive Summary:
A high-severity type confusion vulnerability in Google Chrome's V8 engine could allow an unauthenticated attacker to execute arbitrary code via a crafted web page.

Vulnerability Details

CVE-ID: CVE-2026-10022

Affected Software: Google Chrome

Affected Versions: Google Chrome 148.0.7778.216

Vulnerability: This is a Type Confusion vulnerability (CWE-843) occurring in the V8 engine. The flaw is triggered when the engine incorrectly handles object types, which can be exploited by an unauthenticated remote attacker through a victim interacting with malicious content.

Business Impact

The vulnerability carries a CVSS score of 8.8, reflecting its potential for total impact on system confidentiality, integrity, and availability. Successful exploitation allows for remote code execution, which could lead to full system compromise, unauthorized data access, and significant operational disruption.

Remediation Plan

Immediate Action: Update Google Chrome to version 148.0.7778.216 or later immediately to resolve the vulnerable V8 component.

Proactive Monitoring: Monitor endpoint security logs for unusual browser process activity or crashes related to the V8 engine.

Compensating Controls: While no direct virtual patch exists, ensuring that users operate with the minimum necessary privileges can limit the impact of a successful code execution event.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Type confusion in V8 is a historically frequent attack vector, making this a high-priority update for all deployments.

Analyst Recommendation

Given the severity of V8-related vulnerabilities in browser environments, security teams must prioritize the deployment of the latest Chrome update across all workstations. Prompt patching is the only effective way to neutralize this threat and prevent potential remote code execution attacks.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome 148.0.7778.216
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Google Chrome contains a vulnerability involving insufficient validation of untrusted input within its USB implementation, potentially leading to system compromise.

Executive Summary:
A critical input validation vulnerability in Google Chrome's USB stack poses a significant risk of remote system compromise for users.

Vulnerability Details

CVE-ID: CVE-2026-10021

Affected Software: Google Chrome

Affected Versions: Google Chrome 148.0.7778.216

Vulnerability: The vulnerability is defined as insufficient validation of untrusted input (CWE-20) within the browser's USB handling logic. It is an unauthenticated, remote vulnerability that requires user interaction to execute.

Business Impact

With a CVSS score of 8.8, this vulnerability represents a high risk to the enterprise. Exploitation could lead to unauthorized access to system resources, potential data theft, and the ability for an attacker to execute arbitrary code within the context of the user's browser or system.

Remediation Plan

Immediate Action: Apply the latest security update to Google Chrome to ensure the USB input validation logic is properly secured.

Proactive Monitoring: Review browser logs and endpoint telemetry for anomalous USB-related service calls or unexpected browser behavior.

Compensating Controls: Restricting browser access to hardware APIs through enterprise policy management can serve as a temporary mitigation if patching is delayed.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Input validation flaws in browser hardware interfaces are high-value targets for attackers seeking to bypass sandbox protections.

Analyst Recommendation

All systems running Google Chrome should be updated to the latest version immediately. Failure to address this vulnerability increases the risk of remote exploitation, making rapid patching a critical component of the organization's browser security posture.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome 148.0.7778.216
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
An integer overflow vulnerability exists in the ANGLE graphics library used by Google Chrome, which could result in application-level issues.

Executive Summary:
An integer overflow vulnerability in Google Chrome's ANGLE graphics component may allow for restricted impact to the application environment.

Vulnerability Details

CVE-ID: CVE-2026-10019

Affected Software: Google Chrome

Affected Versions: Google Chrome 148.0.7778.216

Vulnerability: This is an integer overflow vulnerability (CWE-472) located within the ANGLE graphics library. The flaw is triggered via remote, unauthenticated access with user interaction, specifically affecting the confidentiality of the application.

Business Impact

While the CVSS score is 8.8, the vector indicates a more limited impact on confidentiality compared to code execution, as the flaw primarily impacts the ANGLE library's integer handling. Nevertheless, it remains a security concern that could be leveraged as part of a larger exploit chain to compromise the browser environment.

Remediation Plan

Immediate Action: Update Google Chrome to the latest version to patch the integer overflow in the ANGLE library.

Proactive Monitoring: Monitor for browser instability or graphics-related rendering issues that may indicate exploitation attempts.

Compensating Controls: Ensure standard browser security features, such as sandboxing, remain enabled to isolate the graphics process.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Integer overflows in graphics libraries often serve as the initial stage in complex, multi-stage exploit chains.

Analyst Recommendation

Security teams should treat this update with urgency, as it addresses a flaw in the browser's graphics rendering stack. Applying the latest Chrome update is necessary to ensure the integrity of the browser and to prevent the potential use of this vulnerability in chained attacks.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome versions prior to 148.0.7778.216
---END_METADATA---

Description Summary:
An out-of-bounds read vulnerability in the Headless mode of Google Chrome can be leveraged for sandbox escapes.

Executive Summary:
A high-severity out-of-bounds read vulnerability in Google Chrome's Headless mode presents a risk of sandbox escape to remote attackers.

Vulnerability Details

CVE-ID: CVE-2026-10017

Affected Software: Google Chrome

Affected Versions: Google Chrome prior to 148.0.7778.216

Vulnerability: This vulnerability involves an out-of-bounds read within the Headless browser component. An unauthenticated remote attacker who has compromised the renderer process can leverage this flaw through a crafted HTML page to potentially escape the sandbox and execute arbitrary code.

Business Impact

The CVSS score of 8.3 underscores the necessity for remediation. Out-of-bounds read vulnerabilities can be precursors to more complex exploitation chains, allowing attackers to access sensitive memory regions, potentially leading to data leakage or full system compromise.

Remediation Plan

Immediate Action: Patch Google Chrome to version 148.0.7778.216 or newer across all platforms.

Proactive Monitoring: Audit logs for suspicious activity originating from automated browser or "Headless" browser instances.

Compensating Controls: Restrict the execution of Headless browser instances in production environments to trusted users and applications only.

Exploitation Status

Public Exploit Available: false

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

Analyst Recommendation

Organizations utilizing Headless Chrome for automation or testing should prioritize this update. Addressing this vulnerability is critical to maintaining the security boundary of the browser, especially in environments where automated scripts may be exposed to untrusted external content.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A Use-After-Free vulnerability in the DOM component of Google Chrome allows for potential memory corruption.

Executive Summary:
A high-severity Use-After-Free vulnerability in Google Chrome could allow a remote attacker to execute arbitrary code via a specially crafted webpage.

Vulnerability Details

CVE-ID: CVE-2026-10016

Affected Software: Google Chrome

Affected Versions: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216

Vulnerability: This is a Use-After-Free vulnerability located within the DOM (Document Object Model) implementation. The vulnerability is triggered when an unauthenticated remote attacker convinces a user to visit a malicious site.

Business Impact

Successful exploitation of this flaw can lead to remote code execution, resulting in full system compromise, unauthorized data access, or the deployment of malware. With a CVSS score of 8.8, this vulnerability poses a significant risk to organizational endpoints, necessitating immediate remediation to prevent potential operational disruption or data breaches.

Remediation Plan

Immediate Action: Update all Google Chrome instances to version 148.0.7778.216 or later immediately.

Proactive Monitoring: Review endpoint logs for unexpected browser crashes or suspicious network activity originating from browser processes.

Compensating Controls: Utilize endpoint protection platforms (EPP) and browser-based security policies to restrict execution of untrusted scripts.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Use-After-Free flaws in browser engines are classic vectors for exploitation and should be patched without delay.

Analyst Recommendation

Given the critical nature of browser-based memory corruption vulnerabilities, IT teams must prioritize the deployment of the provided security update. Failure to patch these vulnerabilities leaves users susceptible to drive-by download attacks and browser-based exploits.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
An integer overflow vulnerability in the WTF (Web Template Framework) library of Google Chrome may lead to memory corruption.

Executive Summary:
An integer overflow vulnerability in Google Chrome's WTF component poses a high risk of remote code execution through malicious web content.

Vulnerability Details

CVE-ID: CVE-2026-10015

Affected Software: Google Chrome

Affected Versions: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216

Vulnerability: This vulnerability is an integer overflow located in the WTF component of Google Chrome. It requires an unauthenticated remote attacker to entice a user into visiting a malicious webpage to trigger the flaw.

Business Impact

The integer overflow can be leveraged to bypass security controls or achieve remote code execution, threatening the integrity and confidentiality of the host machine. The CVSS score of 8.8 reflects the high potential for total impact if the vulnerability is successfully exploited by an attacker.

Remediation Plan

Immediate Action: Apply the latest Google Chrome security updates to version 148.0.7778.216 or higher.

Proactive Monitoring: Monitor for abnormal memory usage patterns in browser processes or suspicious redirects within the web environment.

Compensating Controls: Ensure that browser security settings are configured to high-protection modes and deploy endpoint security software to detect malicious payloads.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Integer overflows in core browser libraries are high-value targets for attackers and require prompt attention.

Analyst Recommendation

Organizations should enforce automated browser updates to ensure all workstations are protected against this high-severity vulnerability. Prompt patching is the most effective way to eliminate the risk of exploitation.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A Use-After-Free vulnerability in the WebCodecs API of Google Chrome could lead to unauthorized code execution.

Executive Summary:
A critical Use-After-Free flaw in Google Chrome's WebCodecs API exposes users to potential remote code execution via malicious web content.

Vulnerability Details

CVE-ID: CVE-2026-10013

Affected Software: Google Chrome

Affected Versions: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216

Vulnerability: This vulnerability is a Use-After-Free error occurring within the WebCodecs API. An unauthenticated attacker can exploit this by directing a user to a specially crafted website to trigger memory corruption.

Business Impact

Exploitation of this vulnerability may allow an attacker to execute arbitrary code within the context of the browser, potentially leading to full system compromise. The CVSS score of 8.8 highlights the severity of this issue, necessitating rapid response to protect organizational assets.

Remediation Plan

Immediate Action: Update all Google Chrome installations to version 148.0.7778.216 or later.

Proactive Monitoring: Monitor for unexpected browser process terminations or unusual memory consumption metrics across the enterprise.

Compensating Controls: Use web filtering to prevent access to unverified or malicious domains that could host exploits.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Use-After-Free vulnerabilities are frequently targeted for exploit development due to their ability to facilitate code execution.

Analyst Recommendation

The severity of this vulnerability dictates an immediate update cycle across all managed devices. Security teams should prioritize this patch to neutralize the threat of remote code execution.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the SVG component of Google Chrome allows for potential memory corruption.

Executive Summary:
A use-after-free vulnerability in Google Chrome's SVG implementation poses a significant risk of arbitrary code execution for unauthenticated users.

Vulnerability Details

CVE-ID: CVE-2026-10007

Affected Software: Google Chrome

Affected Versions: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216

Vulnerability: This is a use-after-free (CWE-416) vulnerability within the SVG rendering component. The attacker requires the user to interact with a specially crafted web page, effectively making this an unauthenticated, user-assisted attack vector.

Business Impact

Successful exploitation allows an attacker to achieve arbitrary code execution within the context of the browser, potentially leading to total system compromise or data exfiltration. Given the CVSS score of 8.8, this flaw represents a high-severity risk that could disrupt business operations and compromise sensitive user credentials or internal corporate data.

Remediation Plan

Immediate Action: Update all instances of Google Chrome to version 148.0.7778.216 or later immediately.

Proactive Monitoring: Monitor browser-based traffic and endpoint security logs for unusual process spawns or unexpected crashes in the Chrome browser process.

Compensating Controls: Ensure that browser-based security policies are enforced via Group Policy or MDM to prevent the execution of untrusted scripts or the loading of malicious SVG content.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Use-after-free vulnerabilities in browser engines are complex but historically represent a primary target for exploit developers.

Analyst Recommendation

The high CVSS score reflects the potential for serious impact; organizations should prioritize patching all endpoints running Chrome. Immediate deployment of the provided update is critical to mitigate the risk of browser-based exploitation.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the PDFium library of Google Chrome could lead to memory corruption and potential code execution.

Executive Summary:
A use-after-free vulnerability in the PDFium component of Google Chrome exposes users to potential remote code execution via malicious PDF documents.

Vulnerability Details

CVE-ID: CVE-2026-10002

Affected Software: Google Chrome

Affected Versions: Google Chrome: 148.0.7778.216 up to (excluding) 148.0.7778.216

Vulnerability: This vulnerability involves a use-after-free (CWE-416) flaw in the PDFium library, which handles PDF rendering. An attacker can trigger this by tricking an unauthenticated user into opening a malicious PDF file.

Business Impact

Exploitation of this vulnerability allows an attacker to execute arbitrary code with the privileges of the browser, which can result in full system compromise. With a CVSS score of 8.8, the risk to confidentiality, integrity, and availability is high, necessitating urgent attention to prevent unauthorized access to sensitive business environments.

Remediation Plan

Immediate Action: Update Google Chrome to version 148.0.7778.216 or later to patch the PDFium library.

Proactive Monitoring: Review endpoint logs for anomalous file handling or browser process behavior initiated after opening PDF documents.

Compensating Controls: Utilize endpoint protection platforms that can scan incoming PDF attachments for malicious indicators before they are opened in the browser.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. PDF-based exploits are common, and users should exercise caution when opening unexpected documents.

Analyst Recommendation

Given the prevalence of PDF usage in business workflows, this vulnerability presents a significant attack surface. All systems must be updated to the latest version of Chrome to neutralize this risk immediately.

---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome on Windows prior to 148.0.7778.216
---END_METADATA---

Description Summary:
A use-after-free vulnerability in the Google Chrome Password manager allows for potential sandbox escapes.

Executive Summary:
A high-severity use-after-free vulnerability in Google Chrome on Windows could allow a remote attacker to achieve a sandbox escape through a crafted HTML page.

Vulnerability Details

CVE-ID: CVE-2026-10000

Affected Software: Google Chrome

Affected Versions: Google Chrome on Windows prior to 148.0.7778.216

Vulnerability: This use-after-free flaw exists in the password management component of Google Chrome. An unauthenticated attacker who has compromised the browser's renderer process can leverage this vulnerability to escape the sandbox environment.

Business Impact

With a CVSS score of 8.3, this vulnerability poses a significant risk to endpoint security. A successful sandbox escape allows an attacker to break out of the browser's security constraints, potentially leading to unauthorized access to the underlying operating system and user data.

Remediation Plan

Immediate Action: Update all instances of Google Chrome on Windows to version 148.0.7778.216 or later immediately.

Proactive Monitoring: Monitor endpoint security logs for signs of anomalous browser process crashes or unauthorized attempts to access system-level files from the browser process.

Compensating Controls: Utilize browser-based security policies or managed endpoint configurations to restrict user access to untrusted or malicious websites until patches are applied.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of June 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, the potential for sandbox escape makes it a high-risk target for sophisticated threat actors.

Analyst Recommendation

Security teams must prioritize updating Google Chrome to the latest version to mitigate the risk of sandbox escape. Regular browser maintenance is essential to maintain the integrity of the browser's security boundary and protect organizational endpoints.

Executive Summary:
A critical vulnerability has been identified in Crafty Controller, a popular server management tool. This flaw, tracked as CVE-2026-0963, allows an authenticated remote attacker to bypass security restrictions and gain full control over the underlying server, enabling them to tamper with files and execute malicious code. Due to its high severity (CVSS 9.9), immediate remediation is required to prevent a complete system compromise.

Vulnerability Details

CVE-ID: CVE-2026-0963

Affected Software: Crafty Controller

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is an input neutralization flaw, specifically a path traversal, within the File Operations API Endpoint. An authenticated attacker can send a specially crafted request to this API containing directory traversal sequences (e.g., ../). The application fails to properly sanitize this input, allowing the attacker to navigate outside of the intended directory and access, modify, or create files anywhere on the server's filesystem with the permissions of the Crafty Controller service account. This can be leveraged for remote code execution by overwriting application scripts, configuration files, or system executables.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.9. Successful exploitation could lead to a complete compromise of the server hosting Crafty Controller. The potential business impact is severe, including theft of sensitive data, deployment of ransomware, complete service disruption, and loss of system integrity. An attacker could use the compromised server as a pivot point to launch further attacks against the internal network, significantly expanding the scope of the breach and leading to substantial financial and reputational damage.

Remediation Plan

Immediate Action: Update Crafty Controller to the latest version as recommended by the vendor. After patching, it is crucial to review access logs and system files for any signs of compromise that may have occurred prior to the update.

Proactive Monitoring: Monitor application and web server logs for suspicious requests to the File Operations API endpoint, specifically looking for patterns indicative of path traversal such as ../, ..\\, and their URL-encoded variants. Implement file integrity monitoring (FIM) to alert on unexpected changes to critical system files or application directories. Monitor for unusual outbound network connections from the server, which could indicate a successful compromise.

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

• Deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block path traversal attempts.
• Restrict network access to the Crafty Controller management interface to only trusted IP addresses and administrative networks.
• Run the Crafty Controller service with the lowest possible user privileges to limit the impact of a potential code execution exploit.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of the publication date (Jan 30, 2026), there are no known public exploits or active exploitation campaigns targeting this vulnerability. However, given the critical severity and the relative simplicity of path traversal attacks, proof-of-concept exploits are likely to be developed and released quickly. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.

Analyst Recommendation

Given the critical CVSS score of 9.9, this vulnerability poses a direct and immediate threat to the confidentiality, integrity, and availability of affected systems. We strongly recommend that organizations identify all instances of Crafty Controller within their environment and apply the vendor-supplied patches without delay. If patching cannot be performed immediately, the compensating controls listed above should be implemented as a matter of urgency. Due to the high likelihood of future exploitation, this vulnerability should be prioritized at the highest level by all security and IT operations teams.