Monthly
Circuit soundness failure in Payy (polybase/payy) prior to 1.3.0 lets an authorized rollup prover smuggle an extra burn message into the public messages[1000] array accepted by RollupV1.verifyRollup(), causing the rollup contract to transfer USDC from the contract to an attacker-controlled recipient. The attacker must be a registered prover with the ability to construct a valid agg_final proof for an already-approved rollup block and to manipulate the unconstrained tail of the public input array, so the assessed vector is authenticated (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, integrity-only impact with no confidentiality or availability loss). Exploitability today is further limited because verifyRollup() is restricted to the existing allowlisted prover, but the flaw becomes effectively unauthenticated under the permissionless prover model in the Payy whitepaper (Section 3.3.2 stake-to-join and Section 3.3.1 fallback submission by other nodes). No public exploit code had been identified at time of analysis, and the vendor-released patch is version 1.3.0.
Remote code execution affects Dell Wyse Management Suite in all versions prior to WMS 5.5 HF1, stemming from the application's acceptance of extraneous untrusted data alongside trusted data (CWE-349). Per the provided CVSS vector (PR:N), a remote unauthenticated attacker could potentially achieve full code execution against the management server, though the Dell description text characterizes the actor as 'low privileged' - a discrepancy worth verifying. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Cache poisoning in PowerDNS Recursor allows a malicious or compromised authoritative DNS server to inject forged records by returning a crafted zone that the resolver ingests through its ZoneToCache feature. Because the poisoned data lands in the shared recursor cache, all downstream clients can be served attacker-controlled answers, enabling traffic redirection and spoofing. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; the CVSS 7.5 (high) rating reflects high integrity impact with a scope change but high attack complexity.
Local privilege escalation in Windows COM across Windows 10 (1809, 21H2, 22H2), Windows 11 (22H3-26H1), and Windows Server (2019-2025) allows unauthenticated attackers with local access to achieve full system compromise (high confidentiality, integrity, and availability impact) by exploiting acceptance of untrusted data alongside trusted data. CVSS 8.4 reflects the severe impact of complete privilege escalation despite requiring local access. Vendor-released patch available with specific build n
Arbitrary code execution in OpenClaw versions prior to 2026.3.24 enables local attackers to execute malicious code during npm package installation by crafting a malicious .npmrc file that overrides the git executable. When npm install runs in the staged package directory with git dependencies, the attacker-controlled .npmrc configuration triggers execution of arbitrary programs specified by the attacker. Exploitation requires user interaction to install the malicious plugin or hook locally. No public exploit identified at time of analysis.
Cache poisoning in Nuxt OG Image 6.2.5 through 6.6.x lets unauthenticated remote attackers overwrite the cached image slot used for a site's legitimate Open Graph image by submitting attacker-controlled rendering parameters (notably the 'title' value) alongside a derived cacheKey to the dynamic /_og/d/*.png route, so spoofed image content is then served to users and crawlers that request the poisoned URL. Both the module's own CVSS 4.0 vector (6.9, AV:N/AC:L/PR:N/UI:N/VI:L) and the independent assessment (CVSS 3.1, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) agree the impact is limited to integrity of served image content - no code execution, data theft, or availability loss - and that exploitation requires a runtime deployment where URL signing has not been configured. No public exploit code was identified at time of analysis and the issue is not listed as actively exploited, but a fixed release (6.7.0), the upstream commit, and the advisory are all public, so the technical details needed to reproduce the cache-key collision are openly documented. The independent assessment characterizes this as a genuine but moderate-severity integrity issue rather than a top-priority emergency.
Cache poisoning in GitLab CE/EE allows an authenticated user, on deployments running a specific caching configuration, to corrupt cached page content that is subsequently served to other users because cache keys are constructed improperly. Affected versions are all releases from 16.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 on both Community and Enterprise editions; exploitation requires a valid account (PR:L), a non-default deployment/caching setup, high attack complexity (AC:H), and victim interaction (UI:R), yielding only limited confidentiality, integrity, and availability impact (CVSS 4.6). No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV), so this is best treated as a low-priority, targeted-scenario issue rather than a broadly exploitable one.
BIND 9 secondary (slave) servers that restrict zone transfers with TSIG can be tricked into serving attacker-supplied zone contents: an attacker able to occupy or spoof the position of the configured primary can deliver a multi-message TCP IXFR whose final TSIG-signed message never arrives, and named commits and serves the records already received without rolling back to the pre-transfer state. Affected releases are BIND 9 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, and 9.21.0 through 9.21.25, along with the -S1 builds 9.11.3-S1 through 9.18.50-S1 and 9.20.9-S1 through 9.20.27-S1; no valid TSIG key is required (CVSS 3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L, 6.5), but exploitation is conditional on the attacker's network position and the multi-message IXFR condition, so this is an integrity-only, high-complexity issue rather than a broadly reachable critical flaw. No public exploit identified at time of analysis and no CISA KEV listing; vendor patches are downloadable for the 9.20 and 9.21 branches.
A malformed zone loaded into ISC BIND 9 authoritative servers can contain an NS or DNAME node above the zone origin, which named misinterprets as a zone cut, so queries for names inside the configured zone lose authoritative status and return out-of-zone delegations. Exploitation requires high privileges (PR:H) because the attacker must control the zone data delivered to the server, for example by controlling a primary from which the target secondary performs zone transfers; this is not a remotely unauthenticated attack. On servers that also provide recursion, BIND can follow the locally sourced cut and cache attacker-supplied data for names outside the configured zone, and the condition persists as long as the malformed zone remains in the zone database. No public exploit identified at time of analysis.
Web cache poisoning in WP Fastest Cache WordPress plugin before 1.5.1 enables unauthenticated attackers to inject content into the site-wide page cache by exploiting its failure to include tracking-related query parameters in cache key construction. Because the plugin caches responses to URLs containing these parameters under the canonical clean-URL key, an attacker-controlled page render is stored and subsequently served to every visitor of the legitimate URL. A publicly available proof-of-concept exploit exists; no active exploitation confirmed in CISA KEV at time of analysis.
Circuit soundness failure in Payy (polybase/payy) prior to 1.3.0 lets an authorized rollup prover smuggle an extra burn message into the public messages[1000] array accepted by RollupV1.verifyRollup(), causing the rollup contract to transfer USDC from the contract to an attacker-controlled recipient. The attacker must be a registered prover with the ability to construct a valid agg_final proof for an already-approved rollup block and to manipulate the unconstrained tail of the public input array, so the assessed vector is authenticated (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, integrity-only impact with no confidentiality or availability loss). Exploitability today is further limited because verifyRollup() is restricted to the existing allowlisted prover, but the flaw becomes effectively unauthenticated under the permissionless prover model in the Payy whitepaper (Section 3.3.2 stake-to-join and Section 3.3.1 fallback submission by other nodes). No public exploit code had been identified at time of analysis, and the vendor-released patch is version 1.3.0.
Remote code execution affects Dell Wyse Management Suite in all versions prior to WMS 5.5 HF1, stemming from the application's acceptance of extraneous untrusted data alongside trusted data (CWE-349). Per the provided CVSS vector (PR:N), a remote unauthenticated attacker could potentially achieve full code execution against the management server, though the Dell description text characterizes the actor as 'low privileged' - a discrepancy worth verifying. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Cache poisoning in PowerDNS Recursor allows a malicious or compromised authoritative DNS server to inject forged records by returning a crafted zone that the resolver ingests through its ZoneToCache feature. Because the poisoned data lands in the shared recursor cache, all downstream clients can be served attacker-controlled answers, enabling traffic redirection and spoofing. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; the CVSS 7.5 (high) rating reflects high integrity impact with a scope change but high attack complexity.
Local privilege escalation in Windows COM across Windows 10 (1809, 21H2, 22H2), Windows 11 (22H3-26H1), and Windows Server (2019-2025) allows unauthenticated attackers with local access to achieve full system compromise (high confidentiality, integrity, and availability impact) by exploiting acceptance of untrusted data alongside trusted data. CVSS 8.4 reflects the severe impact of complete privilege escalation despite requiring local access. Vendor-released patch available with specific build n
Arbitrary code execution in OpenClaw versions prior to 2026.3.24 enables local attackers to execute malicious code during npm package installation by crafting a malicious .npmrc file that overrides the git executable. When npm install runs in the staged package directory with git dependencies, the attacker-controlled .npmrc configuration triggers execution of arbitrary programs specified by the attacker. Exploitation requires user interaction to install the malicious plugin or hook locally. No public exploit identified at time of analysis.
Cache poisoning in Nuxt OG Image 6.2.5 through 6.6.x lets unauthenticated remote attackers overwrite the cached image slot used for a site's legitimate Open Graph image by submitting attacker-controlled rendering parameters (notably the 'title' value) alongside a derived cacheKey to the dynamic /_og/d/*.png route, so spoofed image content is then served to users and crawlers that request the poisoned URL. Both the module's own CVSS 4.0 vector (6.9, AV:N/AC:L/PR:N/UI:N/VI:L) and the independent assessment (CVSS 3.1, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) agree the impact is limited to integrity of served image content - no code execution, data theft, or availability loss - and that exploitation requires a runtime deployment where URL signing has not been configured. No public exploit code was identified at time of analysis and the issue is not listed as actively exploited, but a fixed release (6.7.0), the upstream commit, and the advisory are all public, so the technical details needed to reproduce the cache-key collision are openly documented. The independent assessment characterizes this as a genuine but moderate-severity integrity issue rather than a top-priority emergency.
Cache poisoning in GitLab CE/EE allows an authenticated user, on deployments running a specific caching configuration, to corrupt cached page content that is subsequently served to other users because cache keys are constructed improperly. Affected versions are all releases from 16.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 on both Community and Enterprise editions; exploitation requires a valid account (PR:L), a non-default deployment/caching setup, high attack complexity (AC:H), and victim interaction (UI:R), yielding only limited confidentiality, integrity, and availability impact (CVSS 4.6). No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV), so this is best treated as a low-priority, targeted-scenario issue rather than a broadly exploitable one.
BIND 9 secondary (slave) servers that restrict zone transfers with TSIG can be tricked into serving attacker-supplied zone contents: an attacker able to occupy or spoof the position of the configured primary can deliver a multi-message TCP IXFR whose final TSIG-signed message never arrives, and named commits and serves the records already received without rolling back to the pre-transfer state. Affected releases are BIND 9 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, and 9.21.0 through 9.21.25, along with the -S1 builds 9.11.3-S1 through 9.18.50-S1 and 9.20.9-S1 through 9.20.27-S1; no valid TSIG key is required (CVSS 3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L, 6.5), but exploitation is conditional on the attacker's network position and the multi-message IXFR condition, so this is an integrity-only, high-complexity issue rather than a broadly reachable critical flaw. No public exploit identified at time of analysis and no CISA KEV listing; vendor patches are downloadable for the 9.20 and 9.21 branches.
A malformed zone loaded into ISC BIND 9 authoritative servers can contain an NS or DNAME node above the zone origin, which named misinterprets as a zone cut, so queries for names inside the configured zone lose authoritative status and return out-of-zone delegations. Exploitation requires high privileges (PR:H) because the attacker must control the zone data delivered to the server, for example by controlling a primary from which the target secondary performs zone transfers; this is not a remotely unauthenticated attack. On servers that also provide recursion, BIND can follow the locally sourced cut and cache attacker-supplied data for names outside the configured zone, and the condition persists as long as the malformed zone remains in the zone database. No public exploit identified at time of analysis.
Web cache poisoning in WP Fastest Cache WordPress plugin before 1.5.1 enables unauthenticated attackers to inject content into the site-wide page cache by exploiting its failure to include tracking-related query parameters in cache key construction. Because the plugin caches responses to URLs containing these parameters under the canonical clean-URL key, an attacker-controlled page render is stored and subsequently served to every visitor of the legitimate URL. A publicly available proof-of-concept exploit exists; no active exploitation confirmed in CISA KEV at time of analysis.