Type Confusion in V8 in Google Chrome prior to 149
Description
Type Confusion in V8 in Google Chrome prior to 149
AI Analyst Comment
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Search and filter 21553 vulnerabilities with AI analyst insights
Type Confusion in V8 in Google Chrome prior to 149
Type Confusion in V8 in Google Chrome prior to 149
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in UI in Google Chrome on Android prior to 149
Use after free in UI in Google Chrome on Android prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A use-after-free vulnerability exists in the UI component of Google Chrome for Android, potentially allowing remote code execution.
Executive Summary:
A critical use-after-free vulnerability in Google Chrome for Android poses a significant risk of arbitrary code execution for mobile device users.
Vulnerability Details
CVE-ID: CVE-2026-10932
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability is a use-after-free flaw located within the UI component of the browser. It typically requires an unauthenticated remote attacker to entice a user to visit a malicious webpage to trigger the memory corruption.
Business Impact
Successful exploitation of this flaw could allow an attacker to execute arbitrary code within the context of the browser, potentially leading to data theft, unauthorized access to user accounts, or full device compromise. With a CVSS score of 8.8, this vulnerability represents a high-severity risk to mobile enterprise security and user privacy.
Remediation Plan
Immediate Action: Update Google Chrome on all affected Android devices to version 149 or later immediately.
Proactive Monitoring: Monitor mobile device management (MDM) logs for outdated browser versions and anomalous application behavior.
Compensating Controls: Ensure Google Play Protect is enabled on all Android devices to provide an additional layer of defense against malicious web content.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Given the high CVSS score and the prevalence of mobile browsing in enterprise environments, this update should be prioritized. IT administrators must ensure that all managed Android devices receive the browser update to mitigate the risk of remote code execution.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Script injection in Headless in Google Chrome prior to 149
Script injection in Headless in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A script injection vulnerability in the Headless mode of Google Chrome could allow an attacker to execute unauthorized scripts.
Executive Summary:
A script injection vulnerability within the Headless mode of Google Chrome could enable an attacker to execute malicious code, threatening system integrity.
Vulnerability Details
CVE-ID: CVE-2026-10928
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a script injection vulnerability affecting the Headless mode functionality of Google Chrome. An unauthenticated attacker can leverage this to inject and execute arbitrary scripts, potentially manipulating browser automation tasks or exposing sensitive headless environment data.
Business Impact
Given the widespread use of headless browsers for automated testing and web scraping, this vulnerability could be leveraged to compromise automated workflows. With a CVSS score of 8.8, the impact includes unauthorized data access and the potential for persistent control over the automated environment.
Remediation Plan
Immediate Action: Upgrade Google Chrome to version 149 or later to patch the underlying script injection flaw.
Proactive Monitoring: Audit automated tasks and headless browser deployments for unusual script execution patterns or unexpected external connections.
Compensating Controls: Isolate automated browser environments from the internal network and limit the permissions of the service accounts running headless tasks.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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 relying on automated browser testing must prioritize this update, as headless environments are often overlooked during standard patching cycles. Updating to the latest version is the only effective way to neutralize this injection vulnerability.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Cast in Google Chrome prior to 149
Use after free in Cast in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Chrome prior to 149
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability in the Cast component of Google Chrome allows a remote, unauthenticated attacker to trigger memory corruption.
Executive Summary:
A critical Use-After-Free vulnerability in the Google Chrome Cast component poses a significant security threat that requires immediate remediation.
Vulnerability Details
CVE-ID: CVE-2026-10926
Affected Software: Google Chrome
Affected Versions: Chrome prior to 149
Vulnerability: This vulnerability is a Use-After-Free issue found in the Cast component, which handles casting media to external devices. An unauthenticated attacker can exploit this by forcing the browser to access memory that has already been deallocated, leading to potential code execution.
Business Impact
With a CVSS score of 8.8, this flaw represents a significant risk to the confidentiality and integrity of business systems. Successful exploitation could allow an attacker to gain control over the browser, potentially leading to unauthorized access to internal resources or sensitive user data.
Remediation Plan
Immediate Action: Update all instances of Google Chrome to version 149.0.7827.53/54 or later.
Proactive Monitoring: Monitor for unusual network traffic originating from the browser, particularly related to casting services or multimedia protocols.
Compensating Controls: Disable casting features via enterprise policy if not required for business operations to mitigate the attack surface.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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
Memory corruption vulnerabilities, particularly those affecting peripheral features like Cast, are common attack vectors. IT administrators must ensure the latest Chrome update is deployed across the environment to protect users from this potential exploit.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in WebAppInstalls in Google Chrome on Android prior to 149
Use after free in WebAppInstalls in Google Chrome on Android prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome on Android
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the WebAppInstalls component of Google Chrome on Android prior to version 149 may allow for arbitrary code execution.
Executive Summary:
A high-severity use-after-free flaw in Google Chrome on Android could allow attackers to execute arbitrary code via the WebAppInstalls component.
Vulnerability Details
CVE-ID: CVE-2026-10923
Affected Software: Google Chrome on Android
Affected Versions: See vendor advisory for affected versions
Vulnerability: This vulnerability involves a use-after-free condition within the WebAppInstalls feature of the browser. An attacker could potentially leverage this flaw to trigger memory corruption and execute arbitrary code on the host device.
Business Impact
The CVSS score of 8.8 reflects the high danger posed by this vulnerability to mobile endpoints. Compromise of mobile devices used for business can lead to the exposure of corporate email, multifactor authentication tokens, and internal application access, representing a significant risk to organizational mobility security.
Remediation Plan
Immediate Action: Update Google Chrome on all Android devices to version 149 or the latest available version via the Google Play Store.
Proactive Monitoring: Monitor mobile device management (MDM) platforms for devices running outdated browser versions and enforce compliance policies.
Compensating Controls: Utilize mobile application management (MAM) to sandbox corporate data and ensure that suspicious application behavior is identified and blocked.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 6, 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
Mobile device security must be maintained by ensuring the Chrome browser is updated to version 149 or higher on all Android endpoints. Administrators should use MDM tools to verify that the update is applied across the mobile fleet to prevent potential exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Insufficient validation of untrusted input in DevTools in Google Chrome prior to 149
Insufficient validation of untrusted input in DevTools in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome prior to 149.0.7827.53 on Linux, and prior to 149.0.7827.53/54 on Windows and macOS
---END_METADATA---
Description Summary:
Insufficient input validation in Google Chrome DevTools allows a remote attacker to bypass the Same Origin Policy via malicious network traffic after triggering specific UI gestures.
Executive Summary:
A security flaw in Google Chrome's DevTools could allow remote attackers to bypass the Same Origin Policy, potentially leading to unauthorized data access.
Vulnerability Details
CVE-ID: CVE-2026-10922
Affected Software: Google Chrome
Affected Versions: Google Chrome prior to 149.0.7827.53 on Linux, and prior to 149.0.7827.53/54 on Windows and macOS
Vulnerability: This vulnerability involves insufficient validation of untrusted input within the DevTools component. An unauthenticated attacker can exploit this by enticing a user to perform specific UI gestures, facilitating a cross-origin attack.
Business Impact
The CVSS score of 8.8 reflects the high risk posed by this Same Origin Policy (SOP) bypass. By circumventing SOP, attackers can potentially steal sensitive session tokens, cookies, or private user data from other web applications, leading to account takeover and significant privacy breaches.
Remediation Plan
Immediate Action: Update Google Chrome to version 149.0.7827.53 or 149.0.7827.53/54 to patch the validation logic in DevTools.
Proactive Monitoring: Review web traffic logs for signs of suspicious cross-origin requests or anomalous traffic patterns directed at sensitive internal web applications.
Compensating Controls: Utilize modern browser security headers (e.g., Content Security Policy) and ensure that users are educated on the risks of interacting with unfamiliar UI prompts or suspicious web content.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of June 6, 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
While this exploit requires specific user interaction, the potential for sensitive data exfiltration is substantial. Security teams should ensure the browser update is applied globally to mitigate the risk of SOP bypass attacks.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in ANGLE in Google Chrome on Windows prior to 149
Use after free in ANGLE in Google Chrome on Windows prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Chrome on Windows prior to 149
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability in the ANGLE component of Google Chrome on Windows potentially allows an unauthenticated attacker to cause memory corruption.
Executive Summary:
A high-severity Use-After-Free vulnerability in Chrome's ANGLE component on Windows requires immediate patching to prevent potential unauthorized code execution.
Vulnerability Details
CVE-ID: CVE-2026-10914
Affected Software: Google Chrome
Affected Versions: Chrome on Windows prior to 149
Vulnerability: This is a Use-After-Free vulnerability within the ANGLE graphics engine. An unauthenticated remote attacker could exploit this by convincing a user to navigate to a malicious webpage, leading to a state where the browser uses freed memory, resulting in a system crash or arbitrary code execution.
Business Impact
The CVSS score of 8.8 highlights the critical nature of this vulnerability. Organizations face risks of data compromise and unauthorized access if an attacker successfully exploits this flaw, as it allows for the subversion of the browser's security model.
Remediation Plan
Immediate Action: Update all Windows installations of Chrome to version 149.0.7827.53/54 or later.
Proactive Monitoring: Review endpoint telemetry for suspicious browser activity or attempts to utilize graphics-related APIs in an unusual manner.
Compensating Controls: Utilize Group Policy or MDM solutions to enforce browser security policies and ensure that all users are running the latest patched version.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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 prevalence of Chrome in enterprise environments, this vulnerability necessitates an urgent patching cycle. Security teams should ensure that all Windows workstations are updated to the latest version to eliminate this security gap.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in ANGLE in Google Chrome on Windows prior to 149
Use after free in ANGLE in Google Chrome on Windows prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Chrome on Windows prior to 149
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability in the ANGLE graphics abstraction layer of Google Chrome on Windows may allow for memory corruption.
Executive Summary:
A high-severity Use-After-Free vulnerability in the ANGLE component of Google Chrome for Windows presents a significant risk of arbitrary code execution.
Vulnerability Details
CVE-ID: CVE-2026-10913
Affected Software: Google Chrome
Affected Versions: Chrome on Windows prior to 149
Vulnerability: This vulnerability is a Use-After-Free flaw residing in the ANGLE (Almost Native Graphics Layer Engine) component. An unauthenticated attacker can exploit this memory management error through a specially crafted website to gain unauthorized control over the browser process.
Business Impact
With a CVSS score of 8.8, this flaw poses a severe risk to Windows-based endpoints. Successful exploitation could lead to full browser compromise, potentially allowing an attacker to bypass security boundaries and execute malicious payloads, resulting in significant business disruption and data loss.
Remediation Plan
Immediate Action: Upgrade Google Chrome on all Windows systems to version 149.0.7827.53/54 or later.
Proactive Monitoring: Monitor Windows Event Logs for recurring browser process crashes, which may indicate attempted exploitation of memory-related vulnerabilities.
Compensating Controls: Implement robust EDR (Endpoint Detection and Response) solutions that can identify and block memory-based exploitation techniques.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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 ANGLE engine is a critical graphics component, and flaws within it are high-value targets. Organizations should prioritize patching Chrome on all Windows assets immediately to prevent potential exploitation of this memory corruption vulnerability.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Type Confusion in V8 in Google Chrome prior to 149
Type Confusion in V8 in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A type confusion vulnerability in the V8 JavaScript engine of Google Chrome could allow an attacker to achieve arbitrary code execution.
Executive Summary:
A critical type confusion flaw in the V8 JavaScript engine of Google Chrome exposes users to potential remote code execution and system compromise.
Vulnerability Details
CVE-ID: CVE-2026-10910
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability is a type confusion flaw located in the V8 JavaScript engine. An unauthenticated attacker can exploit this by enticing a user to navigate to a malicious website, causing the engine to incorrectly interpret object types, thereby facilitating code execution.
Business Impact
The high CVSS score of 8.8 reflects the significant risk posed by this vulnerability, which allows attackers to bypass standard sandbox protections. Successful exploitation can lead to a full breach of the client workstation, resulting in loss of sensitive credentials or unauthorized access to corporate applications.
Remediation Plan
Immediate Action: Update all Google Chrome installations to version 149 or newer as soon as the patch is released.
Proactive Monitoring: Review web proxy and firewall logs for traffic directed toward suspicious or newly registered domains that may be hosting exploit kits.
Compensating Controls: Use browser-based security features such as "Enhanced Safe Browsing" and ensure that endpoint security software is configured to block known malicious script patterns.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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
V8 engine vulnerabilities are frequent targets for threat actors due to their high success rates in bypassing browser security. It is imperative to prioritize the deployment of the latest security updates to all managed endpoints to mitigate this severe risk.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Out of bounds write in ANGLE in Google Chrome prior to 149
Out of bounds write in ANGLE in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
An out-of-bounds write vulnerability exists in the ANGLE graphics engine of Google Chrome, which could allow an attacker to trigger memory corruption.
Executive Summary:
An out-of-bounds write flaw in Google Chrome's ANGLE component allows an attacker to cause memory corruption, potentially leading to arbitrary code execution.
Vulnerability Details
CVE-ID: CVE-2026-10907
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability involves an out-of-bounds write error within the ANGLE graphics library. An unauthenticated attacker can exploit this via malicious web content to bypass security controls and execute arbitrary code within the context of the browser process.
Business Impact
With a CVSS score of 8.8, this vulnerability poses a severe threat to organizational security. Exploitation could result in unauthorized code execution, leading to potential data exfiltration, the installation of persistent malware, or lateral movement within the local network.
Remediation Plan
Immediate Action: Apply the latest security updates provided by Google to update Chrome to version 149 or later.
Proactive Monitoring: Implement robust endpoint detection and response (EDR) solutions to identify and block suspicious browser-based process activities.
Compensating Controls: Restrict non-essential browser extensions and enforce strict content security policies to minimize the potential impact of web-based attacks.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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 high-impact exploitation, it is critical that IT administrators deploy the vendor-provided patches immediately. Failure to address this vulnerability increases the risk of successful remote code execution attacks against the organization’s endpoints.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Inappropriate implementation in V8 in Google Chrome prior to 149
Inappropriate implementation in V8 in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome prior to 149.0.7827.53 on Linux, and prior to 149.0.7827.53/54 on Windows and macOS
---END_METADATA---
Description Summary:
An inappropriate implementation vulnerability in the V8 engine of Google Chrome allows remote attackers to execute arbitrary code within the sandbox via a crafted HTML page.
Executive Summary:
A critical vulnerability in the Google Chrome V8 engine could allow a remote attacker to achieve arbitrary code execution on affected systems.
Vulnerability Details
CVE-ID: CVE-2026-10904
Affected Software: Google Chrome
Affected Versions: Google Chrome prior to 149.0.7827.53 on Linux, and prior to 149.0.7827.53/54 on Windows and macOS
Vulnerability: This is an implementation flaw within the V8 JavaScript engine. It is an unauthenticated, remote code execution vulnerability that can be triggered when a user visits a maliciously crafted HTML page.
Business Impact
With a CVSS score of 8.8, this vulnerability poses a significant risk to organizational security. Successful exploitation could lead to full system compromise, unauthorized data access, and potential lateral movement within the network, severely impacting confidentiality, integrity, and availability.
Remediation Plan
Immediate Action: Update all instances of Google Chrome to version 149.0.7827.53 (Linux) or 149.0.7827.53/54 (Windows/macOS) immediately.
Proactive Monitoring: Monitor network traffic for unusual outbound connections from browser processes and review system logs for signs of anomalous process execution.
Compensating Controls: Deploy endpoint protection platforms (EPP) configured to detect malicious script execution and ensure that browser sandboxing features remain enabled and enforced via Group Policy or MDM.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of June 6, 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 severity of this remote code execution flaw, organizations must prioritize the deployment of the Chrome 149 update across all managed endpoints. Failure to patch allows attackers a reliable vector to bypass browser security controls and execute arbitrary code.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in WebRTC in Google Chrome prior to 149
Use after free in WebRTC in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Chrome prior to 149
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability exists in the WebRTC component of Google Chrome, which could allow a remote attacker to achieve memory corruption.
Executive Summary:
A critical Use-After-Free flaw in Google Chrome’s WebRTC component exposes users to potential memory corruption and unauthorized code execution risks.
Vulnerability Details
CVE-ID: CVE-2026-10903
Affected Software: Google Chrome
Affected Versions: Chrome prior to 149
Vulnerability: This vulnerability involves a Use-After-Free condition within the WebRTC implementation, a protocol used for real-time communication. An unauthenticated attacker could trigger this flaw by enticing a user to visit a malicious site, resulting in memory corruption.
Business Impact
The CVSS score of 8.8 underscores the urgency of addressing this flaw. If exploited, an attacker could compromise the integrity of the browser session, leading to potential data exfiltration or the execution of arbitrary commands on the underlying host, jeopardizing sensitive corporate information.
Remediation Plan
Immediate Action: Apply the vendor-provided security update to Chrome version 149.0.7827.53/54 or later across the enterprise.
Proactive Monitoring: Review web proxy and firewall logs for traffic patterns indicative of attempts to reach malicious domains or suspicious WebRTC signaling activity.
Compensating Controls: Deploy browser isolation technologies or restrict browser extensions that are not essential for business operations to reduce the attack surface.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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
WebRTC vulnerabilities are frequently targeted due to their complexity and potential for remote code execution. It is imperative that IT security teams push the latest Chrome update to all workstations to mitigate the risk of exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Ozone in Google Chrome prior to 149
Use after free in Ozone in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Chrome prior to 149
---END_METADATA---
Description Summary:
A Use-After-Free (UAF) vulnerability exists in the Ozone component of Google Chrome, potentially allowing remote attackers to trigger memory corruption.
Executive Summary:
A high-severity Use-After-Free vulnerability in Google Chrome's Ozone component poses a significant risk of arbitrary code execution for unauthenticated users.
Vulnerability Details
CVE-ID: CVE-2026-10902
Affected Software: Google Chrome
Affected Versions: Chrome prior to 149
Vulnerability: This is a Use-After-Free vulnerability in the Ozone component, which manages graphics and windowing system abstraction. The flaw can be triggered by an unauthenticated remote attacker through a crafted webpage, leading to unpredictable application behavior or memory corruption.
Business Impact
With a CVSS score of 8.8, this vulnerability represents a significant threat to organizational security. Successful exploitation could allow an attacker to execute arbitrary code within the context of the browser, potentially leading to unauthorized system access, data theft, or the installation of malicious software on the host machine.
Remediation Plan
Immediate Action: Update all instances of Google Chrome to version 149.0.7827.53/54 or later immediately.
Proactive Monitoring: Monitor browser crash logs and endpoint security telemetry for anomalous process behavior or unexpected memory access patterns.
Compensating Controls: Utilize endpoint protection platforms (EPP) with exploit prevention features and ensure browser security settings are configured to restrict high-risk script execution where possible.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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 severity of Use-After-Free vulnerabilities in browser environments, administrators must prioritize the deployment of the Chrome 149 update. Failure to patch allows a window of opportunity for attackers to leverage this memory corruption flaw for unauthorized system interaction.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Inappropriate implementation in GPU in Google Chrome prior to 149
Inappropriate implementation in GPU in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: prior to 149.0.7827.53
---END_METADATA---
Description Summary:
An inappropriate implementation in the GPU component of Google Chrome allows a remote, unauthenticated attacker to potentially perform a sandbox escape via a crafted HTML page.
Executive Summary:
A critical-severity GPU implementation flaw in Google Chrome permits sandbox escapes, potentially leading to full device compromise.
Vulnerability Details
CVE-ID: CVE-2026-10897
Affected Software: Google Chrome
Affected Versions: prior to 149.0.7827.53
Vulnerability: This vulnerability involves an inappropriate implementation within the GPU process. An unauthenticated remote attacker can leverage a crafted HTML page to trigger this flaw, resulting in a sandbox escape and the potential for arbitrary code execution.
Business Impact
With a CVSS score of 8.8, this vulnerability is classified as critical by Chromium security. A sandbox escape provides an attacker with a pathway to execute code outside the browser's security model, which could lead to unauthorized access to the underlying system, data theft, and persistent malware infection.
Remediation Plan
Immediate Action: Update all installations of Google Chrome to version 149.0.7827.53 or later to remediate the GPU implementation flaw.
Proactive Monitoring: Monitor system logs for signs of abnormal GPU process activity or unexpected browser behavior that may indicate an attempt to exploit the sandbox.
Compensating Controls: Use hardware-level security features and browser sandboxing settings to mitigate the potential impact of an escape, while prioritizing the immediate deployment of the software patch.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 6, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
This vulnerability represents a significant risk to the integrity of the host system. It is vital that organizations expedite the patching process for all Chrome deployments to ensure that the browser's sandbox remains an effective security barrier against remote attackers.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Chrome for iOS in Google Chrome on iOS prior to 149
Use after free in Chrome for iOS in Google Chrome on iOS prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability exists in the Chrome for iOS application, potentially allowing for arbitrary code execution.
Executive Summary:
A critical Use-After-Free vulnerability in Chrome for iOS poses a significant risk of remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-10896
Affected Software: Google Chrome (iOS)
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability is a memory corruption flaw (Use-After-Free) specific to the Chrome browser application on the iOS platform. An unauthenticated attacker can exploit this by directing a user to a malicious webpage, leading to unauthorized code execution.
Business Impact
With a CVSS score of 8.8, this vulnerability poses a high risk to mobile device security within the enterprise. Successful exploitation could lead to the exposure of personal or corporate data stored on the mobile device and potentially grant an attacker a foothold into the mobile ecosystem.
Remediation Plan
Immediate Action: Update the Google Chrome application on all iOS devices to version 149 or later via the Apple App Store.
Proactive Monitoring: Use Mobile Device Management (MDM) solutions to track and enforce compliance with the latest application versions.
Compensating Controls: Ensure iOS system updates are current to utilize the latest underlying OS security features, which provide additional layers of defense against application-level exploits.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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
Mobile security is critical, and users should ensure their iOS browsers are updated promptly. Administrators should utilize MDM policies to mandate the update to version 149 or later, effectively mitigating the risk of memory corruption and potential device compromise.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Ozone in Google Chrome prior to 149
Use after free in Ozone in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability exists in the Ozone windowing system component of Google Chrome, potentially allowing for arbitrary code execution.
Executive Summary:
A critical Use-After-Free vulnerability in Google Chrome’s Ozone component poses a significant risk of remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-10895
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a memory corruption issue stemming from a Use-After-Free error within the Ozone component. An unauthenticated remote attacker can exploit this by enticing a user to visit a malicious website to execute arbitrary code.
Business Impact
The CVSS score of 8.8 indicates a high risk to organizational security, as successful exploitation results in the execution of code at the user's privilege level. This can lead to persistent access, sensitive data exfiltration, or the installation of malicious software, undermining the integrity of the computing environment.
Remediation Plan
Immediate Action: Upgrade Google Chrome to version 149 or later across all managed endpoints to resolve the vulnerability.
Proactive Monitoring: Monitor for unexpected browser behavior or network connections from browser processes that may indicate an active exploit attempt.
Compensating Controls: Implement browser-based security policies that restrict the execution of untrusted scripts or plugins on high-risk websites.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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 must prioritize this update as part of their standard patching cycle to avoid exposure to memory-based exploits. Updating to the latest stable release of Google Chrome is the recommended course of action to ensure robust protection against this vulnerability.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Chromoting in Google Chrome prior to 149
Use after free in Chromoting in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---
Description Summary:
A use-after-free vulnerability exists in the Chromoting component of Google Chrome prior to version 149, which could lead to arbitrary code execution.
Executive Summary:
A high-severity use-after-free vulnerability in Google Chrome's Chromoting component poses a significant risk of arbitrary code execution for affected users.
Vulnerability Details
CVE-ID: CVE-2026-10893
Affected Software: Google Chrome
Affected Versions: See vendor advisory for affected versions
Vulnerability: The vulnerability is a use-after-free flaw within the Chromoting component. This allows an attacker to potentially trigger memory corruption, leading to a crash or the execution of arbitrary code if a user is lured into interacting with malicious content.
Business Impact
With a CVSS score of 8.8, this vulnerability presents a substantial risk to organizational security, as browser-based exploits are common vectors for initial access. Successful exploitation could result in full user-level code execution, potentially leading to the compromise of sensitive credentials, local data, or internal network access.
Remediation Plan
Immediate Action: Update all Google Chrome instances to version 149 or the latest available security release provided by the vendor.
Proactive Monitoring: Monitor endpoint logs for suspicious browser behavior, abnormal crash reports, or unexpected process execution patterns originating from Chrome.
Compensating Controls: Deploy endpoint protection platforms (EPP) and ensure browser-based security policies are configured to restrict script execution where possible.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 6, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of use-after-free flaws in widely used browsers, the potential for exploitation is high.
Analyst Recommendation
Security teams must mandate the update of all Chrome browser instances to version 149 or higher across the enterprise. Timely patching is essential to mitigate the risk of memory corruption-based attacks targeting the browser's remote desktop capabilities.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in GFX in Google Chrome on Linux prior to 149
Use after free in GFX in Google Chrome on Linux prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability exists in the GFX component of Google Chrome on Linux, potentially allowing for arbitrary code execution.
Executive Summary:
A critical Use-After-Free vulnerability in Google Chrome’s GFX component on Linux poses a significant risk of remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-10891
Affected Software: Google Chrome (Linux)
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability involves memory corruption in the GFX (Graphics) subsystem due to a Use-After-Free error. An unauthenticated attacker can exploit this flaw through a specially crafted webpage to execute arbitrary code on the host system.
Business Impact
The CVSS score of 8.8 reflects the high potential for an attacker to gain control over the underlying operating system on Linux-based workstations. This could lead to a full breach of the affected device, resulting in data theft, unauthorized access to internal resources, and potential lateral movement within the network.
Remediation Plan
Immediate Action: Update Google Chrome on all Linux distributions to version 149 or later immediately.
Proactive Monitoring: Audit Linux workstation logs for anomalous system calls or crashes originating from the Chrome browser process.
Compensating Controls: Utilize SELinux or AppArmor profiles to restrict the browser process's access to sensitive system files and resources, limiting the impact of a successful exploit.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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 prevalence of Chrome in Linux environments, users and administrators must prioritize this update. Applying the vendor patch for version 149 is essential to mitigate the risk of arbitrary code execution and maintain the security posture of Linux-based endpoints.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Cast in Google Chrome prior to 149
Use after free in Cast in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability exists in the Cast component of Google Chrome, which may allow an attacker to execute arbitrary code.
Executive Summary:
A critical Use-After-Free vulnerability in Google Chrome’s Cast component poses a significant risk of remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-10890
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a memory corruption vulnerability involving a Use-After-Free condition in the Cast framework. An unauthenticated attacker could exploit this by enticing a user to navigate to a malicious site, resulting in arbitrary code execution.
Business Impact
With a CVSS score of 8.8, this vulnerability represents a high-severity threat that could facilitate unauthorized access to local machine resources. Successful exploitation could compromise user sessions, expose internal network information, or serve as a delivery mechanism for further malware propagation.
Remediation Plan
Immediate Action: Update all Google Chrome browser instances to version 149 or later as soon as patches become available.
Proactive Monitoring: Review web filtering and proxy logs for traffic directed toward unknown or high-risk domains that might be hosting exploit payloads.
Compensating Controls: Deploy endpoint protection solutions that can detect and block memory manipulation or abnormal process behavior common in browser exploits.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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. Promptly updating to the latest version of Google Chrome is the most effective way to eliminate this memory corruption flaw and protect organizational endpoints from potential remote exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Cast Streaming in Google Chrome prior to 149
Use after free in Cast Streaming in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A Use-After-Free vulnerability exists in the Cast Streaming component of Google Chrome, potentially allowing for arbitrary code execution.
Executive Summary:
A critical Use-After-Free vulnerability in Google Chrome’s Cast Streaming component poses a significant risk of remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-10888
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a memory corruption vulnerability categorized as a Use-After-Free within the Cast Streaming function. An unauthenticated remote attacker can trigger this flaw via a crafted webpage to gain unauthorized code execution.
Business Impact
The exploitation of this vulnerability could lead to total system compromise, allowing an attacker to execute arbitrary code within the context of the browser process. Given the high CVSS score of 8.8, this presents a severe risk to organizational confidentiality and integrity, potentially enabling the exfiltration of sensitive user data or credentials.
Remediation Plan
Immediate Action: Update all instances of Google Chrome to version 149 or later immediately.
Proactive Monitoring: Monitor endpoint logs for suspicious browser process crashes or unusual memory usage patterns that may indicate exploitation attempts.
Compensating Controls: Ensure that browser-based security features, such as site isolation and sandboxing, are enabled and enforced via group policy.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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 Use-After-Free vulnerability necessitates an immediate response. Organizations should prioritize patching all Chrome installations to version 149 or higher to mitigate the risk of remote code execution and potential system takeover.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Chrome for iOS in Google Chrome on iOS prior to 149
Use after free in Chrome for iOS in Google Chrome on iOS prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome for iOS
AFFECTED_VERSIONS: Google Chrome on iOS prior to 149.0.7827.45
---END_METADATA---
Description Summary:
A use-after-free vulnerability in Chrome for iOS allows potential remote code execution.
Executive Summary:
A high-severity use-after-free vulnerability in Chrome for iOS poses a significant risk of remote code execution, requiring an immediate update to the latest version.
Vulnerability Details
CVE-ID: CVE-2026-10885
Affected Software: Google Chrome for iOS
Affected Versions: Google Chrome on iOS prior to 149.0.7827.45.
Vulnerability: This is a use-after-free vulnerability in Chrome for iOS. An attacker could potentially exploit this memory corruption issue to execute arbitrary code or cause a crash during the processing of network-related tasks.
Business Impact
With a CVSS score of 8.8, this vulnerability presents a high risk to mobile device users. Successful exploitation could lead to data theft or loss of device integrity. Given that Google is aware of exploits for similar vulnerabilities in the wild, the risk of targetted attacks is significant.
Remediation Plan
Immediate Action: Update the Google Chrome application on all iOS devices to version 149.0.7827.45 via the App Store.
Proactive Monitoring: Encourage users to enable automatic app updates and monitor for any abnormal behavior in mobile browser sessions.
Compensating Controls: Utilize Mobile Device Management (MDM) solutions to enforce version compliance and restrict access to sensitive applications until the browser is patched.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of Jun 5, 2026, there is no public information indicating active exploitation of this specific vulnerability. However, Google is aware of exploits for similar CVEs (e.g., CVE-2026-3909 & CVE-2026-3910) existing in the wild, necessitating rapid remediation.
Analyst Recommendation
Mobile browsers remain prime targets for exploitation. Organizations should ensure that all managed iOS devices are updated to the latest version of Chrome to mitigate this memory corruption threat. Prompt patching is essential to maintain the security posture of mobile endpoints.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Type Confusion in ANGLE in Google Chrome prior to 149
Type Confusion in ANGLE in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A type confusion vulnerability exists in the ANGLE graphics engine component of Google Chrome, potentially allowing for arbitrary code execution.
Executive Summary:
A type confusion vulnerability in Google Chrome's ANGLE component poses a high risk of remote code execution if exploited by an attacker.
Vulnerability Details
CVE-ID: CVE-2026-10883
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a type confusion vulnerability residing within the ANGLE (Almost Native Graphics Layer Engine) component. The flaw can be triggered by a remote, unauthenticated attacker via a specially crafted web page, leading to potential memory corruption or arbitrary code execution.
Business Impact
Successful exploitation of this vulnerability could lead to a complete compromise of the browser session and the underlying host system. Given the CVSS score of 8.8, this flaw represents a significant risk to data confidentiality, integrity, and availability, potentially facilitating unauthorized access to sensitive user data or internal network resources.
Remediation Plan
Immediate Action: Update Google Chrome to the latest stable release (version 149 or later) as soon as it is available from the vendor.
Proactive Monitoring: Monitor endpoint logs for abnormal browser process behavior, such as unexpected crashes or unauthorized memory access attempts.
Compensating Controls: Ensure that browser security settings are strictly enforced via Group Policy or MDM, and consider utilizing an endpoint protection platform (EPP) to detect malicious process execution.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
The severity of this vulnerability necessitates immediate attention to prevent potential exploitation. Organizations should prioritize patching all instances of Google Chrome across their environment to version 149 or higher to eliminate this high-risk attack vector.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Network in Google Chrome prior to 149
Use after free in Network in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Google Chrome prior to 149.0.7827.53/54 (Windows/Mac) and 149.0.7827.53 (Linux)
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the Network component of Google Chrome allows for potential remote code execution.
Executive Summary:
A high-severity use-after-free vulnerability in Google Chrome’s Network component poses a significant risk of remote code execution, especially given observed exploitation of similar flaws.
Vulnerability Details
CVE-ID: CVE-2026-10882
Affected Software: Google Chrome
Affected Versions: Google Chrome prior to 149.0.7827.53/54 (Windows/Mac) and 149.0.7827.53 (Linux).
Vulnerability: This is a use-after-free memory corruption vulnerability within the Network component of Google Chrome. Exploiting this issue could allow an attacker to trigger a crash or execute arbitrary code in the context of the browser process.
Business Impact
With a CVSS score of 8.8, this vulnerability is a high-priority threat. Successful exploitation could lead to complete system compromise if the browser process is successfully escaped, or result in the theft of sensitive session data. The existence of exploits for related vulnerabilities elevates the urgency of this patch.
Remediation Plan
Immediate Action: Update Google Chrome to version 149.0.7827.53/54 (Windows/Mac) or 149.0.7827.53 (Linux) immediately.
Proactive Monitoring: Ensure that automated browser update policies are enforced across the enterprise and review endpoint logs for unexpected browser crashes.
Compensating Controls: Employ endpoint protection solutions that detect memory corruption patterns and restrict browser process capabilities via sandboxing or group policies.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of Jun 5, 2026, there is no public information indicating active exploitation of this specific vulnerability. However, Google is aware of exploits for similar CVEs (e.g., CVE-2026-3909 & CVE-2026-3910) existing in the wild, necessitating rapid remediation.
Analyst Recommendation
Given the prevalence of use-after-free vulnerabilities in browser environments and the observed activity regarding similar flaws, this update should be treated as a high-priority task. Ensure all workstations and servers running Chrome are updated to the latest stable release to mitigate the risk of exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A SQL injection vulnerability in the OSNexus QuantaStor SDS Manager login endpoint allows unauthenticated attackers to bypass authentication.
A SQL injection vulnerability in the OSNexus QuantaStor SDS Manager login endpoint allows unauthenticated attackers to bypass authentication.
---METADATA---
VENDOR: OSNexus
PRODUCT: QuantaStor SDS Manager
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---
Description Summary:
A SQL injection vulnerability in the OSNexus QuantaStor SDS Manager login endpoint allows unauthenticated attackers to bypass authentication.
Executive Summary:
OSNexus QuantaStor SDS Manager contains a critical SQL injection vulnerability that allows unauthenticated attackers to bypass authentication and gain administrative access.
Vulnerability Details
CVE-ID: CVE-2026-10880
Affected Software: OSNexus QuantaStor SDS Manager
Affected Versions: See vendor advisory
Vulnerability: The username field in the login endpoint lacks proper sanitization, allowing an unauthenticated remote attacker to inject SQL commands and bypass password requirements to log in as an administrator.
Business Impact
With a CVSS score of 9.8, this flaw allows for full administrative compromise of the storage management interface. This could result in unauthorized access to stored data, configuration changes, or the complete destruction of storage volumes, severely impacting business continuity and data integrity.
Remediation Plan
Immediate Action: Apply the latest security updates provided by OSNexus to patch the login endpoint.
Proactive Monitoring: Monitor server logs for suspicious database query strings or multiple failed login attempts followed by successful administrative sessions.
Compensating Controls: Implement a Web Application Firewall (WAF) to detect and block common SQL injection patterns targeting the management interface.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of Jun 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
This vulnerability is critical because it provides an unauthenticated path to administrative privileges. Administrators should ensure the QuantaStor SDS Manager is fully patched and shielded from direct public exposure until updates are successfully applied.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
The hawkBit device management client in subsys/mgmt/hawkbit accumulates the body of an HTTP response from the update server into a heap buffer in resp...
The hawkBit device management client in subsys/mgmt/hawkbit accumulates the body of an HTTP response from the update server into a heap buffer in response_json_cb() (subsys/mgmt/hawkbit/hawkbit
---METADATA---
VENDOR: Zephyr Project
PRODUCT: Zephyr
AFFECTED_VERSIONS: 2.4.0 up to (excluding) 4.5.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A heap-based buffer overflow vulnerability in the Zephyr RTOS hawkBit device management client allows for potential memory corruption during HTTP response processing.
Executive Summary:
A high-severity heap buffer overflow in the Zephyr hawkBit client could allow remote attackers to cause system crashes or potentially execute arbitrary code.
Vulnerability Details
CVE-ID: CVE-2026-10849
Affected Software: Zephyr Project Zephyr
Affected Versions: 2.4.0 up to (excluding) 4.5.0
Vulnerability: The hawkBit client fails to safely handle HTTP response bodies within the response_json_cb function, leading to a heap-based buffer overflow (CWE-122, CWE-787). This vulnerability can be triggered by a remote, unauthenticated attacker sending a specially crafted HTTP response to the device.
Business Impact
With a CVSS score of 8.2, this vulnerability represents a significant threat to device stability and security. Exploitation could lead to persistent denial of service or remote code execution on connected IoT devices, potentially compromising the integrity of managed fleets and enabling unauthorized control over embedded systems.
Remediation Plan
Immediate Action: Update the Zephyr RTOS codebase to version 4.5.0 or later to apply the necessary bounds checking for heap allocations.
Proactive Monitoring: Monitor network traffic directed toward the hawkBit client for unusually large or malformed HTTP JSON payloads.
Compensating Controls: Deploy network-level traffic inspection or a firewall to filter and validate incoming traffic from external update servers to the hawkBit management interface.
Exploitation Status
Public Exploit Available: Unknown.
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 flaw is technically significant as it resides in a core component of the device management subsystem.
Analyst Recommendation
Given the critical role of the hawkBit client in device management, this update must be treated as a high priority. Organizations utilizing Zephyr RTOS should verify their version and apply the patch to prevent potential remote exploitation of their device fleet.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The OCPP 1
The OCPP 1
---METADATA---
VENDOR: Zephyr Project
PRODUCT: Zephyr RTOS
AFFECTED_VERSIONS: 4.3.0 up to (excluding) 4.5.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A memory bounds error in the OCPP 1 implementation within Zephyr RTOS allows for potential out-of-bounds read or write operations, which may lead to system instability or service disruption.
Executive Summary:
A memory corruption vulnerability in Zephyr RTOS versions 4.3.0 through 4.4.9 poses a significant risk of denial-of-service or unauthorized data access.
Vulnerability Details
CVE-ID: CVE-2026-10848
Affected Software: Zephyr Project Zephyr RTOS
Affected Versions: 4.3.0 up to (excluding) 4.5.0
Vulnerability: This vulnerability involves out-of-bounds read and write flaws (CWE-125 and CWE-787) within the OCPP 1 stack. The attack vector is network-based and does not require user interaction or prior authentication to trigger.
Business Impact
Successful exploitation of these memory bounds errors can lead to a crash of the affected device or the potential for arbitrary code execution. Given the CVSS score of 7.0, this represents a high-severity risk that could cause critical system downtime in industrial or IoT environments relying on the Zephyr RTOS.
Remediation Plan
Immediate Action: Upgrade to Zephyr RTOS version 4.5.0 or later to incorporate the necessary memory safety fixes.
Proactive Monitoring: Review network traffic and system logs for unexpected behavior or crash events originating from the OCPP interface.
Compensating Controls: Implement network segmentation to restrict access to devices running the affected OCPP service, thereby limiting the exposure to untrusted network segments.
Exploitation Status
Public Exploit Available: No — there is no confirmed public exploit available in the current data.
Analyst Notes: As of August 3, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's reliance on memory management errors makes it a target for stability-focused attacks, but the requirement for specific network conditions may limit immediate, widespread exploitation.
Analyst Recommendation
Organizations utilizing the Zephyr RTOS should prioritize the migration to version 4.5.0 to address these critical memory bounds vulnerabilities. Given the potential for service disruption, testing and deployment of this patch should be scheduled immediately to ensure the integrity and availability of embedded systems.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
IBM WebSphere Application Server 8
IBM WebSphere Application Server 8
---METADATA---
VENDOR: IBM
PRODUCT: WebSphere Application Server
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A security vulnerability has been identified in IBM WebSphere Application Server 8. Further details regarding the specific nature of the flaw remain under investigation.
Executive Summary:
IBM WebSphere Application Server 8 is subject to a high-severity vulnerability that requires immediate administrative attention to mitigate potential system compromise.
Vulnerability Details
CVE-ID: CVE-2026-10845
Affected Software: IBM WebSphere Application Server
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability affects IBM WebSphere Application Server 8. Due to the limited technical disclosure, the specific attack vector and authentication requirements are currently being evaluated by the vendor.
Business Impact
With a CVSS score of 7.3, this vulnerability represents a significant risk to organizational infrastructure. Successful exploitation could lead to unauthorized system access, potential data exfiltration, or service disruption, directly impacting the availability and integrity of mission-critical business applications hosted on the platform.
Remediation Plan
Immediate Action: Prioritize reviewing the official IBM security bulletin and apply the relevant security patches or configuration updates as soon as they are released.
Proactive Monitoring: Inspect application server logs for anomalous administrative activity or unauthorized request patterns that deviate from established baselines.
Compensating Controls: Implement strict network segmentation and ensure that the management interface for WebSphere is not exposed to untrusted networks or the public internet.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 23, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Given the critical role WebSphere plays in enterprise environments, administrators must remain vigilant. Monitor IBM’s security portal daily for patches and prioritize the deployment of all recommended updates to prevent potential exploitation of this high-severity flaw.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The AllCoach WordPress plugin before 1
The AllCoach WordPress plugin before 1
---METADATA---
VENDOR: WordPress
PRODUCT: AllCoach
AFFECTED_VERSIONS: 0 up to 1.0.2
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
An improper privilege management vulnerability in the AllCoach WordPress plugin allows authenticated users with lower privileges to perform unauthorized actions.
Executive Summary:
A high-severity privilege management vulnerability in the AllCoach WordPress plugin allows attackers to escalate privileges and potentially achieve full system control.
Vulnerability Details
CVE-ID: CVE-2026-10830
Affected Software: WordPress AllCoach Plugin
Affected Versions: 0 up to 1.0.2
Vulnerability: The plugin suffers from Improper Privilege Management (CWE-269), where it fails to properly validate the capabilities of the requesting user. This allows an authenticated user to perform actions beyond their assigned access level, potentially leading to total system compromise.
Business Impact
The CVSS score of 8.8 reflects the high risk of unauthorized administrative actions. If exploited, an attacker could gain full control over the WordPress site, modify content, inject malicious code, or access sensitive user data, leading to severe reputational and operational damage.
Remediation Plan
Immediate Action: Update the AllCoach plugin to the latest version (1.0.2 or higher) or remove the plugin if it is no longer required for business operations.
Proactive Monitoring: Review WordPress user roles and permissions, and monitor the audit logs for suspicious administrative actions performed by low-privileged accounts.
Compensating Controls: Utilize a Web Application Firewall (WAF) to detect and block common privilege escalation patterns and unauthorized request attempts against the plugin's endpoints.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of July 7, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Privilege management flaws are critical in CMS environments. Site administrators should immediately update the AllCoach plugin and perform a security audit of all user accounts to ensure no unauthorized elevation of privileges has taken place.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The WPForms Pro plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1
The WPForms Pro plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1
---METADATA---
VENDOR: WordPress
PRODUCT: WPForms Pro
AFFECTED_VERSIONS: 0 through 1.10.1.1
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The WPForms Pro plugin for WordPress is vulnerable to an arbitrary file upload flaw, allowing unauthenticated attackers to upload malicious files to the server.
Executive Summary:
A critical arbitrary file upload vulnerability in the WPForms Pro plugin for WordPress allows unauthenticated attackers to achieve remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-10818
Affected Software: WordPress WPForms Pro
Affected Versions: 0 through 1.10.1.1
Vulnerability: This vulnerability is an unrestricted file upload flaw (CWE-434). It allows an unauthenticated attacker to bypass security controls and upload malicious payloads, which could lead to full site compromise.
Business Impact
Successful exploitation allows an attacker to execute arbitrary code on the underlying server. This poses a severe risk to data confidentiality, integrity, and availability, potentially leading to total site takeover and the exfiltration of sensitive customer or administrative data. Given the CVSS score of 8.1, this represents a high-severity risk that requires immediate attention.
Remediation Plan
Immediate Action: Update the WPForms Pro plugin to version 2.0.0 or later immediately to apply the patch.
Proactive Monitoring: Monitor server access logs for suspicious file upload activity or requests targeting plugin directories.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block unauthorized file uploads and execution of scripts in upload directories.
Exploitation Status
Public Exploit Available: No confirmed public exploit exists in our curated sources.
Analyst Notes: As of July 25, 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 lack of authentication required to trigger the upload mechanism.
Analyst Recommendation
The severity of this flaw necessitates immediate action. Administrators must prioritize updating the WPForms Pro plugin to the latest version to prevent potential remote code execution and full site compromise.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
A critical flaw in the Autodesk Fusion MCP extension allows arbitrary code execution when a user visits a maliciously crafted webpage.
A critical flaw in the Autodesk Fusion MCP extension allows arbitrary code execution when a user visits a maliciously crafted webpage.
---METADATA---
VENDOR: Autodesk
PRODUCT: Fusion
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---
Description Summary:
A critical flaw in the Autodesk Fusion MCP extension allows arbitrary code execution when a user visits a maliciously crafted webpage.
Executive Summary:
A critical vulnerability in the Autodesk Fusion MCP extension enables unauthenticated remote attackers to achieve arbitrary code execution on the host machine.
Vulnerability Details
CVE-ID: CVE-2026-10789
Affected Software: Autodesk Fusion
Affected Versions: See vendor advisory
Vulnerability: This vulnerability resides in the MCP extension of Autodesk Fusion. It allows an unauthenticated attacker to execute arbitrary code with the privileges of the logged-in user by enticing them to visit a malicious webpage.
Business Impact
With a CVSS score of 9.6, this vulnerability poses a severe risk to organizational security. Successful exploitation could lead to full system compromise, unauthorized data exfiltration, or the deployment of ransomware, resulting in significant operational downtime and potential loss of intellectual property.
Remediation Plan
Immediate Action: Update Autodesk Fusion to the latest version provided by the vendor immediately to patch the MCP extension.
Proactive Monitoring: Monitor endpoint activity for unauthorized process launches or abnormal network connections originating from the Fusion application.
Compensating Controls: Implement browser-based security controls or network filtering to block access to known malicious domains and minimize the risk of users navigating to untrusted sites.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of Jun 22, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Given the critical nature of this remote code execution flaw, organizations must prioritize patching all instances of Autodesk Fusion. Administrators should ensure that all endpoints are updated to the latest version to prevent potential exploitation.
Update Autodesk Fusion to the latest version. Check the vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
A missing authorization vulnerability in the Drupal LocalGov Workflows module allows unauthorized users to access restricted resources via forceful br...
A missing authorization vulnerability in the Drupal LocalGov Workflows module allows unauthorized users to access restricted resources via forceful browsing.
---METADATA---
VENDOR: Drupal
PRODUCT: LocalGov Workflows
AFFECTED_VERSIONS: 0.0.0 to 1.6.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A missing authorization vulnerability in the Drupal LocalGov Workflows module allows unauthorized users to access restricted resources via forceful browsing.
Executive Summary:
The Drupal LocalGov Workflows module is susceptible to a critical missing authorization flaw that allows unauthenticated attackers to bypass access controls.
Vulnerability Details
CVE-ID: CVE-2026-10768
Affected Software: Drupal LocalGov Workflows
Affected Versions: 0.0.0 to 1.6.0
Vulnerability: This vulnerability is caused by missing authorization checks, which permits unauthenticated attackers to perform forceful browsing. This allows access to sensitive workflow data or administrative functions that should be restricted.
Business Impact
With a CVSS score of 9.8, this vulnerability represents a critical risk to data confidentiality and integrity. Successful exploitation could allow an attacker to view or modify sensitive administrative workflows, potentially leading to unauthorized data exposure or complete compromise of the application's workflow management system.
Remediation Plan
Immediate Action: Update the Drupal LocalGov Workflows module to version 1.6.0 or later immediately to apply the necessary authorization checks.
Proactive Monitoring: Monitor application access logs for unexpected attempts to access administrative paths or workflow-related objects by unprivileged users.
Compensating Controls: Implement strict access control lists at the web server or WAF level to restrict access to sensitive module paths until the update is applied.
Exploitation Status
Public Exploit Available: No (unknown)
Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous because it requires no authentication to reach the vulnerable code.
Analyst Recommendation
This vulnerability is highly critical and should be treated with the utmost urgency. Administrators must prioritize updating to version 1.6.0 or later to ensure that proper authorization logic is enforced and to prevent unauthorized access to sensitive system resources.
Update Drupal LocalGov Workflows to the latest version. Monitor for exploitation attempts and review access logs.
Pega Platform versions 8
Pega Platform versions 8
---METADATA---
VENDOR: Pegasystems
PRODUCT: Pega Infinity
AFFECTED_VERSIONS: 8.5.0 up to (excluding) Infinity 25.1.3
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
Pega Infinity is affected by an improper verification of cryptographic signatures vulnerability, which allows authenticated attackers to potentially compromise data integrity and confidentiality.
Executive Summary:
A cryptographic signature verification flaw in Pega Infinity allows authenticated attackers to compromise system data, necessitating an immediate software update.
Vulnerability Details
CVE-ID: CVE-2026-10754
Affected Software: Pegasystems Pega Infinity
Affected Versions: 8.5.0 up to (excluding) Infinity 25.1.3
Vulnerability: This vulnerability, identified as CWE-347, involves the improper verification of cryptographic signatures. It requires an authenticated user to exploit the flaw, as indicated by the PR:L (Privileges Required: Low) vector.
Business Impact
Successful exploitation allows an attacker with low-level privileges to bypass signature checks, which can lead to unauthorized data modification or access. With a CVSS score of 8.6, this vulnerability poses a significant risk to the integrity of business operations and the confidentiality of stored information within the Pega environment.
Remediation Plan
Immediate Action: Upgrade Pega Infinity to version 25.1.3 or higher as specified in the vendor security advisory.
Proactive Monitoring: Monitor system access logs for unusual patterns involving administrative or sensitive data functions that rely on cryptographic verification.
Compensating Controls: Ensure that strict internal network segmentation and robust identity management policies are enforced to limit the potential impact of authenticated users.
Exploitation Status
Public Exploit Available: No (exploit_available: false)
Analyst Notes: As of August 11, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's requirement for authentication limits the attack surface to existing platform users.
Analyst Recommendation
Given the high severity of this vulnerability, administrators should prioritize the application of the vendor-provided security patches. Updating to the latest version of Pega Infinity is the only reliable method to eliminate the risk associated with this cryptographic implementation error.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Improper output neutralization for logs vulnerability in upKeeper Solutions upKeeper Instant Privilege Access on Windows allows Log Injection-Tamperin...
Improper output neutralization for logs vulnerability in upKeeper Solutions upKeeper Instant Privilege Access on Windows allows Log Injection-Tampering-Forging
---METADATA---
VENDOR: upKeeper Solutions
PRODUCT: Instant Privilege Access
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
An improper output neutralization flaw in upKeeper Instant Privilege Access allows for log injection, tampering, or forging by an attacker.
Executive Summary:
UpKeeper Instant Privilege Access contains a log injection vulnerability that could allow attackers to manipulate audit trails and compromise the integrity of security monitoring.
Vulnerability Details
CVE-ID: CVE-2026-10745
Affected Software: upKeeper Solutions Instant Privilege Access
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a log injection vulnerability resulting from improper neutralization of output. This flaw allows an attacker to manipulate system logs, which could be used to hide malicious activity or deceive administrative oversight.
Business Impact
The ability to manipulate logs undermines the primary tool used for forensic analysis and incident detection. With a CVSS score of 7.9, this vulnerability carries a high impact, as it facilitates the obfuscation of unauthorized actions, potentially allowing attackers to maintain persistence within the environment without being detected by security teams.
Remediation Plan
Immediate Action: Update the upKeeper Instant Privilege Access software to the latest version provided by the vendor to ensure proper input/output sanitization.
Proactive Monitoring: Audit logs for suspicious entries, unusual formatting, or attempts to inject newline characters or control codes into log streams.
Compensating Controls: Utilize a centralized, immutable logging server that prevents local users from tampering with log files once they have been transmitted.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 24, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Log integrity is a cornerstone of enterprise security. It is highly recommended that organizations using upKeeper Instant Privilege Access apply the vendor's patch immediately to prevent attackers from masking their footprints. Failure to do so may result in a significant gap in security visibility.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The WP App Bar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'app-bar-features' parameter in all versions up to, and inclu...
The WP App Bar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'app-bar-features' parameter in all versions up to, and including, 1
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Infility Global plugin for WordPress is vulnerable to Stored Cross-Site Scripting via /cf7_record Log Endpoint in all versions up to, and includin...
The Infility Global plugin for WordPress is vulnerable to Stored Cross-Site Scripting via /cf7_record Log Endpoint in all versions up to, and including, 2
---METADATA---
VENDOR: WordPress
PRODUCT: Infility Global
AFFECTED_VERSIONS: 0 through 2.15.21
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
The Infility Global plugin for WordPress is susceptible to a stored cross-site scripting (XSS) vulnerability via the /cf7_record log endpoint, allowing for arbitrary script execution.
Executive Summary:
The Infility Global plugin for WordPress contains a stored cross-site scripting vulnerability that could allow attackers to execute malicious scripts in the context of an administrator's session.
Vulnerability Details
CVE-ID: CVE-2026-10734
Affected Software: WordPress Infility Global
Affected Versions: 0 through 2.15.21
Vulnerability: This is a stored cross-site scripting (CWE-79) vulnerability occurring within the /cf7_record log endpoint. It allows unauthenticated attackers to inject malicious scripts that are stored and executed when a user views the log data.
Business Impact
Successful exploitation could lead to session hijacking, defacement, or the execution of unauthorized administrative actions. Given the CVSS score of 7.2, this vulnerability poses a significant threat to the security of the WordPress administrative dashboard and overall site integrity.
Remediation Plan
Immediate Action: As no patch is currently available, administrators should immediately deactivate and remove the Infility Global plugin until a secure version is released.
Proactive Monitoring: Review administrative audit logs for suspicious activity or unauthorized changes to site configuration that might indicate an XSS-based attack.
Compensating Controls: Implement a robust Content Security Policy (CSP) and use a Web Application Firewall (WAF) to filter malicious input patterns targeting the /cf7_record endpoint.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of August 16, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The lack of a patch necessitates immediate deactivation to maintain a secure environment.
Analyst Recommendation
This vulnerability is critical due to the lack of a vendor-provided fix. Users must prioritize removing the affected software to prevent exploitation until the developer releases a patched version.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
A security issue exists within FactoryTalk® Services Platform (FTSP), allowing an attacker to bypass JWT signature validation during Okta Web Authenti...
A security issue exists within FactoryTalk® Services Platform (FTSP), allowing an attacker to bypass JWT signature validation during Okta Web Authentication
---METADATA---
VENDOR: Rockwell
PRODUCT: FactoryTalk Services Platform
AFFECTED_VERSIONS: 6.60
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
Rockwell Automation FactoryTalk Services Platform version 6.60 contains a flaw that permits the bypass of JSON Web Token signature validation during Okta Web Authentication.
Executive Summary:
A high severity authentication bypass vulnerability in Rockwell FactoryTalk Services Platform version 6.60 could allow an attacker to circumvent critical security validation processes.
Vulnerability Details
CVE-ID: CVE-2026-10714
Affected Software: Rockwell FactoryTalk Services Platform
Affected Versions: 6.60
Vulnerability: The platform suffers from a weak authentication mechanism (CWE-1390) where JWT signature validation can be bypassed during Okta Web Authentication. This requires a low-privileged authenticated user to initiate the exploit.
Business Impact
Successful exploitation allows an attacker to bypass authentication checks, potentially gaining unauthorized administrative access to the FactoryTalk Services Platform. This could lead to the compromise of industrial control systems or sensitive operational technology data. Given the CVSS score of 8.8, this vulnerability represents a substantial risk to operational continuity and system security.
Remediation Plan
Immediate Action: Apply the vendor-provided patch, RAID 1158263, to the affected FactoryTalk Services Platform version 6.60.
Proactive Monitoring: Monitor authentication logs for anomalous login activity or multiple failed attempts that might precede or follow a bypass attempt.
Compensating Controls: Restrict network access to the FactoryTalk Services Platform to known, trusted internal IP addresses to minimize the attack surface while the patch is being deployed.
Exploitation Status
Public Exploit Available: No confirmed public exploit (weaponized or otherwise) is available in the provided data.
Analyst Notes: As of July 15, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Per CISA's SSVC assessment, the exploitation risk is assessed as none.
Analyst Recommendation
Security teams must prioritize the application of the official Rockwell Automation patch to remediate this authentication flaw. Failure to address this vulnerability could leave critical infrastructure systems exposed to unauthorized access, making immediate patching a high-priority task.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Missing authentication for critical function vulnerability in AKIN Software Computer Import Export Industry and Trade Ltd
Missing authentication for critical function vulnerability in AKIN Software Computer Import Export Industry and Trade Ltd
---METADATA---
VENDOR: AKIN Software
PRODUCT: CafePlus
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
CafePlus by AKIN Software suffers from a missing authentication vulnerability, potentially allowing unauthorized access to critical functions.
Executive Summary:
A missing authentication vulnerability in AKIN Software’s CafePlus exposes critical functions to unauthorized access, risking full system compromise.
Vulnerability Details
CVE-ID: CVE-2026-10711
Affected Software: AKIN Software CafePlus
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability is categorized as a missing authentication for a critical function. This flaw allows an unauthenticated attacker to interact with sensitive administrative or operational functions within the software that should otherwise be protected by access controls.
Business Impact
The absence of authentication on critical functions presents a severe risk, as it allows unauthorized users to manipulate software operations, potentially leading to service disruption, revenue loss, or access to sensitive customer data. A CVSS score of 8.8 underscores the urgency of this issue, as it effectively bypasses the primary security boundary of the application.
Remediation Plan
Immediate Action: Update the CafePlus application to the latest version provided by AKIN Software to restore proper authentication checks.
Proactive Monitoring: Audit access logs for unauthorized attempts to access administrative modules or unusual command execution patterns within the CafePlus environment.
Compensating Controls: If a patch is not immediately deployable, restrict access to the CafePlus management interface to authorized personnel using network-level access control lists (ACLs).
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 24, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Missing authentication is a critical security failure that renders standard access policies ineffective. It is imperative that organizations using CafePlus identify their current version and coordinate with AKIN Software to apply necessary updates immediately to prevent unauthorized control over the software.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A maliciously crafted FBX file, when parsed through Autodesk FBX SDK, can trigger a stack-based buffer overflow vulnerability in fbxsdk::ExtractDrive
A maliciously crafted FBX file, when parsed through Autodesk FBX SDK, can trigger a stack-based buffer overflow vulnerability in fbxsdk::ExtractDrive
---METADATA---
VENDOR: Autodesk
PRODUCT: FBX SDK
AFFECTED_VERSIONS: 2020.3.9 up to (excluding) 2020.3.10
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A stack-based buffer overflow in the Autodesk FBX SDK function fbxsdk::ExtractDrive allows for potential code execution when parsing a maliciously crafted FBX file.
Executive Summary:
A stack-based buffer overflow vulnerability in the Autodesk FBX SDK could allow an attacker to achieve arbitrary code execution or cause application crashes via a specially crafted file.
Vulnerability Details
CVE-ID: CVE-2026-10710
Affected Software: Autodesk FBX SDK
Affected Versions: 2020.3.9 up to (excluding) 2020.3.10
Vulnerability: This is a stack-based buffer overflow (CWE-121) triggered within the fbxsdk::ExtractDrive function. The vulnerability requires user interaction, as the victim must open a malicious FBX file, and the attacker does not require prior authentication.
Business Impact
Successful exploitation of this vulnerability could result in total system compromise, including the execution of arbitrary code with the privileges of the user running the application. Given the CVSS score of 7.8, this represents a significant risk to the confidentiality, integrity, and availability of data processed by applications utilizing the affected SDK.
Remediation Plan
Immediate Action: Update the Autodesk FBX SDK to version 2020.3.10 or later as recommended by the vendor security advisory.
Proactive Monitoring: Monitor systems for anomalous application crashes or unexpected memory usage patterns within software that processes FBX files.
Compensating Controls: Implement strict file validation policies and restrict the processing of untrusted FBX files from unknown or unverified sources.
Exploitation Status
Public Exploit Available: Unknown.
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 potential for memory corruption, but it requires specific user interaction to trigger.
Analyst Recommendation
Organizations utilizing the Autodesk FBX SDK must prioritize the transition to version 2020.3.10. Given the potential for arbitrary code execution, patching should be scheduled as a high priority to minimize the exposure window.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A maliciously crafted FBX file, when parsed through Autodesk FBX SDK, can trigger a stack-based buffer overflow vulnerability in fbxsdk::FbxIO::Binary...
A maliciously crafted FBX file, when parsed through Autodesk FBX SDK, can trigger a stack-based buffer overflow vulnerability in fbxsdk::FbxIO::BinaryReadSectionHeader
---METADATA---
VENDOR: Autodesk
PRODUCT: FBX SDK
AFFECTED_VERSIONS: Autodesk FBX SDK: 2020.3.9 up to (excluding) 2020.3.10
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A stack-based buffer overflow vulnerability in the Autodesk FBX SDK allows remote attackers to execute arbitrary code via a maliciously crafted FBX file.
Executive Summary:
Autodesk FBX SDK is vulnerable to a stack-based buffer overflow that could allow an attacker to gain control over the affected system through a malicious file.
Vulnerability Details
CVE-ID: CVE-2026-10709
Affected Software: Autodesk FBX SDK
Affected Versions: Autodesk FBX SDK: 2020.3.9 up to (excluding) 2020.3.10
Vulnerability: The vulnerability exists in the fbxsdk::FbxIO::BinaryReadSectionHeader function, where insufficient bounds checking leads to a stack-based buffer overflow (CWE-121). An attacker requires user interaction, such as convincing a user to open a crafted FBX file, to trigger the flaw.
Business Impact
A successful exploit could allow for arbitrary code execution, leading to full system compromise or data exfiltration. While the CVSS score of 7.8 notes the requirement for user interaction, the potential for total system impact makes this a critical risk for design and engineering workflows.
Remediation Plan
Immediate Action: Update to Autodesk FBX SDK version 2020.3.10 or later as advised by the vendor.
Proactive Monitoring: Implement endpoint protection to scan incoming FBX files for malicious content and monitor for abnormal application behavior when processing 3D data.
Compensating Controls: Restrict the opening of FBX files from untrusted or external sources to mitigate the risk of triggering the overflow.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of August 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Buffer overflows in file parsing libraries are a well-known attack vector, requiring vigilance when handling untrusted files.
Analyst Recommendation
Users and developers utilizing the Autodesk FBX SDK must ensure they update to the remediated version immediately. Avoid processing FBX files from untrusted sources until the update has been fully deployed across all workstations and servers.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
In Adalo’s no-code app builder, (Versions 1 and 2) the attackers may extract full user records and correlate user behavior across multiple application...
In Adalo’s no-code app builder, (Versions 1 and 2) the attackers may extract full user records and correlate user behavior across multiple applications via dbId enumeration. The platform does not implement data minimization, privacy by design, or implement appropriate technical safeguards, allowing
Update Adalo No-Code App Builder App Builder to the latest version. Monitor for exploitation attempts and review access logs.
The Zephyr Bluetooth GATT client CCC-write response handler gatt_write_ccc_rsp() in subsys/bluetooth/host/gatt
The Zephyr Bluetooth GATT client CCC-write response handler gatt_write_ccc_rsp() in subsys/bluetooth/host/gatt
---METADATA---
VENDOR: GATT
PRODUCT: zephyr
AFFECTED_VERSIONS: zephyrproject zephyr: 2.4.0 up to (excluding) 4.5.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the Zephyr Bluetooth GATT client handler can lead to memory corruption when processing specific responses.
Executive Summary:
A use-after-free vulnerability in the Zephyr RTOS Bluetooth stack allows adjacent attackers to trigger memory corruption or system crashes.
Vulnerability Details
CVE-ID: CVE-2026-10685
Affected Software: Zephyr Project Zephyr
Affected Versions: 2.4.0 up to (excluding) 4.5.0
Vulnerability: A use-after-free vulnerability (CWE-416) exists in the gatt_write_ccc_rsp() function within the Bluetooth host subsystem. An attacker within Bluetooth range can trigger this condition by sending a malformed GATT response, causing the system to interact with freed memory.
Business Impact
The vulnerability poses a risk of system instability, denial of service, or potentially arbitrary code execution on devices running the Zephyr RTOS. Given the nature of embedded systems, this could lead to the total loss of control over connected IoT devices or the compromise of local Bluetooth communications. The CVSS score of 7.6 highlights the urgency of addressing this flaw in connected product ecosystems.
Remediation Plan
Immediate Action: Update the Zephyr RTOS project to version 4.5.0 or later.
Proactive Monitoring: Monitor Bluetooth traffic for unexpected or malformed GATT responses that deviate from standard protocol specifications.
Compensating Controls: Disable Bluetooth functionality if it is not required for the device's operational use case to mitigate the attack vector entirely.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of August 1, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Use-after-free flaws in low-level Bluetooth stacks are notoriously difficult to exploit but are highly impactful when successful.
Analyst Recommendation
Developers and manufacturers utilizing Zephyr RTOS must integrate the provided security patch immediately. Ensuring the Bluetooth stack is updated is critical for the security of all deployed Zephyr-based hardware.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The Zephyr ADIN2111/ADIN1110 10BASE-T1S/T1L Ethernet driver (drivers/ethernet/eth_adin2111
The Zephyr ADIN2111/ADIN1110 10BASE-T1S/T1L Ethernet driver (drivers/ethernet/eth_adin2111
---METADATA---
VENDOR: zephyrproject
PRODUCT: zephyr
AFFECTED_VERSIONS: 3.7.0 up to (excluding) 4.5.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
Memory safety vulnerabilities in the Zephyr ADIN2111/ADIN1110 Ethernet driver allow for potential memory corruption or unauthorized data access.
Executive Summary:
Memory safety flaws in the Zephyr Ethernet driver expose the system to potential corruption and unauthorized access, necessitating an immediate update to the latest version.
Vulnerability Details
CVE-ID: CVE-2026-10673
Affected Software: zephyrproject zephyr
Affected Versions: 3.7.0 up to (excluding) 4.5.0
Vulnerability: This issue involves memory safety errors (CWE-787, CWE-125) within the ADIN2111/ADIN1110 10BASE-T1S/T1L Ethernet driver. These flaws allow an attacker with adjacent network access to trigger memory corruption or read out-of-bounds memory, which could lead to system instability or arbitrary code execution.
Business Impact
Given the CVSS score of 8.3, this vulnerability poses a significant risk to systems relying on Zephyr for network communications. Exploitation could result in a complete compromise of the embedded device, leading to service disruption or the exfiltration of sensitive data handled by the RTOS.
Remediation Plan
Immediate Action: Update the Zephyr RTOS to version 4.5.0 or later to patch the vulnerable Ethernet driver.
Proactive Monitoring: Monitor network traffic for malformed frames or unexpected behavior in devices utilizing the ADIN2111/ADIN1110 hardware interfaces.
Compensating Controls: Isolate devices using the affected driver to a trusted, restricted network segment to prevent adjacent network attackers from reaching the vulnerable interface.
Exploitation Status
Public Exploit Available: No (exploit_available: false)
Analyst Notes: As of July 17, 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 complexity of these memory safety bugs generally requires deep expertise in embedded systems and driver-level exploitation.
Analyst Recommendation
Due to the existence of a proof-of-concept and the critical nature of memory corruption vulnerabilities in RTOS environments, users must prioritize the transition to Zephyr version 4.5.0. Failure to update leaves devices exposed to network-based attacks that could result in full system takeover.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Zephyr's dynamic kernel-object tracking (kernel/userspace/userspace
Zephyr's dynamic kernel-object tracking (kernel/userspace/userspace
---METADATA---
VENDOR: zephyrproject
PRODUCT: zephyr
AFFECTED_VERSIONS: 1.14.0 up to (excluding) 4.5.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the Zephyr RTOS kernel-object tracking mechanism could allow unauthorized operations.
Executive Summary:
A high-severity use-after-free vulnerability exists in the Zephyr RTOS kernel, potentially allowing a local attacker to trigger memory corruption or unauthorized system actions.
Vulnerability Details
CVE-ID: CVE-2026-10667
Affected Software: zephyrproject zephyr
Affected Versions: 1.14.0 up to (excluding) 4.5.0
Vulnerability: The vulnerability is a use-after-free (CWE-416) condition found within the dynamic kernel-object tracking logic, which can be triggered by a local attacker to manipulate kernel-space memory.
Business Impact
With a CVSS score of 7.8, this vulnerability poses a critical risk to systems running the Zephyr RTOS. Successful exploitation could lead to system crashes (DoS) or the potential for privilege escalation, compromising the reliability of embedded or IoT devices.
Remediation Plan
Immediate Action: Review the Zephyr project security advisories and apply the latest kernel updates provided by the project to ensure the fix is implemented.
Proactive Monitoring: Monitor device stability and kernel logs for memory-related errors or unexpected reboots that may indicate exploitation attempts.
Compensating Controls: Implement memory protection features and kernel hardening where supported by the specific hardware platform to limit the impact of memory corruption.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Use-after-free flaws in RTOS kernels are inherently complex and typically require precise timing to exploit.
Analyst Recommendation
Given the critical nature of RTOS kernel vulnerabilities, it is imperative that all developers and administrators running versions of Zephyr prior to 4.5.0 update their codebase immediately. Refer to the official GitHub advisory for specific commit-level remediation details.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
parse_ipv4() in subsys/net/ip/utils
parse_ipv4() in subsys/net/ip/utils
---METADATA---
VENDOR: Zephyr Project
PRODUCT: Zephyr
AFFECTED_VERSIONS: 1.9.0 up to (excluding) 4.5.0
CONFIDENCE: high
MISSING: patch (specific version number for fixed release)
---END_METADATA---
Description Summary:
A memory-safety vulnerability in the parse_ipv4() function within the Zephyr RTOS networking stack may allow for potential remote code execution or system instability.
Executive Summary:
A critical memory-safety vulnerability in the Zephyr RTOS networking stack could allow an unauthenticated remote attacker to compromise system integrity.
Vulnerability Details
CVE-ID: CVE-2026-10666
Affected Software: Zephyr Project Zephyr
Affected Versions: 1.9.0 up to (excluding) 4.5.0
Vulnerability: The parse_ipv4() function in subsys/net/ip/utils is susceptible to a memory-safety issue (CWE-787). This allows an unauthenticated attacker to trigger an out-of-bounds write via maliciously crafted network traffic.
Business Impact
As this affects the networking stack of an RTOS, a successful exploit could lead to full system compromise, including remote code execution, denial of service, or unauthorized control of the embedded device. The CVSS score of 8.1 reflects the high potential for impact on connected devices, which are often critical components of industrial or IoT infrastructure.
Remediation Plan
Immediate Action: Upgrade to the latest available version of the Zephyr RTOS (targeted at 4.5.0 or later) as provided by the vendor.
Proactive Monitoring: Monitor network traffic for malformed IPv4 packets that may trigger crashes or unexpected behavior in the network stack.
Compensating Controls: Implement network segmentation and firewall rules to restrict traffic to only known, trusted sources, reducing the attack surface for the networking stack.
Exploitation Status
Public Exploit Available: No (unknown)
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Memory-safety flaws in RTOS networking stacks are high-value targets; thus, prompt patching is essential.
Analyst Recommendation
The severity of this memory corruption vulnerability necessitates immediate action, particularly for devices deployed in public-facing or untrusted network environments. Developers should integrate the provided fix commits into their downstream distributions to ensure system security.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
In Zephyr's WireGuard subsystem (subsys/net/lib/wireguard), wg_process_data_message() in wg_crypto
In Zephyr's WireGuard subsystem (subsys/net/lib/wireguard), wg_process_data_message() in wg_crypto
---METADATA---
VENDOR: zephyrproject
PRODUCT: zephyr
AFFECTED_VERSIONS: 4.4.0 up to (excluding) 4.5.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
A buffer overflow vulnerability in the WireGuard subsystem of Zephyr RTOS 4.4.0 allows remote attackers to cause potential integrity or availability impacts.
Executive Summary:
A high-severity buffer overflow in the Zephyr RTOS WireGuard subsystem could allow remote attackers to compromise system integrity or availability.
Vulnerability Details
CVE-ID: CVE-2026-10665
Affected Software: zephyrproject zephyr
Affected Versions: 4.4.0 up to (excluding) 4.5.0
Vulnerability: This is a Buffer Overflow (CWE-787) vulnerability located in the wg_process_data_message() function within the WireGuard cryptographic subsystem. An unauthenticated attacker can exploit this via maliciously crafted network packets to cause memory corruption, potentially leading to system instability or arbitrary code execution.
Business Impact
With a CVSS score of 7.4, this vulnerability poses a serious risk to embedded devices running Zephyr RTOS. Because the flaw exists in the network stack, it is remotely exploitable, which could lead to a complete compromise of the device's integrity or result in a Denial of Service (DoS), potentially disrupting critical industrial or IoT operations.
Remediation Plan
Immediate Action: Apply the vendor-provided security updates or backport the fix from the referenced commit to your local Zephyr environment.
Proactive Monitoring: Monitor network traffic for malformed or unexpected WireGuard protocol packets that may indicate an exploitation attempt.
Compensating Controls: If patching is not immediately feasible, isolate devices using Zephyr's WireGuard implementation behind a firewall that inspects and filters traffic to the relevant ports.
Exploitation Status
Public Exploit Available: No (Exploit_available: false)
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The complexity of the attack (AC:H) provides a slight barrier, but the impact on integrity and availability remains severe.
Analyst Recommendation
Due to the nature of buffer overflows in kernel-level network stacks, this vulnerability should be treated with high urgency. Developers and system integrators should prioritize updating to the patched version of Zephyr or applying the upstream fix to ensure the robustness of their communication subsystems.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A missing length validation in the Zephyr Bluetooth Host ISO receive path can be triggered by malformed HCI ISO data
A missing length validation in the Zephyr Bluetooth Host ISO receive path can be triggered by malformed HCI ISO data
---METADATA---
VENDOR: Zephyr Project
PRODUCT: Zephyr RTOS
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---
Description Summary:
A missing length validation in the Zephyr Bluetooth Host ISO receive path can be triggered by malformed HCI ISO data, leading to potential memory corruption or system crashes.
Executive Summary:
A high-severity vulnerability exists in the Zephyr RTOS Bluetooth Host stack where missing length validation allows unauthenticated attackers to trigger a crash via malformed ISO data.
Vulnerability Details
CVE-ID: CVE-2026-10658
Affected Software: Zephyr Project Zephyr RTOS
Affected Versions: See vendor advisory for affected versions
Vulnerability: The flaw resides in the Bluetooth Host ISO receive path, where the system fails to perform adequate length validation on incoming Host Controller Interface (HCI) ISO data. An unauthenticated attacker can exploit this by sending malformed packets, potentially resulting in memory corruption or a system-wide assertion failure.
Business Impact
With a CVSS score of 7.1, this vulnerability presents a substantial risk to systems utilizing Zephyr RTOS for Bluetooth communication. Successful exploitation results in system instability or denial-of-service, which could compromise the reliability of connected embedded hardware. Impact includes potential service outages and the need for manual device resets.
Remediation Plan
Immediate Action: Apply the vendor-provided patch or upgrade to the latest stable release of Zephyr RTOS that includes the required input validation logic.
Proactive Monitoring: Review system logs for unexpected crashes or error messages related to the Bluetooth Host Controller Interface during data reception.
Compensating Controls: Use a hardware-based Bluetooth controller or firewall to sanitize or drop malformed HCI traffic before it reaches the host software stack.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 23, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Given that this vulnerability affects the core Bluetooth Host communication path, it is imperative that organizations using Zephyr RTOS verify their current version and deploy the latest security updates. Patching is the only effective way to ensure the integrity of the data receive path and prevent exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A malformed Bluetooth Classic SDP attribute can trigger a reachable assertion in Zephyr's SDP parser
A malformed Bluetooth Classic SDP attribute can trigger a reachable assertion in Zephyr's SDP parser
---METADATA---
VENDOR: Zephyr Project
PRODUCT: Zephyr RTOS
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---
Description Summary:
A malformed Bluetooth Classic SDP attribute can trigger a reachable assertion in the Zephyr RTOS SDP parser, potentially causing a denial-of-service.
Executive Summary:
A critical vulnerability in the Zephyr RTOS Bluetooth stack allows unauthenticated attackers to trigger a system assertion, resulting in a potential denial-of-service.
Vulnerability Details
CVE-ID: CVE-2026-10651
Affected Software: Zephyr Project Zephyr RTOS
Affected Versions: See vendor advisory for affected versions
Vulnerability: This vulnerability involves a reachable assertion within the Bluetooth Classic Service Discovery Protocol (SDP) parser. An unauthenticated remote attacker can trigger this condition by sending a specially crafted SDP attribute, causing the affected device to crash.
Business Impact
The exploitation of this flaw leads to a denial-of-service, which can render embedded devices running Zephyr RTOS unresponsive. Given the CVSS score of 7.1, this is a High-severity risk, particularly for critical infrastructure or medical devices that rely on constant availability. Unplanned downtime in these environments could lead to significant operational disruption and safety risks.
Remediation Plan
Immediate Action: Update the Zephyr RTOS codebase to the version specified in the official vendor advisory to incorporate the necessary assertion handling patches.
Proactive Monitoring: Monitor Bluetooth traffic logs for malformed or unexpected SDP attribute packets that deviate from standard protocol specifications.
Compensating Controls: Implement strict Bluetooth perimeter security, such as disabling Bluetooth functionality when not required or restricting pairing to trusted devices only.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 23, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
The reliance on the Bluetooth stack in embedded systems makes this flaw a significant concern for device stability. Administrators must prioritize applying vendor-supplied updates to the RTOS image to mitigate the risk of remote service disruption caused by malformed protocol packets.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The Form Maker by 10Web plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1
The Form Maker by 10Web plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1
Executive Summary:
A high-severity vulnerability exists within the Form Maker by 10Web plugin for WordPress, identified as CVE-2026-1065. This flaw allows an attacker to inject malicious code into the website by submitting a specially crafted form. This can lead to the compromise of administrator or user accounts, theft of sensitive data, and potential takeover of the affected website.
Vulnerability Details
CVE-ID: CVE-2026-1065
Affected Software: WordPress Form Maker by 10Web plugin
Affected Versions: All versions up to, and including, 1
Vulnerability: The vulnerability is a Stored Cross-Site Scripting (XSS) flaw. An unauthenticated attacker can inject malicious client-side script (e.g., JavaScript) into fields within a form created by the plugin. The plugin fails to properly sanitize this input before storing it in the database. When a privileged user, such as an administrator, views the submitted form data in the WordPress backend, the malicious script executes within the context of their browser session, potentially allowing the attacker to hijack their session, steal credentials, perform actions on their behalf, or redirect them to a malicious site.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 7.2. Successful exploitation could lead to significant business impact, including the compromise of administrator accounts, which would grant an attacker full control over the WordPress site. This could result in website defacement, theft of sensitive data submitted by users through forms (personally identifiable information, etc.), loss of customer trust, and reputational damage. The compromised website could also be used as a platform to host malware or launch further attacks against visitors.
Remediation Plan
Immediate Action:
Proactive Monitoring:
<script>, <img>, <iframe>) or JavaScript event handlers (onerror, onload).Compensating Controls:
/wp-admin/) to trusted IP addresses only.Exploitation Status
Public Exploit Available: False
Analyst Notes: As of February 3, 2026, there are no known public exploits or active exploitation campaigns targeting this specific vulnerability. However, the technique for exploiting Stored XSS is well-understood by threat actors. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, but this status could change if widespread attacks are observed.
Analyst Recommendation
Given the high severity (CVSS 7.2) of this vulnerability and its presence in a popular form-building plugin, we strongly recommend immediate remediation. Organizations using the affected "Form Maker by 10Web" plugin should prioritize applying the vendor-supplied security update without delay. Although there is no evidence of active exploitation in the wild, the risk of compromise is significant, and proactive patching is the most effective defense.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A type confusion vulnerability in the V8 JavaScript engine of Google Chrome could allow for remote code execution.
Executive Summary:
A type confusion vulnerability in Google Chrome’s V8 engine creates a high-risk scenario for remote code execution and potential system takeover.
Vulnerability Details
CVE-ID: CVE-2026-10935
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The issue is a type confusion vulnerability within the V8 JavaScript engine. An unauthenticated attacker can exploit this flaw by delivering malicious JavaScript to the browser, which, when processed, leads to memory corruption and arbitrary code execution.
Business Impact
The CVSS score of 8.8 highlights the critical nature of this V8 flaw. Successful exploitation results in complete control over the browser, which can be leveraged to steal sensitive data, deploy malware, or pivot into internal infrastructure, causing significant reputational and operational damage.
Remediation Plan
Immediate Action: Apply the vendor-provided update to move all Chrome instances to version 149 or higher.
Proactive Monitoring: Utilize endpoint security tools to monitor for unusual memory allocation patterns or unauthorized subprocess spawning associated with the browser.
Compensating Controls: Implement network-level filtering to block access to known malicious domains and ensure that all browser instances are running in an appropriately restricted user context.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 5, 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
Consistent with previous V8 engine vulnerabilities, this issue represents a significant threat to endpoint security. Security teams must treat this update with high priority and ensure all workstations are patched to the secure version immediately.