Monthly
Cross-audience Google ID token reuse in the toolbox-core module of mcp-toolbox-sdk-python causes a credential intended for one service to be silently handed to a different service within the same process. Because the module-level token cache is not keyed by audience, an application that fetches ID tokens for two or more audiences in one process can send a Service A token to Service B; an attacker who operates, compromises, or passively monitors Service B can capture that token and replay it against Service A to impersonate the victim application. Exploitation is unauthenticated against the vulnerable app (PR:N) but conditional: it requires a multi-audience deployment plus attacker visibility into Service B traffic, and the leaked token is time-bounded by its expiry. No public exploit code has been identified at time of analysis, and the flaw is not confirmed as actively exploited (no CISA KEV listing).
Cross-user information disclosure in the http-cache-semantics npm library (through 4.2.0) allows unauthenticated attackers to retrieve cached HTTP responses belonging to other users from a shared cache. By re-requesting an identical URL with a large client-supplied Cache-Control: max-stale directive, an attacker can cause the library to serve cache entries that were deliberately security-zeroed - such as responses carrying Set-Cookie session credentials - instead of suppressing them. The vendor CVSS 4.0 score is 8.7 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H), while the independent assessment rates it CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, reflecting that real-world exploitation depends on a downstream shared-cache configuration that stores authenticated responses; the vendor advisory is available from VulnCheck. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Netty's HTTP CORS handler silently rewrites the Vary response header to Vary: Origin in releases before 4.1.137.Final and 4.2.17.Final, letting a shared caching proxy or CDN reuse authenticated, user-specific responses across users and leak sensitive data. Exposure is confined to deployments that install io.netty.handler.codec.http.cors.CorsHandler, also set their own Vary headers (such as Authorization or Cookie) for per-user caching, and sit behind a shared cache; because those three conditions must coincide, the assessed vector raises attack complexity to AC:H even though the published base score is 7.5 (AV:N/PR:N/UI:N/C:H). Publicly available exploit code exists (a public gist alongside the upstream fix PRs), but there is no evidence of active exploitation: the issue is not in CISA KEV, SSVC records Exploitation: none and Automatable: no, and EPSS is only 0.40% (33rd percentile), consistent with the assessment that real-world urgency is much lower than the headline score suggests.
Cross-user SSR payload disclosure in Nuxt 4.x allows unauthenticated network attackers to retrieve another authenticated user's full server-side rendered data by fetching `/<page>/_payload.json` after any authenticated user has warmed a cached route. The runtime `cache:nuxt:payload` storage introduced in nuxt 4.4.0 keyed payloads by URL path alone - omitting cookie, authorization header, or `cache.varies` dimensions - causing the renderer to serve one user's SSR data (including `useFetch`/`useAsyncData` results such as profile, tenant, billing, and token-like values) to any subsequent requester. No public exploit identified at time of analysis; vendor-released patch is available as nuxt@4.5.1.
Information disclosure in Regular Labs Articles Anywhere and Users Anywhere extensions for Joomla allows unauthenticated remote attackers to view content that should be expired or unpublished. Date-sensitive query caching generates cache keys lacking a bounded time component, so results cached during a valid period persist and can be served after content becomes unavailable. No active exploitation or public proof-of-concept has been identified, and EPSS indicates a low probability of widespread exploitation.
Information disclosure in multiple Regular Labs Joomla extensions allows unauthenticated visitors to retrieve administrator-only content indexed via Smart Search. Affected extensions include Articles Anywhere, Conditional Content, Modules Anywhere, ReReplacer, Sourcerer, Snippets Pro, and Tabs & Accordions Pro. No public exploit or active exploitation is known, and EPSS probability is low (0.19%).
Cross-context cache disclosure in Directus before 12.0.0 lets share-token holders and anonymous clients receive permission-filtered responses that were cached for a differently-scoped principal, because the cache key omits authorization context. When response caching is enabled, the key derived in api/src/utils/get-cache-key.ts covers only version, path, query, and accountability.user; since share tokens and anonymous requests both collapse to user null, requests to the same URL and query share a cache bucket and skip permission re-evaluation. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the flaw is a straightforward, config-dependent information-disclosure issue fixed in 12.0.0.
Web cache poisoning in the Ghost Node.js CMS before 6.37.0 lets an unauthenticated attacker inject an x-ghost-preview header that alters the rendered frontend response, which a shared caching layer then stores and serves to other visitors of the same page. When Ghost's public frontend and admin panel share a single domain, this request-specific preview output can be weaponized to hijack staff accounts; separate-domain deployments are not exposed. No public exploit is identified at time of analysis, and the issue carries a vendor CVSS of 9.6.
Information disclosure in @angular/common HttpTransferCache allows unauthenticated attackers to obtain other users' private data when Server-Side Rendering and hydration are enabled. The flaw stems from the cache failing to inspect the withCredentials flag or Cookie header, allowing credentialed responses to be serialized into SSR HTML and inadvertently shared via downstream CDN/reverse-proxy caches. No public exploit identified at time of analysis, but a vendor patch and detailed advisory describing the conditions are available.
Information disclosure in the Linux kernel's Intel Xe DRM graphics driver (drm/xe) allows a local user to read stale data from previously freed memory pages belonging to other processes. The xe_vm_madvise_ioctl() handler failed to reject PAT indices set to XE_COH_NONE (non-coherent) coherency mode on CPU-cached buffer objects, letting a GPU bypass dirty CPU caches and read sensitive content directly from DRAM before the kernel's page-clearing writeback completes. There is no public exploit identified at time of analysis, and EPSS rates exploitation probability at just 0.02%, consistent with a local, race-dependent leak rather than a widely weaponized flaw.
Cross-audience Google ID token reuse in the toolbox-core module of mcp-toolbox-sdk-python causes a credential intended for one service to be silently handed to a different service within the same process. Because the module-level token cache is not keyed by audience, an application that fetches ID tokens for two or more audiences in one process can send a Service A token to Service B; an attacker who operates, compromises, or passively monitors Service B can capture that token and replay it against Service A to impersonate the victim application. Exploitation is unauthenticated against the vulnerable app (PR:N) but conditional: it requires a multi-audience deployment plus attacker visibility into Service B traffic, and the leaked token is time-bounded by its expiry. No public exploit code has been identified at time of analysis, and the flaw is not confirmed as actively exploited (no CISA KEV listing).
Cross-user information disclosure in the http-cache-semantics npm library (through 4.2.0) allows unauthenticated attackers to retrieve cached HTTP responses belonging to other users from a shared cache. By re-requesting an identical URL with a large client-supplied Cache-Control: max-stale directive, an attacker can cause the library to serve cache entries that were deliberately security-zeroed - such as responses carrying Set-Cookie session credentials - instead of suppressing them. The vendor CVSS 4.0 score is 8.7 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H), while the independent assessment rates it CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, reflecting that real-world exploitation depends on a downstream shared-cache configuration that stores authenticated responses; the vendor advisory is available from VulnCheck. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Netty's HTTP CORS handler silently rewrites the Vary response header to Vary: Origin in releases before 4.1.137.Final and 4.2.17.Final, letting a shared caching proxy or CDN reuse authenticated, user-specific responses across users and leak sensitive data. Exposure is confined to deployments that install io.netty.handler.codec.http.cors.CorsHandler, also set their own Vary headers (such as Authorization or Cookie) for per-user caching, and sit behind a shared cache; because those three conditions must coincide, the assessed vector raises attack complexity to AC:H even though the published base score is 7.5 (AV:N/PR:N/UI:N/C:H). Publicly available exploit code exists (a public gist alongside the upstream fix PRs), but there is no evidence of active exploitation: the issue is not in CISA KEV, SSVC records Exploitation: none and Automatable: no, and EPSS is only 0.40% (33rd percentile), consistent with the assessment that real-world urgency is much lower than the headline score suggests.
Cross-user SSR payload disclosure in Nuxt 4.x allows unauthenticated network attackers to retrieve another authenticated user's full server-side rendered data by fetching `/<page>/_payload.json` after any authenticated user has warmed a cached route. The runtime `cache:nuxt:payload` storage introduced in nuxt 4.4.0 keyed payloads by URL path alone - omitting cookie, authorization header, or `cache.varies` dimensions - causing the renderer to serve one user's SSR data (including `useFetch`/`useAsyncData` results such as profile, tenant, billing, and token-like values) to any subsequent requester. No public exploit identified at time of analysis; vendor-released patch is available as nuxt@4.5.1.
Information disclosure in Regular Labs Articles Anywhere and Users Anywhere extensions for Joomla allows unauthenticated remote attackers to view content that should be expired or unpublished. Date-sensitive query caching generates cache keys lacking a bounded time component, so results cached during a valid period persist and can be served after content becomes unavailable. No active exploitation or public proof-of-concept has been identified, and EPSS indicates a low probability of widespread exploitation.
Information disclosure in multiple Regular Labs Joomla extensions allows unauthenticated visitors to retrieve administrator-only content indexed via Smart Search. Affected extensions include Articles Anywhere, Conditional Content, Modules Anywhere, ReReplacer, Sourcerer, Snippets Pro, and Tabs & Accordions Pro. No public exploit or active exploitation is known, and EPSS probability is low (0.19%).
Cross-context cache disclosure in Directus before 12.0.0 lets share-token holders and anonymous clients receive permission-filtered responses that were cached for a differently-scoped principal, because the cache key omits authorization context. When response caching is enabled, the key derived in api/src/utils/get-cache-key.ts covers only version, path, query, and accountability.user; since share tokens and anonymous requests both collapse to user null, requests to the same URL and query share a cache bucket and skip permission re-evaluation. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the flaw is a straightforward, config-dependent information-disclosure issue fixed in 12.0.0.
Web cache poisoning in the Ghost Node.js CMS before 6.37.0 lets an unauthenticated attacker inject an x-ghost-preview header that alters the rendered frontend response, which a shared caching layer then stores and serves to other visitors of the same page. When Ghost's public frontend and admin panel share a single domain, this request-specific preview output can be weaponized to hijack staff accounts; separate-domain deployments are not exposed. No public exploit is identified at time of analysis, and the issue carries a vendor CVSS of 9.6.
Information disclosure in @angular/common HttpTransferCache allows unauthenticated attackers to obtain other users' private data when Server-Side Rendering and hydration are enabled. The flaw stems from the cache failing to inspect the withCredentials flag or Cookie header, allowing credentialed responses to be serialized into SSR HTML and inadvertently shared via downstream CDN/reverse-proxy caches. No public exploit identified at time of analysis, but a vendor patch and detailed advisory describing the conditions are available.
Information disclosure in the Linux kernel's Intel Xe DRM graphics driver (drm/xe) allows a local user to read stale data from previously freed memory pages belonging to other processes. The xe_vm_madvise_ioctl() handler failed to reject PAT indices set to XE_COH_NONE (non-coherent) coherency mode on CPU-cached buffer objects, letting a GPU bypass dirty CPU caches and read sensitive content directly from DRAM before the kernel's page-clearing writeback completes. There is no public exploit identified at time of analysis, and EPSS rates exploitation probability at just 0.02%, consistent with a local, race-dependent leak rather than a widely weaponized flaw.