Monthly
Kids Mode on Vivo devices exposes local gallery photos through a control logic defect in a specific built-in webpage, bypassing the sandboxed environment's access restrictions. All versions of Vivo Kids Mode are affected per the wildcard CPE (cpe:2.3:a:vivo:kids_mode:*:*:*:*:*:*:*:*). Exploitation requires physical access to the device; no public exploit code and no CISA KEV listing exist at time of analysis.
Namespace isolation bypass in Traefik's Kubernetes CRD provider allows a tenant confined by RBAC to a single namespace to bind their own router to a `TraefikService` owned by a different namespace, exposing or rerouting that namespace's backend services - defeating the isolation boundary that `allowCrossNamespace=false` (the default) is meant to enforce. All Traefik v2 releases through 2.11.53, v3.0.0-3.6.24, and v3.7.0-3.7.9 are affected; patches are available at v2.11.54, v3.6.25, and v3.7.10. A proof-of-concept test harness accompanies the advisory confirming the bypass; the vulnerability has not been added to CISA KEV at time of analysis.
Privilege escalation via dynamic client registration in malach-it's Boruta OAuth 2.0/OpenID Connect provider library (Elixir) lets an unauthenticated registrant create OIDC clients that carry administrative security attributes. Because Boruta.Openid.register_client/3 forwards caller-supplied parameters straight into the administrative client-creation changeset with no public/admin allowlist, a self-registering client can dictate its own supported grant types, authorized scopes, PKCE enforcement, public refresh/revocation behavior, token lifetimes, and signing settings on versions 2.3.0 through 2.3.6. There is no public exploit identified at time of analysis and it is not in CISA KEV, but a vendor-released patch (2.3.7) is available.
Remote code execution in Apache Syncope's connector subsystem allows an administrator holding sufficient entitlements to run arbitrary Groovy scripts through scripted REST and SQL connectors, escaping the intended sandbox and executing code on the host. It affects Syncope 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.6, and 4.1.0-M0 through 4.1.1, and is rooted in improper isolation (CWE-653) of the scripting engine. Although the published CVSS is 9.8, the vendor description states an authenticated privileged administrator is required, and there is no public exploit identified at time of analysis.
Remote code execution in Apache Syncope's workflow engine lets an administrator holding sufficient entitlements run arbitrary Groovy code on the server by importing and starting a malicious BPMN process definition through the REST API. Because Flowable's Groovy scriptTasks execute with no sandbox in affected 3.0.x, 4.0.x, and 4.1.x releases, script code embedded in the process runs directly with the privileges of the Syncope core JVM. No public exploit has been identified at time of analysis and the flaw is not in CISA KEV, but the trivial exploitation path once an entitled admin account is reached makes it a strong candidate for post-compromise abuse and insider misuse.
Groovy sandbox escape in Apache Syncope's Implementations feature lets an administrator holding Implementation entitlements author a malicious Groovy class that runs untrusted code outside the intended security sandbox, effectively achieving arbitrary code execution on the identity-management server. It affects Syncope 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.6, and 4.1.0-M0 through 4.1.1. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the published CVSS of 9.8 overstates real-world exposure because the flaw requires a privileged administrator account.
Incorrect listener-rule priority ordering in AWS Load Balancer Controller before v3.4.2 enables authenticated Kubernetes users to intercept, spoof, or deny gRPC traffic belonging to other namespaces on a shared Gateway. The controller incorrectly assigned ALB listener rule priority by route kind (HTTPRoute vs GRPCRoute) rather than route specificity, causing all HTTPRoutes to be evaluated before GRPCRoutes at the ALB layer regardless of which was more specific or narrower in scope. No public exploit has been identified at time of analysis, but the SSVC framework rates technical impact as total for the subsequent system, reflecting that cross-namespace traffic confidentiality, integrity, and availability are fully compromised when conditions are met.
Insufficient compartmentalization in the Imagination Technologies Graphics DDK kernel module enables a local, low-privileged attacker to abuse shared secure GPU memory allocations to either covertly pass data between otherwise isolated secure GPU processes or disrupt a peer process, causing image corruption and GPU hardware recovery events. Multiple DDK release trains spanning versions 1.18 RTM through 26.1 RTM are confirmed affected per EUVD-2026-36606. No public exploit exists and SSVC confirms no observed exploitation, but the 'Information Disclosure' tag in the advisory signals a confidentiality dimension that the official CVSS C:N metric does not fully capture.
Code execution via Groovy sandbox bypass in Apache Syncope 3.0 through 3.0.16, 4.0 through 4.0.5, and 4.1.0 allows a high-privileged administrator holding Implementations entitlements to run untrusted code outside the sandbox. By placing payload logic in a Groovy class static initializer, the attacker reaches a non-sandboxed execution path, yielding full confidentiality, integrity, and availability impact. No public exploit identified at time of analysis, and EPSS is very low (0.02%, 6th percentile), consistent with a privilege-gated, not mass-scanned, issue.
Spring gRPC 1.0.0 through 1.0.2 inherits authenticated user identity on gRPC worker threads after access denial, allowing a subsequent unauthenticated request on the same thread to gain escalated permissions. The vulnerability requires an authenticated attacker with prior knowledge of thread reuse patterns and affects only configurations where both authenticated and unauthenticated requests share gRPC worker threads. A patch is available in version 1.0.3.
Kids Mode on Vivo devices exposes local gallery photos through a control logic defect in a specific built-in webpage, bypassing the sandboxed environment's access restrictions. All versions of Vivo Kids Mode are affected per the wildcard CPE (cpe:2.3:a:vivo:kids_mode:*:*:*:*:*:*:*:*). Exploitation requires physical access to the device; no public exploit code and no CISA KEV listing exist at time of analysis.
Namespace isolation bypass in Traefik's Kubernetes CRD provider allows a tenant confined by RBAC to a single namespace to bind their own router to a `TraefikService` owned by a different namespace, exposing or rerouting that namespace's backend services - defeating the isolation boundary that `allowCrossNamespace=false` (the default) is meant to enforce. All Traefik v2 releases through 2.11.53, v3.0.0-3.6.24, and v3.7.0-3.7.9 are affected; patches are available at v2.11.54, v3.6.25, and v3.7.10. A proof-of-concept test harness accompanies the advisory confirming the bypass; the vulnerability has not been added to CISA KEV at time of analysis.
Privilege escalation via dynamic client registration in malach-it's Boruta OAuth 2.0/OpenID Connect provider library (Elixir) lets an unauthenticated registrant create OIDC clients that carry administrative security attributes. Because Boruta.Openid.register_client/3 forwards caller-supplied parameters straight into the administrative client-creation changeset with no public/admin allowlist, a self-registering client can dictate its own supported grant types, authorized scopes, PKCE enforcement, public refresh/revocation behavior, token lifetimes, and signing settings on versions 2.3.0 through 2.3.6. There is no public exploit identified at time of analysis and it is not in CISA KEV, but a vendor-released patch (2.3.7) is available.
Remote code execution in Apache Syncope's connector subsystem allows an administrator holding sufficient entitlements to run arbitrary Groovy scripts through scripted REST and SQL connectors, escaping the intended sandbox and executing code on the host. It affects Syncope 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.6, and 4.1.0-M0 through 4.1.1, and is rooted in improper isolation (CWE-653) of the scripting engine. Although the published CVSS is 9.8, the vendor description states an authenticated privileged administrator is required, and there is no public exploit identified at time of analysis.
Remote code execution in Apache Syncope's workflow engine lets an administrator holding sufficient entitlements run arbitrary Groovy code on the server by importing and starting a malicious BPMN process definition through the REST API. Because Flowable's Groovy scriptTasks execute with no sandbox in affected 3.0.x, 4.0.x, and 4.1.x releases, script code embedded in the process runs directly with the privileges of the Syncope core JVM. No public exploit has been identified at time of analysis and the flaw is not in CISA KEV, but the trivial exploitation path once an entitled admin account is reached makes it a strong candidate for post-compromise abuse and insider misuse.
Groovy sandbox escape in Apache Syncope's Implementations feature lets an administrator holding Implementation entitlements author a malicious Groovy class that runs untrusted code outside the intended security sandbox, effectively achieving arbitrary code execution on the identity-management server. It affects Syncope 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.6, and 4.1.0-M0 through 4.1.1. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the published CVSS of 9.8 overstates real-world exposure because the flaw requires a privileged administrator account.
Incorrect listener-rule priority ordering in AWS Load Balancer Controller before v3.4.2 enables authenticated Kubernetes users to intercept, spoof, or deny gRPC traffic belonging to other namespaces on a shared Gateway. The controller incorrectly assigned ALB listener rule priority by route kind (HTTPRoute vs GRPCRoute) rather than route specificity, causing all HTTPRoutes to be evaluated before GRPCRoutes at the ALB layer regardless of which was more specific or narrower in scope. No public exploit has been identified at time of analysis, but the SSVC framework rates technical impact as total for the subsequent system, reflecting that cross-namespace traffic confidentiality, integrity, and availability are fully compromised when conditions are met.
Insufficient compartmentalization in the Imagination Technologies Graphics DDK kernel module enables a local, low-privileged attacker to abuse shared secure GPU memory allocations to either covertly pass data between otherwise isolated secure GPU processes or disrupt a peer process, causing image corruption and GPU hardware recovery events. Multiple DDK release trains spanning versions 1.18 RTM through 26.1 RTM are confirmed affected per EUVD-2026-36606. No public exploit exists and SSVC confirms no observed exploitation, but the 'Information Disclosure' tag in the advisory signals a confidentiality dimension that the official CVSS C:N metric does not fully capture.
Code execution via Groovy sandbox bypass in Apache Syncope 3.0 through 3.0.16, 4.0 through 4.0.5, and 4.1.0 allows a high-privileged administrator holding Implementations entitlements to run untrusted code outside the sandbox. By placing payload logic in a Groovy class static initializer, the attacker reaches a non-sandboxed execution path, yielding full confidentiality, integrity, and availability impact. No public exploit identified at time of analysis, and EPSS is very low (0.02%, 6th percentile), consistent with a privilege-gated, not mass-scanned, issue.
Spring gRPC 1.0.0 through 1.0.2 inherits authenticated user identity on gRPC worker threads after access denial, allowing a subsequent unauthenticated request on the same thread to gain escalated permissions. The vulnerability requires an authenticated attacker with prior knowledge of thread reuse patterns and affects only configurations where both authenticated and unauthenticated requests share gRPC worker threads. A patch is available in version 1.0.3.