3630 matches found
CVE-2026-64430
CVE-2026-64430 affects the Linux kernel NTB EPF subsystem. ntb_epf_vec_isr previously called pci_irq_vector() in hardirq context, and pci_irq_vector() may call msi_get_virq() which takes a mutex and can trigger scheduling while atomic. The fix caches the Linux IRQ number for vector 0 when vectors...
CVE-2026-64430 NTB: epf: Avoid calling pci_irq_vector() from hardirq context
In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid calling pciirqvector from hardirq context ntbepfvecisr calls pciirqvector in hardirq context to derive the vector number. pciirqvector calls msigetvirq that takes a mutex and can therefore trigger "scheduling whil...
Cache Confusion
Next.js is vulnerable to Cache Confusion. The vulnerability is due to improper caching of server-side fetch responses, where cached response bodies may be reused across requests with different request bodies, allowing confidential data from one request to be exposed to unauthorized users...
Sensitive Information Exposure
Next.js is vulnerable to Sensitive Information Exposure. The vulnerability is due to improper caching of server-side fetch responses for non-UTF-8 request bodies, where different request bodies can share the same cache entry, allowing confidential response data to be exposed to unauthorized...
Linux Distros Unpatched Vulnerability : CVE-2026-39155
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - Knot DNS before 3.4.10 and 3.5.x before 3.5.4 contains a vulnerability in mod-onlinesign where the next NSEC owner name can be computed incorrectly. This can...
kernel: ipv6: fix possible UAF in icmpv6_rcv()
A flaw was found in the Linux kernel's IPv6 Internet Protocol version 6 implementation. This vulnerability, a Use-After-Free UAF error, occurs due to incorrect caching of network packet addresses before a memory operation. An attacker could potentially exploit this flaw to cause memory corruption...
CVE-2026-39155
Knot DNS before 3.4.10 and 3.5.x before 3.5.4 contains a vulnerability in mod-onlinesign where the next NSEC owner name can be computed incorrectly. This can create an overly broad authenticated denial interval, allowing downstream validating resolvers using aggressive negative caching to...
CVE-2026-65755
Joomla Extension - regularlabs.com - Date-sensitive query-cache leakage in Articles Anywhere and Users Anywhere extension - Date-sensitive query cache keys did not retain a bounded time component. Cached results could remain active across future publication or expiry boundaries, potentially...
CVE-2026-65755
Joomla Extension - regularlabs.com - Date-sensitive query-cache leakage in Articles Anywhere and Users Anywhere extension - Date-sensitive query cache keys did not retain a bounded time component. Cached results could remain active across future publication or expiry boundaries, potentially...
CVE-2026-39155
Knot DNS before 3.4.10 and 3.5.x before 3.5.4 contains a vulnerability in mod-onlinesign where the next NSEC owner name can be computed incorrectly. This can create an overly broad authenticated denial interval, allowing downstream validating resolvers using aggressive negative caching to...
CVE-2026-39155
Knot DNS before 3.4.10 and 3.5.x before 3.5.4 contains a vulnerability in mod-onlinesign where the next NSEC owner name can be computed incorrectly. This can create an overly broad authenticated denial interval, allowing downstream validating resolvers using aggressive negative caching to...
CVE-2026-39155
Knot DNS before 3.4.10 and 3.5.x before 3.5.4 contains a vulnerability in mod-onlinesign where the next NSEC owner name can be computed incorrectly. This can create an overly broad authenticated denial interval, allowing downstream validating resolvers using aggressive negative caching to...
CVE-2026-39155
Knot DNS before 3.4.10 and 3.5.x before 3.5.4 contains a vulnerability in mod-onlinesign where the next NSEC owner name can be computed incorrectly. This can create an overly broad authenticated denial interval, allowing downstream validating resolvers using aggressive negative caching to...
Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
Impact A server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This is only an issu...
unbound: Unbound: Cache poisoning via insufficient RRSIG.Labels validation and premature cache writes
A flaw was found in Unbound. Insufficient validation of the RRSIG.Labels field, combined with premature cache writes during RFC 8198 aggressive NSEC processing, can lead to cache poisoning. This vulnerability allows a malicious actor, controlling a single delegated zone, to poison arbitrary sibli...
Improper Authorization
PraisonAI is vulnerable to Improper Authorization. The vulnerability is due to caching tool approval decisions by tool name instead of validating each invocation and its arguments, allowing attackers to reuse a previously approved tool to perform unauthorized operations with arbitrary parameters,...
EUVD-2026-41636
Gitea: Cached Per-Branch Permission Check in Pre-Receive Hook Allows Full Repository Write...
EUVD-2026-46361
SoupAuthManager caches proxy authentication credentials without scoping them to the proxy authority host:port. When the proxy configuration changes e.g., via system settings or WPAD, cached Proxy-Authorization headers from the previous proxy are sent to the new proxy, leaking credentials...
AZL-93237 CVE-2026-12547 affecting package libsoup 3.4.4-16
SoupAuthManager caches proxy authentication credentials without scoping them to the proxy authority host:port. When the proxy configuration changes e.g., via system settings or WPAD, cached Proxy-Authorization headers from the previous proxy are sent to the new proxy, leaking credentials...
CVE-2026-12547
SoupAuthManager caches proxy authentication credentials without scoping them to the proxy authority host:port. When the proxy configuration changes e.g., via system settings or WPAD, cached Proxy-Authorization headers from the previous proxy are sent to the new proxy, leaking credentials...