Monthly
Memory corruption in Google Chrome's Workers component affects versions prior to 155.0.8059.84 and can allow a remote attacker to execute arbitrary code inside the browser's renderer sandbox when a victim visits a crafted HTML page. The CVSS vector indicates network reachability, no authentication, and required user interaction, with high confidentiality, integrity, and availability impact inside the sandbox; however, Scope is Unchanged, so full host compromise requires a separate sandbox escape. Assessment signals conflict and should be weighed carefully: CVSS is 8.8 while Chromium rated it Medium, SSVC says exploitation is none and automatable is no, and no public exploit identified at time of analysis; a vendor patch is available.
Memory corruption in the V8 JavaScript engine of Google Chrome before 155.0.8059.84 lets a remote, unauthenticated attacker achieve arbitrary code execution inside the browser's renderer sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction (CVSS UI:R) - the target must navigate to attacker-controlled or compromised web content - and no public exploit code has been identified at time of analysis, with CISA SSVC rating current exploitation as 'none'. Because the code execution is explicitly confined to the sandbox (S:U), full host compromise would require chaining a separate sandbox-escape vulnerability, making this a high-priority patch item rather than an emergency.
Memory corruption in Google Chrome's DOM implementation allows remote attackers to execute arbitrary code within the browser's renderer sandbox by convincing a victim to load a crafted HTML page. All Chrome builds prior to 155.0.8059.84 are affected; exploitation is unauthenticated (CVSS PR:N) but requires the user to navigate to attacker-controlled content (UI:R), and the resulting code execution is contained by the sandbox (S:U), so host compromise would require a separate sandbox-escape vulnerability. No public exploit has been identified at time of analysis and CISA's SSVC assessment rates exploitation as none, though the vendor's Chrome severity rating is High and technical impact is total for the compromised renderer; a vendor patch is available in Chrome 155.0.8059.84 and the corresponding extended stable update.
Improper memory-buffer bounds handling in Unitronics UniStream Pro PLCs (B10 and C10 hardware variants) running UniLogic firmware prior to 1.41.329 allows an attacker with network reachability and low-privilege authentication (CVSS PR:L) to corrupt memory and potentially achieve high confidentiality and integrity impact with limited availability impact (CVSS 8.3). Because these are OT/ICS controllers, successful exploitation could let an authenticated actor disrupt or manipulate the logic and data handled by the device rather than just crash it. The flaw was reported by Israel's INCD; no public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV, so exploitation is currently assessed as requiring deliberate, targeted access rather than opportunistic scanning. Devices already running UniLogic 1.41.329 or later are not affected.
A sandbox escape in Mozilla Firefox's Networking component allows unauthenticated remote attackers to break out of the browser's security sandbox and potentially execute code on the host when a victim loads attacker-controlled web content. The vulnerability stems from incorrect boundary conditions (CWE-119) and carries a CVSS score of 9.6, though exploitation requires user interaction (UI:R) and the sandbox escape alone must be chained with a separate content-process code-execution primitive for full host compromise. No public exploit code has been identified, and the EPSS score is low at 0.19% (8th percentile); patched versions are Firefox 158 and Firefox ESR 153.5.
Memory corruption in Mozilla Firefox's Layout engine lets a remote, unauthenticated attacker who convinces a victim to render attacker-controlled web content corrupt memory, with the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicating high confidentiality and integrity impact and a full availability impact on the client. All Firefox builds prior to 158 are affected, along with Firefox ESR releases prior to 115.43 and 153.5. Exploitation hinges entirely on user interaction - the victim must navigate to or render a hostile page - and no public exploit or active exploitation has been identified at time of analysis; EPSS is low at 0.16% (5th percentile), and vendor-released fixes (Firefox 158, ESR 115.43, ESR 153.5) are available per Mozilla advisories mfsa2026-106 through mfsa2026-110.
Mozilla Firefox releases prior to 158, Firefox ESR prior to 115.43, and Firefox ESR prior to 153.5 contain incorrect boundary conditions in the JavaScript engine that let remote attackers corrupt or disclose memory when a user loads attacker-controlled web content. Because the weakness sits in script processing, no credentials or pre-existing privileges are needed - but exploitation is not unattended: the victim must actively browse to a malicious or compromised page with JavaScript enabled (the default), and the vendor rates availability impact as none, so the realistic outcome is memory disclosure/integrity corruption rather than a guaranteed crash or confirmed remote code execution. Publicly available exploit code has not been observed and there is no public exploit identified at time of analysis; CISA KEV does not list this CVE, and EPSS is only 0.16% (4th percentile), so this is a genuine patch-promptly issue rather than an emergency one.
Memory corruption in Mozilla Firefox's JavaScript engine can be triggered when a remote unauthenticated attacker convinces a user to load attacker-controlled JavaScript content, yielding high confidentiality and integrity impact with no availability impact. This is not a zero-click attack; exploitation requires user interaction (UI:R) to render a malicious page, so it depends on social engineering, malvertising, or a compromised site. Mozilla fixed the issue in Firefox 158, Firefox ESR 115.43, and Firefox ESR 153.5; at time of analysis there is no public exploit identified, and EPSS is very low at 0.16% (4th percentile), indicating a genuine but not emergency-level risk.
Authenticated attackers holding service-level credentials on the Flexible Service Processor (FSP) can read or modify arbitrary regions of Hostboot memory on IBM Power Systems firmware levels FW1060.00 through FW1060.81 by sending a specially crafted message over the service processor mailbox interface, corrupting the host firmware boot stack and the hypervisor it subsequently loads. The flaw is rated CVSS 8.2 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H), with the scope-change rating reflecting that the FSP compromise crosses a boundary into host firmware and produces high confidentiality, integrity, and availability impact on the managed system. Exploitation is gated behind high-privilege service-processor access rather than network reach to the managed OS, and no public exploit code has been identified at time of analysis; no EPSS score was supplied, so it could not be factored into the risk picture.
Buffer overflow in the Edimax BR-6208AC router (firmware 1.32) allows an attacker who can reach the device's HTTP management interface to corrupt memory via a crafted 'ifname' argument sent to the /goform/formWlSiteSurvey endpoint, with high impact to confidentiality, integrity, and availability. Exploitation requires at least low-privileged authenticated access to the web UI (CVSS 4.0 vector PR:L; independently assessed CVSS 3.1 base 8.6), meaning the endpoint must be reachable either from the LAN or from an internet-exposed admin panel using valid or default credentials; no user interaction is required once the attacker is authenticated. Publicly available exploit code exists (a PoC walkthrough is published on GitHub), but there is no evidence of confirmed active exploitation in the wild, and the vendor did not respond to disclosure - the product is end-of-life and no fix is expected.
Memory corruption in Google Chrome's Workers component affects versions prior to 155.0.8059.84 and can allow a remote attacker to execute arbitrary code inside the browser's renderer sandbox when a victim visits a crafted HTML page. The CVSS vector indicates network reachability, no authentication, and required user interaction, with high confidentiality, integrity, and availability impact inside the sandbox; however, Scope is Unchanged, so full host compromise requires a separate sandbox escape. Assessment signals conflict and should be weighed carefully: CVSS is 8.8 while Chromium rated it Medium, SSVC says exploitation is none and automatable is no, and no public exploit identified at time of analysis; a vendor patch is available.
Memory corruption in the V8 JavaScript engine of Google Chrome before 155.0.8059.84 lets a remote, unauthenticated attacker achieve arbitrary code execution inside the browser's renderer sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction (CVSS UI:R) - the target must navigate to attacker-controlled or compromised web content - and no public exploit code has been identified at time of analysis, with CISA SSVC rating current exploitation as 'none'. Because the code execution is explicitly confined to the sandbox (S:U), full host compromise would require chaining a separate sandbox-escape vulnerability, making this a high-priority patch item rather than an emergency.
Memory corruption in Google Chrome's DOM implementation allows remote attackers to execute arbitrary code within the browser's renderer sandbox by convincing a victim to load a crafted HTML page. All Chrome builds prior to 155.0.8059.84 are affected; exploitation is unauthenticated (CVSS PR:N) but requires the user to navigate to attacker-controlled content (UI:R), and the resulting code execution is contained by the sandbox (S:U), so host compromise would require a separate sandbox-escape vulnerability. No public exploit has been identified at time of analysis and CISA's SSVC assessment rates exploitation as none, though the vendor's Chrome severity rating is High and technical impact is total for the compromised renderer; a vendor patch is available in Chrome 155.0.8059.84 and the corresponding extended stable update.
Improper memory-buffer bounds handling in Unitronics UniStream Pro PLCs (B10 and C10 hardware variants) running UniLogic firmware prior to 1.41.329 allows an attacker with network reachability and low-privilege authentication (CVSS PR:L) to corrupt memory and potentially achieve high confidentiality and integrity impact with limited availability impact (CVSS 8.3). Because these are OT/ICS controllers, successful exploitation could let an authenticated actor disrupt or manipulate the logic and data handled by the device rather than just crash it. The flaw was reported by Israel's INCD; no public exploit code has been identified at time of analysis, and the CVE is not listed in CISA KEV, so exploitation is currently assessed as requiring deliberate, targeted access rather than opportunistic scanning. Devices already running UniLogic 1.41.329 or later are not affected.
A sandbox escape in Mozilla Firefox's Networking component allows unauthenticated remote attackers to break out of the browser's security sandbox and potentially execute code on the host when a victim loads attacker-controlled web content. The vulnerability stems from incorrect boundary conditions (CWE-119) and carries a CVSS score of 9.6, though exploitation requires user interaction (UI:R) and the sandbox escape alone must be chained with a separate content-process code-execution primitive for full host compromise. No public exploit code has been identified, and the EPSS score is low at 0.19% (8th percentile); patched versions are Firefox 158 and Firefox ESR 153.5.
Memory corruption in Mozilla Firefox's Layout engine lets a remote, unauthenticated attacker who convinces a victim to render attacker-controlled web content corrupt memory, with the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicating high confidentiality and integrity impact and a full availability impact on the client. All Firefox builds prior to 158 are affected, along with Firefox ESR releases prior to 115.43 and 153.5. Exploitation hinges entirely on user interaction - the victim must navigate to or render a hostile page - and no public exploit or active exploitation has been identified at time of analysis; EPSS is low at 0.16% (5th percentile), and vendor-released fixes (Firefox 158, ESR 115.43, ESR 153.5) are available per Mozilla advisories mfsa2026-106 through mfsa2026-110.
Mozilla Firefox releases prior to 158, Firefox ESR prior to 115.43, and Firefox ESR prior to 153.5 contain incorrect boundary conditions in the JavaScript engine that let remote attackers corrupt or disclose memory when a user loads attacker-controlled web content. Because the weakness sits in script processing, no credentials or pre-existing privileges are needed - but exploitation is not unattended: the victim must actively browse to a malicious or compromised page with JavaScript enabled (the default), and the vendor rates availability impact as none, so the realistic outcome is memory disclosure/integrity corruption rather than a guaranteed crash or confirmed remote code execution. Publicly available exploit code has not been observed and there is no public exploit identified at time of analysis; CISA KEV does not list this CVE, and EPSS is only 0.16% (4th percentile), so this is a genuine patch-promptly issue rather than an emergency one.
Memory corruption in Mozilla Firefox's JavaScript engine can be triggered when a remote unauthenticated attacker convinces a user to load attacker-controlled JavaScript content, yielding high confidentiality and integrity impact with no availability impact. This is not a zero-click attack; exploitation requires user interaction (UI:R) to render a malicious page, so it depends on social engineering, malvertising, or a compromised site. Mozilla fixed the issue in Firefox 158, Firefox ESR 115.43, and Firefox ESR 153.5; at time of analysis there is no public exploit identified, and EPSS is very low at 0.16% (4th percentile), indicating a genuine but not emergency-level risk.
Authenticated attackers holding service-level credentials on the Flexible Service Processor (FSP) can read or modify arbitrary regions of Hostboot memory on IBM Power Systems firmware levels FW1060.00 through FW1060.81 by sending a specially crafted message over the service processor mailbox interface, corrupting the host firmware boot stack and the hypervisor it subsequently loads. The flaw is rated CVSS 8.2 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H), with the scope-change rating reflecting that the FSP compromise crosses a boundary into host firmware and produces high confidentiality, integrity, and availability impact on the managed system. Exploitation is gated behind high-privilege service-processor access rather than network reach to the managed OS, and no public exploit code has been identified at time of analysis; no EPSS score was supplied, so it could not be factored into the risk picture.
Buffer overflow in the Edimax BR-6208AC router (firmware 1.32) allows an attacker who can reach the device's HTTP management interface to corrupt memory via a crafted 'ifname' argument sent to the /goform/formWlSiteSurvey endpoint, with high impact to confidentiality, integrity, and availability. Exploitation requires at least low-privileged authenticated access to the web UI (CVSS 4.0 vector PR:L; independently assessed CVSS 3.1 base 8.6), meaning the endpoint must be reachable either from the LAN or from an internet-exposed admin panel using valid or default credentials; no user interaction is required once the attacker is authenticated. Publicly available exploit code exists (a PoC walkthrough is published on GitHub), but there is no evidence of confirmed active exploitation in the wild, and the vendor did not respond to disclosure - the product is end-of-life and no fix is expected.