Denial Of Service
Monthly
Sandbox escape in Google Chrome's Media component on Windows (versions prior to 151.0.7922.109) lets a remote attacker break out of the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and CVSS 9.6 because a successful escape yields full confidentiality, integrity, and availability impact beyond the sandboxed process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though Chrome UAF media bugs are historically attractive targets.
Sandbox escape in Google Chrome for Android before 151.0.7922.109 stems from a use-after-free in the WebGL graphics component (CWE-416), letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Chromium rates this Critical and CVSS scores it 9.6 with a scope change (S:C), reflecting the cross-boundary sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but Chrome WebGL memory-corruption bugs are historically high-value exploitation targets.
Sandbox escape in Google Chrome's Web Authentication (WebAuthn) component before 151.0.7922.109 lets a remote attacker who lures a victim to a crafted HTML page corrupt memory via a use-after-free and potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 (scope-changed), it affects the vast installed base of desktop Chrome; Google has shipped a fixed Stable-channel build. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Use-after-free in the Chrome Extensions subsystem allows sandboxed arbitrary code execution in Google Chrome prior to 151.0.7922.109, requiring a victim to install a crafted malicious extension. The UAF (CWE-416) memory corruption condition is exploitable remotely but demands high attack complexity and active user interaction, resulting in code execution confined within Chrome's sandbox. No public exploit code or CISA KEV listing has been identified at time of analysis; Google has released a fix in the stable channel update of 01 August 2026.
Use-after-free exploitation in Google Chrome's Media component on Windows enables sandbox escape for attackers who have already compromised the renderer process. Chrome versions prior to 151.0.7922.109 on Windows are affected, with a crafted HTML page serving as the trigger mechanism to corrupt freed memory and break out of the renderer sandbox. SSVC rates current exploitation as none and non-automatable, though the total technical impact class reflects full OS-level compromise if the two-stage attack chain is completed successfully.
Use-after-free in the Views UI rendering component of Google Chrome (all versions prior to 151.0.7922.109) enables a remote attacker to corrupt heap memory via a crafted HTML page, requiring the victim to perform specific UI gestures. The CVSS:3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a fully network-delivered attack with no authentication barrier, though high attack complexity and mandatory user interaction substantially reduce opportunistic exploitation likelihood. No public exploit code or CISA KEV listing has been identified at time of analysis; Google rated this High severity internally and shipped a patch in the stable channel update.
Use-after-free in Google Chrome's Views UI framework on Windows, fixed in version 151.0.7922.109, exposes users to heap corruption with full confidentiality, integrity, and availability impact. Exploitation requires convincing a target to perform specific UI gestures while visiting a crafted HTML page, making this a social-engineering-dependent but high-consequence flaw. No public exploit code or CISA KEV listing has been identified at the time of analysis; however, the severity and platform breadth make patching urgent for Windows enterprise fleets.
Use-after-free in the Payments component of Google Chrome prior to 151.0.7922.109 enables a sandbox escape when an attacker has already compromised the renderer process. Exploitation requires chaining a prior renderer compromise with delivery of a crafted HTML page, placing this firmly in the category of multi-stage browser exploitation. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and SSVC classifies exploitation status as none, though the technical impact is rated total due to the full sandbox escape capability.
Sandbox escape in Google Chrome on Android (prior to 151.0.7922.109) via a use-after-free vulnerability in the Skia graphics library allows a remote attacker who has already compromised the renderer process to break out of Chrome's sandbox through a crafted HTML page. The CVSS vector (S:C, C:H/I:H/A:H) confirms full cross-boundary compromise, elevating an attacker from renderer-level code execution to broader Android OS access. No active exploitation is confirmed at time of analysis (SSVC exploitation: none; not listed in CISA KEV), though Technical Impact is rated total by CISA's SSVC framework.
Remote code execution within the Chrome sandbox is possible in Google Chrome versions prior to 151.0.7922.109 due to a use-after-free vulnerability in the V8 JavaScript engine, triggerable by a remote attacker through a specially crafted HTML page. The attacker achieves arbitrary code execution confined to the Chrome renderer sandbox, requiring no privileges but necessitating user interaction to visit a malicious page. Google has released a fix in version 151.0.7922.109; SSVC assessment confirms no known active exploitation at time of analysis, and no public exploit code has been identified.
Sandbox escape in Google Chrome for Linux (versions before 151.0.7922.109) stems from a use-after-free in the Aura windowing subsystem, letting a remote attacker who lures a victim to a crafted HTML page corrupt memory and potentially break out of the renderer sandbox. Google rated the Chromium severity Critical (CVSS 9.6, scope-changed), but there is no public exploit identified at time of analysis and CISA's SSVC framework records exploitation status as 'none'. Because a full sandbox escape gives attacker code the privileges of the browser process on the host, this is a high-priority patch despite the absence of observed exploitation.
Sandbox escape in Google Chrome's Aura display layer on Linux allows a remote attacker with an already-compromised renderer process to break out of the Chrome sandbox via a crafted HTML page, achieving full system-level code execution. Affected versions are all Chrome builds prior to 151.0.7922.109 on Linux. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS scope-changed rating (S:C) and High across C/I/A reflect the severe post-exploitation impact of a successful sandbox escape in a privileged browser context.
Use-after-free in Google Chrome's Translate component (versions prior to 151.0.7922.109) enables remote attackers to execute arbitrary code within the browser's renderer sandbox by directing a user to a crafted HTML page. The CVSS 8.8 score reflects network-accessible, low-complexity exploitation gated only by a single user interaction - visiting an attacker-controlled page. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE primitive within one of the world's most widely deployed browsers represents a materially significant attack surface.
Use-after-free in Google Chrome's HTML engine (all versions prior to 151.0.7922.109) exposes users to potential heap corruption and code execution when they visit a crafted HTML page. The CVSS 8.8 score reflects unauthenticated, network-reachable exploitation requiring only a single user interaction - consistent with Chromium's own 'High' severity classification. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch (151.0.7922.109) has been released and is the primary mitigation.
Heap corruption via use-after-free in Google Chrome's Views UI framework (prior to 151.0.7922.109) can be triggered by a remote attacker who delivers a crafted HTML page and induces a user to perform specific UI gestures. Successful exploitation may lead to arbitrary code execution or denial of service within the browser process. No public exploit code or CISA KEV listing has been identified at time of analysis, and the CVSS AC:H rating signals non-trivial exploitation conditions that reduce real-world risk compared to the high severity label.
Use-after-free in Chrome's Resources component on Android enables sandbox escape for attackers who have already established a foothold in the renderer process. Affected versions are all Chrome for Android releases prior to 151.0.7922.109. The CVSS scope change (S:C) and High ratings across Confidentiality, Integrity, and Availability confirm that successful exploitation breaks out of the browser sandbox, exposing the underlying Android OS. No public exploit code or CISA KEV listing exists at time of analysis, though the chained exploit capability (renderer-to-sandbox-escape) represents a critical capability for advanced threat actors.
Sandbox escape via GPU use-after-free in Google Chrome prior to 151.0.7922.109 enables a remote attacker who has already compromised the renderer process to break out of the Chromium sandbox by delivering a crafted HTML page. The vulnerability resides in Chrome's GPU component and, if successfully chained after an initial renderer compromise, yields full confidentiality, integrity, and availability impact on the host system. No public exploit code has been identified at the time of analysis, and SSVC classifies exploitation status as none with automatable set to no, indicating no evidence of active or mass exploitation.
Use-after-free in the WebGL subsystem of Google Chrome for Android (prior to 151.0.7922.109) enables sandbox escape for an attacker who has already achieved renderer-process compromise. By directing a victim to a crafted HTML page, an adversary with existing renderer access can exploit freed memory corruption in WebGL to break out of Chrome's sandbox and reach OS-level execution on the Android device. No public exploit code or active exploitation has been identified; SSVC rates exploitation as none and automatable as no, though technical impact is assessed as total given the full scope change.
Heap corruption via mismatched memory management in llama.cpp's LLaMA-Android JNI wrapper affects builds b1886 through b7445, where new_1batch() allocates memory with malloc() but free_1batch() releases it using the C++ delete operator, triggering undefined behavior and heap metadata corruption. This mismatch guarantees denial of service via process crash and, depending on allocator state, may enable arbitrary code execution within the affected Android application process. No public exploit code has been confirmed and the vulnerability is not listed in CISA KEV; a vendor-released patch exists as build b7446.
CPU exhaustion via quadratic regex backtracking in rrrene/html_sanitize_ex, an Elixir HTML sanitization library, allows unauthenticated remote attackers to saturate the BEAM scheduler pool and render applications unresponsive. The CSS scrubber's declaration regex applies an unbounded greedy quantifier on the property-name token; a crafted 80 KB style body containing no valid CSS colon costs approximately 2.4 seconds of scheduler time per request, meaning a handful of concurrent requests fully deny service. Affected versions span 0.3.1 through 1.5.2 inclusive; impact is strictly availability — no confidentiality or integrity loss occurs. No public exploit or CISA KEV listing is identified at time of analysis.
Unauthenticated remote shutdown of OpenChamber 1.11.7 is possible by sending a single POST request to /api/system/shutdown, terminating the server process and instantly denying service to all active AI coding sessions. The flaw stems from the /api/system/shutdown route being registered before the authentication middleware in the Express handler chain within bootstrap-runtime.js, meaning authentication is never evaluated for that endpoint regardless of whether UI_PASSWORD is configured. No public exploit code or CISA KEV listing has been identified at time of analysis, though the attack requires no privileges or user interaction and is trivially reproducible against any network-exposed instance.
Deserialization-before-authentication in aiosend's WebhookHandler exposes all webhook integrations prior to version 3.0.7 to pre-authentication denial-of-service. An unauthenticated remote attacker can submit arbitrarily large or complex JSON payloads to any reachable aiosend webhook endpoint, forcing a full Pydantic model deserialization pass - including retention of attacker-supplied extra fields in memory due to CryptoPayObject's extra='allow' configuration - before the HMAC signature is checked and the request is rejected. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the attack requires no credentials and minimal skill.
Resource exhaustion via crafted DNS packet affects PowerDNS Authoritative Server, Recursor, and dnsdist, allowing remote unauthenticated attackers to degrade or deny DNS service by sending specially crafted DNS packets that trigger abnormal memory and CPU consumption. The vulnerability spans all three major PowerDNS software components, significantly broadening the attack surface for operators running mixed PowerDNS environments. No public exploit identified at time of analysis, and the flaw is not listed in the CISA KEV catalog, but the low exploitation barrier - any network-reachable DNS query - makes patching urgent for internet-facing DNS infrastructure.
Unauthenticated remote denial of service in LightFTP through version 2.4 exploits multiple data race conditions in ftpserv.c via the LIST/ABOR command sequence. The control thread closes shared data_socket and file_fd descriptors while worker threads concurrently reference the same fields in worker_thread_cleanup, enabling the OS to reassign stale descriptors to unrelated resources and producing undefined behavior. A publicly available proof-of-concept exists (GitHub issue #75); exploitation has not been confirmed in the wild (not in CISA KEV), but the unauthenticated attack surface and CVSS 4.0 score of 8.2 elevate urgency for exposed deployments.
Memory exhaustion denial-of-service in Sonic 3 A.I.R.'s UDP networking stack allows unauthenticated remote attackers to crash the multiplayer server process with a single crafted packet. The root cause is in ReceivedPacketCache::enqueuePacket() within the OxygenEngine netcore layer: the mUniquePacketID field is read directly from the UDP wire format without bounds validation, and when set to UINT32_MAX the server attempts to allocate one CacheItem per missing packet ID gap, exhausting host memory until an uncaught std::bad_alloc propagates to std::terminate(). No public exploit code and no CISA KEV listing exist at time of analysis, but the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H, score 8.7) reflects that the attack is trivially automatable from any network-reachable position.
Unsafe deserialization in Apache CXF's JMS transport allows any party able to publish to the service's JMS destination to achieve denial of service or, where a compatible deserialization gadget chain is present on the application classpath, remote code execution within the CXF process. All Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 are affected when the JMS transport is in use. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability class (CWE-502 with unrestricted ObjectInputStream) is well-understood and tooling such as ysoserial makes it routinely exploitable wherever gadget libraries are present.
Denial of service persists in Apache CXF due to an incomplete remediation of CVE-2026-50645, allowing unauthenticated network attackers to exhaust server resources by submitting messages containing an excessive number of MIME attachment headers. All Apache CXF deployments running versions prior to 4.2.3, 4.1.8, or 3.6.12 remain vulnerable despite having applied the prior patch. No public exploit code or active exploitation has been identified at time of analysis, but the bypass-of-fix nature of this vulnerability means any organization that patched CVE-2026-50645 and considered itself remediated must re-patch.
Uncontrolled resource consumption in Apache CXF's JAX-RS form parameter processing enables remote denial-of-service attacks against any exposed endpoint accepting form-encoded requests. The framework provides a 'maxFormParameterCount' configuration knob but sets no default ceiling, meaning unpatched deployments will parse arbitrarily large parameter sets until memory or CPU is exhausted. Fixed versions (4.2.3, 4.1.8, and 3.6.12) enforce a default cap of 500 parameters; no public exploit or CISA KEV listing has been identified at time of analysis.
Unbounded attachment ingestion in Apache CXF enables remote denial-of-service against any endpoint that processes multipart messages. Versions prior to 4.2.3, 4.1.8, and 3.6.12 imposed no default ceiling on the 'attachment-max-size' parameter, allowing attackers to exhaust server memory or processing capacity by submitting arbitrarily large attachments. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the low attack complexity makes this a realistic threat for internet-exposed CXF deployments.
Kernel crash vulnerability in the Linux SMB client subsystem results from a type mismatch in smb2_aead_req_alloc() where an unsigned 32-bit integer is incorrectly passed to ERR_PTR(), generating an invalid error pointer that causes a system panic upon dereference. Systems running the Linux kernel with the SMB client module (cifs) and SMBv2/v3 AEAD encryption enabled are affected across multiple stable branches, with patches available in versions 6.6.145, 6.12.96, 6.18.39, 7.1.4, and 7.2-rc1. No public exploit code exists and no CISA KEV listing applies; EPSS probability is extremely low at 0.16% (5th percentile), indicating this is primarily a kernel reliability fix with negligible active exploitation interest despite the high official CVSS score.
Use-after-free race condition in the Linux kernel brcmfmac Broadcom WiFi driver enables adjacent-network attackers to corrupt kernel memory during concurrent device removal and bus_reset work execution. Affected systems include any Linux host running brcmfmac on PCIe, SDIO, or USB Broadcom chipsets - including Raspberry Pi devices - on kernel versions since 5.2 through pre-7.1.6. No public exploit or CISA KEV listing exists at time of analysis, and EPSS probability is low at 0.14% (4th percentile), though the kernel-level impact class remains high.
Unbounded memory growth in GStreamer's RTP H.264 and H.265 depayloader elements allows a remote unauthenticated attacker to exhaust process memory and terminate any application consuming RTP video streams. The rtph264depay and rtph265depay elements in gst-plugins-good lack an upper bound on their internal reassembly buffer, meaning an attacker who continuously sends fragmented RTP packets while withholding the end-of-fragment marker can grow that buffer without limit. No public exploit has been identified at time of analysis, and CISA KEV listing is absent, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is trivially exploitable against any exposed GStreamer RTP pipeline.
NULL pointer dereference in HDF5's H5Pget_fill_value function (all versions before 2.1.1) enables denial of service by processing a specially crafted HDF5 dataset file. The flaw arises when a fill value message (format version 1 or 2) carries the 'defined' flag alongside a negative size field - a malformed state the library fails to normalize to its internal 'undefined' sentinel - allowing a NULL datatype pointer to reach H5T_path_find and crash the process. No public exploit identified at time of analysis; the CVSS 4.0 score of 8.2 reflects high availability impact, but the local file-parsing vector and user interaction requirement meaningfully constrain real-world exposure.
Unauthenticated remote denial-of-service in Nuxt's island/server-component SSR engine allows any attacker to crash a worker process with a single ~130-byte HTTP request. The island URL hash is a non-secret digest computed from public request parameters, so an attacker can forge valid island requests and supply an arbitrarily large integer as a v-for iteration prop - causing the SSR engine to allocate memory proportional to that integer. Reporter-confirmed measurements show count=40000000 or items=4000000 produces an out-of-memory worker crash; no public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the attack is self-evident and trivially reproducible from the advisory description.
Resource exhaustion in boringproxy through 0.10.0 allows any authenticated user to permanently consume server file descriptors, goroutines, and memory by repeatedly requesting the GET /loading endpoint with arbitrary id parameter values. The handler blindly attempts to receive from a nil channel - a Go-language primitive that blocks forever - with no map-lookup validity check, no HTTP server timeouts, no context cancellation, and no runtime reclamation, meaning each malicious request permanently holds one goroutine (~50 kB stack), one file descriptor, and associated heap memory. Once the server's file descriptor limit is exhausted, all listener Accept calls fail and tunnel traffic forwarding halts for every connected user. A public proof-of-concept writeup exists on GitHub; no CISA KEV listing has been identified at time of analysis.
Unauthenticated denial of service in Milvus through 2.6.22 and 3.0.0 allows any remote attacker with network access to port 9091 to immediately terminate core service components - proxy, datanode, or querynode - by issuing a single crafted HTTP GET request. The management server's /management/stop endpoint is not protected by the REST API authentication middleware, making exploitation trivial with a publicly available proof-of-concept. No CISA KEV listing exists at time of analysis, but the combination of zero-prerequisite exploitation, public PoC, and CVSS 4.0 score of 8.7 represents a high real-world availability risk for any Milvus deployment with port 9091 reachable beyond localhost.
Broken access control in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to inject arbitrary graph data into the shared execution cache for flows they do not own, via the deprecated POST /api/v1/build/{flow_id}/vertices endpoint. The endpoint performs no ownership validation, enabling cross-user cache pollution that can corrupt other users' workflow state, trigger unauthorized execution of foreign flows, or produce denial of service across a shared platform instance. No public exploit code exists and CISA KEV does not list this vulnerability; EPSS (0.20%, 10th percentile) and SSVC (exploitation: none, automatable: no) collectively indicate low immediate exploitation risk despite the high CVSS score.
Denial-of-service via malformed XMCP packets forces unexpected reloads of Cisco IOS and IOS XE devices, exploitable by any remote unauthenticated attacker. The CVSS scope change (S:C) reflects that the reload impacts the entire device, not just the XMCP subsystem, bringing down all services simultaneously. No public exploit or CISA KEV listing exists at time of analysis, but the zero-authentication, low-complexity attack vector - combined with Cisco's ubiquitous enterprise footprint - makes this a high-priority patching target for network operations teams.
Denial-of-service in Cisco IOS XE Software's Blocks Extensible Exchange Protocol (BEEP) feature allows an unauthenticated remote attacker to force an unexpected device reload by sending a specially crafted BEEP SOAP request. The CVSS 8.6 score with Changed scope (S:C) reflects that a device reload disrupts all network services downstream of the affected device, amplifying impact beyond the immediate target. No public exploit or CISA KEV listing has been identified at time of analysis, though the low-complexity, no-authentication attack vector makes this a credible automated threat against any internet- or network-exposed IOS XE device running the BEEP feature.
Denial of service in Cisco IOS XE Software's SNMP subsystem allows an authenticated remote attacker to force an affected device to reload by sending a malformed SNMP request, disrupting all traffic transiting the device. The vulnerability spans all three SNMP protocol versions (1, 2c, and 3) and affects an exceptionally broad version range across both the 3.x, 16.x, and 17.x release trains. No public exploit or CISA KEV listing has been identified at time of analysis, but the scope-change rating (S:C) reflects that a device reload cascades into a network outage for all downstream systems dependent on the affected device.
Denial of service in Apache Answer through 2.0.1 allows unauthenticated remote attackers to exhaust CPU resources by sending a specially crafted Accept-Language HTTP header that triggers runaway parsing logic. The root cause is improper handling of a length parameter inconsistency (CWE-400) during header processing, meaning any unauthenticated HTTP request reaching the application can be weaponized for resource exhaustion. No public exploit code or CISA KEV listing has been identified at time of analysis, and the Apache Software Foundation has released a remediated version 2.0.2.
Memory exhaustion denial-of-service in OpenSSL 3.6.0-3.6.3 and 4.0.0-4.0.1 allows a malicious TLS server to leak attacker-tunable amounts of heap memory per handshake in connecting client applications that have explicitly enabled OCSP staple verification. By delivering a syntactically valid BasicOCSPResponse containing an empty SingleResponse sequence - optionally padded with bogus certificates to amplify each allocation - the server causes the internal OCSP_BASICRESP structure to be allocated but never freed, bypassing the cleanup path. No public exploit has been identified at time of analysis and no CISA KEV listing exists; risk is bounded by the non-default OCSP flag requirement.
Out-of-bounds heap/stack write in nanoMODBUS through v1.23.0 lets an unauthenticated network client corrupt memory in the Modbus server via a single crafted Read File Record (FC 0x14) request. The server-side handle_read_file_record() function validates per-request and per-sub-request sizes but never checks the cumulative response size, and a uint8_t accumulator (response_data_size) silently overflows, allowing swap_regs() to write up to ~8490 bytes past the 260-byte receive buffer. There is no public exploit identified at time of analysis, but the flaw yields reliable denial of service and, on embedded/bare-metal targets lacking memory protection, potential remote code execution.
Use-after-free race condition in the Linux kernel's RDMA/rxe (SoftRoCE) subsystem allows a local unprivileged user to trigger a kernel crash or achieve page-level memory corruption. The race occurs between rxe_mmap() - which releases pending_lock while a rxe_mmap_info kref is still live - and a concurrent DESTROY_CQ ioctl that drops the kref to zero, causing vfree() to clear vmalloc PTEs mid-walk in remap_vmalloc_range_partial(). No CISA KEV listing exists and EPSS is 0.16% (5th percentile), reflecting the race's very narrow exploitation window; however, the C:H/I:H/A:H impact and confirmed upstream patch make this a priority update for any environment with RDMA/rxe loaded.
Unbounded memory allocation in Rancher Manager's API audit logging middleware enables unauthenticated remote attackers to crash the Rancher management plane via memory exhaustion. When API audit logging is enabled, the audit copyReqBody middleware - positioned ahead of Rancher's APIBodyLimitingHandler in the handler chain - reads entire HTTP request bodies into memory on public login endpoints with no size cap, bypassing the default 1 MiB limit. An attacker sending a small number of concurrent oversized requests to these endpoints can exhaust server memory and terminate the Rancher Manager process, rendering the Rancher API and UI unavailable and severing management control of all downstream Kubernetes clusters. No public exploit has been identified at time of analysis.
Integer underflow in the raster Rust crate's crop() function enables remote process crash via a single crafted request. When offset_x or offset_y exceeds the source image dimension, the signed subtraction wraps to a large negative i32 in release builds; that value is then cast to usize and passed to Vec::with_capacity(), triggering an unrecoverable capacity-overflow panic that kills the host process. No active exploitation is confirmed (not in CISA KEV) and no public POC is listed, but the AV:N/AC:L/PR:N/UI:N CVSS vector indicates zero-friction denial-of-service for any application that exposes the crop() call to untrusted input.
Process crash in imagecli's seam-carving pipeline allows denial of service via a negative ratio argument to the `carve` operation. The `Carve::apply()` function in `src/image_ops.rs` validates only that `ratio <= 1.0`, omitting a positivity check; a negative input saturates to zero through Rust's defined float-to-uint cast, which is forwarded to `imageproc::seam_carving::shrink_width` - a function that panics on widths below 2, terminating the process. No public exploit code exists and the vulnerability is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) reflects that any application exposing imagecli pipeline construction to untrusted input is exploitable with no authentication or interaction.
Uncontrolled memory allocation in imagecli's `scale` pipeline operation allows remote unauthenticated denial-of-service against any application embedding the library with user-controlled pipeline input. Supplying a large ratio value (e.g., `scale 100000`) causes Scale::apply() in src/image_ops.rs to compute output dimensions that trigger an attempted allocation of hundreds of terabytes, aborting the host process immediately. No active exploitation (CISA KEV) has been identified, but the attack is self-describing from the public GitHub issue and requires no authentication per the CVSS vector (PR:N, AC:L).
Unauthenticated remote denial of service in Apache Qpid Broker-J (all versions through 10.0.1) is achievable by exploiting uncontrolled recursion during type-nesting processing, which exhausts the JVM call stack and triggers a StackOverflowError. The attack requires no credentials and no user interaction against any reachable broker instance. No public exploit identified at time of analysis; EPSS of 0.19% (9th percentile) indicates low real-world exploitation probability. Vendor-released patch: 10.1.0.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows unauthenticated remote attackers to crash the service by sending AMQP messages with deeply nested type structures that exhaust the JVM call stack via a StackOverflowError. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial, unauthenticated network exploitation with no user interaction required, targeting availability exclusively. No active exploitation has been confirmed - this vulnerability is absent from CISA KEV and carries a low EPSS score of 0.21% (11th percentile) - but the zero-prerequisite attack path warrants prompt patching for any internet-facing AMQP deployment.
Unauthenticated denial-of-service in Apache Qpid Broker-J through 10.0.1 allows any network-reachable attacker to crash or hang the broker by sending crafted AMQP protocol messages that exploit improper type size/count validation, triggering unbounded memory allocation. The flaw resides in the pre-authentication protocol parsing path, requiring no credentials, user interaction, or special configuration. No active exploitation is confirmed by CISA KEV, and the EPSS score of 0.19% (9th percentile) indicates minimal observed exploitation activity despite the straightforward attack vector.
Remote unauthenticated denial of service in Apache Qpid Broker-J (all versions through 10.0.1) is achievable by exploiting unbounded symbol value caching in the AMQP message processing layer. A pre-authentication attacker can exhaust broker resources without supplying any credentials, crashing or hanging the service. No active exploitation is confirmed (not in CISA KEV), and EPSS at 0.21% (11th percentile) indicates low exploitation probability at time of analysis, though the network-accessible, zero-complexity attack path keeps it a meaningful patching priority for exposed deployments.
Remote unauthenticated denial of service in OpenStack Swift through 2.38.0 allows any network-reachable attacker to exhaust all proxy worker threads with a trivially crafted HTTP Accept header. The proxy server's Accept header parser employs a qdtext regex pattern susceptible to catastrophic backtracking (CWE-1333), where a payload of just 32 backslash-character pairs stalls a single worker for over 30 seconds. Repeated concurrent requests consume all available proxy workers, causing complete and sustained service unavailability — no authentication, session, or account is required. No public exploit or CISA KEV listing has been identified at time of analysis, though the description itself constitutes a functional attack recipe.
Stack-based buffer overflow in OpenSIPS versions prior to 3.6.6 and 4.0.0-rc1 allows a remote unauthenticated attacker to crash worker processes by exploiting the watcherinfo XML generation path in the presence module. The attacker sends a SIP SUBSCRIBE with a From URI exceeding 200 characters, establishing an oversized watcher entry, then triggers presence.winfo generation to overflow a fixed-size stack buffer in create_winfo_xml() within notify.c. No public exploit has been identified at time of analysis, but the unauthenticated network vector and straightforward two-step attack path make this a credible denial-of-service risk for any SIP infrastructure exposing presence services.
Remote unauthenticated denial of service in Systerel S2OPC Toolkit 1.7.3 is exploitable via the OPC UA AddNodes service, triggering a classic buffer overflow (CWE-120) in address_space_bs.c and sopc_node_mgt_helper_internal.c that crashes the server. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms this is reachable from the network without credentials or user interaction, making it trivially automatable against exposed OPC UA endpoints. No public exploit code or CISA KEV listing has been identified at time of analysis, though the impact is particularly acute in OT/ICS environments where S2OPC is deployed, as availability loss in industrial control infrastructure can translate to physical process disruption.
Stack-based buffer overflow in Systerel S2OPC 1.7.3 enables remote denial of service against OPC UA client applications. A malicious or compromised OPC UA server can send a crafted DeleteMonitoredItemsResponse message that triggers an overflow in LockedStaMac_ProcessMsg_DeleteMonitoredItemsResponse and SOPC_StaMac_NewDeleteMonitoredItems within the client_wrapper state machine, crashing the client process. No public exploit or active exploitation has been identified at time of analysis, though source code references confirm the vulnerable code path exists in the published repository.
Server-side use-after-free in open62541 1.5.5 allows a remote attacker to crash an OPC UA server process, causing denial of service. The flaw arises in the local MonitoredItem subscription path where UA_Subscription_localPublish continues dereferencing a UA_Notification object after a callback has already freed it by calling UA_Server_deleteMonitoredItem on the active item. No public exploit or CISA KEV listing has been identified; impact is limited to availability with no confidentiality or integrity exposure.
Denial-of-service (NULL pointer dereference) in the open62541 OPC UA server v1.5.5 lets remote attackers crash the server by sending an AddReferencesRequest whose target uses an empty targetServerUri combined with a non-zero targetNodeId.serverIndex; the server's AddReferences handler fails to validate this non-local ExpandedNodeId case, leaving the target node pointer NULL while execution continues and dereferences it. Publicly available exploit code exists (SSVC exploitation: poc); it is not listed in CISA KEV and EPSS is low at 0.27% (19th percentile). Note that although the input CVSS is scored 9.8 with full C/I/A impact, the underlying flaw class (CWE-476) is consistent with a crash/DoS rather than confidentiality or code-execution impact.
Uncontrolled resource consumption in open62541 v1.5.5 and earlier allows unauthenticated remote attackers to crash or exhaust resources on OPC UA servers by sending crafted NodeManagement type-instantiation requests. The flaw resides in the server-side node management service logic and is exploitable over the network with no privileges or user interaction under the default access control configuration. No CISA KEV listing exists as of analysis, but the SSVC framework classifies the attack as automatable with a proof-of-concept present; the EPSS score of 0.25% (16th percentile) indicates limited observed exploitation in the wild despite that automation potential.
Out-of-bounds read in S2OPC Toolkit 1.7.3's RepublishResponse message handler enables unauthenticated remote attackers to crash the OPC UA service via a crafted network message, resulting in denial of service. The vulnerable code paths span the subscription publish service layer (msg_subscription_publish_bs.c, msg_subscription_publish_ack_bs.c) and the common encoder module (sopc_encoder.c). No public exploit code or CISA KEV listing exists at time of analysis, but the CVSS:3.1 AV:N/AC:L/PR:N/UI:N vector indicates low-barrier remote exploitation requiring no authentication against reachable OPC UA endpoints.
Denial-of-service via buffer overflow in open62541 v1.5.5 allows a remote, unauthenticated attacker to crash an OPC UA server by sending a crafted Service_Call request with malformed input arguments. The flaw resides in the method-call service handler (ua_services_method.c), where input arguments are validated against runtime-resolved InputArguments metadata without proper bounds enforcement. No active exploitation or CISA KEV listing has been identified at time of analysis, but the network-accessible attack surface and zero-privilege requirement make this a meaningful availability risk for any OPC UA server deployment based on this library version.
Heap-based buffer overflow in Systerel S2OPC Toolkit 1.7.3 enables remote denial of service by sending a crafted OPC UA PublishResponse containing malformed EventNotificationList data to the Alarm/Conditions client wrapper. The affected code paths - libs2opc_client_alarm_conditions.c, state_machine.c, and sopc_event_manager.c - process incoming subscription notification data without adequate bounds checking, allowing a malicious or compromised OPC UA server to crash any connected S2OPC client. No public exploit identified at time of analysis, and no CISA KEV listing; however, the CVSS 7.5/High rating and unauthenticated network vector make this a meaningful risk in OPC UA-enabled industrial environments.
Denial of service in Systerel S2OPC 1.7.3 allows remote unauthenticated attackers to crash or render unavailable an OPC UA server by sending crafted requests that trigger uncontrolled resource consumption in the event monitored-item queue resize handling. Affected source code is confirmed across subscription_core.c and monitored_item_notification_queue_bs.c. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Denial of service in OpenSIPS SIP server versions prior to 3.6.6 allows an unauthenticated remote attacker to crash worker processes by sending a SIP request containing a malformed SDP bandwidth line that omits the required colon delimiter. The crafted payload triggers a null pointer dereference (CWE-476) in the SDP parsing layer; when dialog or QoS modules subsequently clone the corrupted SDP state, the worker process terminates abnormally. No active exploitation is confirmed at time of analysis, though publicly readable patch commits expose the exact byte-level trigger, significantly lowering the barrier to exploit construction.
Buffer overflow in open62541 1.5.5's client-side high-level attribute reading logic crashes OPC UA client processes when handling maliciously crafted server responses, resulting in denial of service. The flaw resides in `src/client/ua_client_highlevel.c` and is reachable whenever a client built on open62541 1.5.5 reads node attributes from an attacker-controlled or compromised OPC UA server. No public exploit code has been identified and EPSS at 0.21% (11th percentile) reflects low current exploitation probability; no CISA KEV listing.
Remote denial-of-service in open62541 v1.5.5 is achievable by exploiting a buffer overflow in the OPC UA Discovery/Local Discovery Server (LDS) handling code. An unauthenticated remote attacker can send a specially crafted OPC UA discovery request to crash the affected server process, resulting in full availability loss. No public exploit code has been confirmed and this vulnerability has not been added to the CISA KEV catalog at the time of analysis.
Denial of service in OpenSIPS versions 3.4.0 through 3.6.5 and 4.0.0-beta allows remote attackers to crash the server with a single crafted SIP PUBLISH request targeting the presence module. The crash stems from a NULL pointer dereference in handle_publish() triggered when enable_sphere_check=1 is configured: get_content_type() is invoked without first calling parse_content_type_hdr(), leaving Content-Type parsing state uninitialized and producing a segmentation fault via either a NULL parsed sub-pointer or a NULL content_type pointer. No public exploit has been identified at time of analysis, but the attack mechanics are fully described in the vendor advisory (GHSA-h3ww-hchh-x2g9), and the fix is available in 3.6.6 and 4.0.0-rc1.
Uncontrolled resource consumption in Apache Qpid ProtonJ2 through version 1.1.0 allows authenticated AMQP clients to cause denial of service by sending deliveries composed of an unbounded number of transfer frames. Because the library imposed no upper limit on how many AMQP transfer frames could constitute a single incoming delivery, a malicious but authenticated client can force unbounded heap accumulation, leading to excessive memory usage and potential JVM failure. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patch version 1.2.0 is available.
Denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a remote unauthenticated attacker to crash the messaging service by sending AMQP messages with maliciously crafted type nesting that triggers an uncontrolled recursive call stack, resulting in a StackOverflowError. The flaw (CWE-674) is exploitable without authentication over the network with low attack complexity, making it trivially reachable against any exposed ProtonJ2 endpoint. No active exploitation has been confirmed (not in CISA KEV) and EPSS sits at 0.21% (11th percentile), suggesting minimal observed exploitation activity at time of analysis despite the ease of triggering the condition.
Remote unauthenticated denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a network attacker to exhaust server memory by sending AMQP messages with maliciously crafted type size or count fields, triggering uncontrolled allocation. The vulnerability (CWE-789) requires no authentication or user interaction and is exploitable directly over the network with low complexity, making it trivially reachable in any exposed deployment. No active exploitation has been confirmed in CISA KEV, and the EPSS score of 0.21% (11th percentile) suggests limited real-world exploitation interest at time of analysis; a vendor-released fix is available in version 1.2.0.
Denial of service in Apache Qpid ProtonJ2 through 1.1.0 allows unauthenticated remote attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values during pre-authentication message processing. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials or user interaction are required, and the attack can be executed at low complexity from any network-accessible position. No public exploit or CISA KEV listing exists at time of analysis, though the trivial exploitation conditions make this a realistic threat against any Qpid ProtonJ2 endpoint exposed to untrusted networks.
Denial of service in Apache Qpid Proton-Dotnet 1.0.0 and earlier allows a pre-authentication remote attacker to crash the AMQP service by submitting messages with deeply nested type structures, triggering a StackOverflowError. The CVSS 7.5 (High) reflects a fully network-exposed, unauthenticated attack path with complete availability impact. No active exploitation has been confirmed (EPSS: 0.19%, 9th percentile; no CISA KEV listing), and the vendor has released a direct fix in version 1.1.0.
Excessive memory allocation in Apache Qpid Proton Dotnet through 1.0.0 enables pre-authentication denial of service via crafted AMQP messages. The .NET AMQP client library fails to properly validate type size or count fields during message parsing, allowing a remote unauthenticated attacker to trigger unbounded memory allocation and exhaust available resources. No public exploit code has been identified at time of analysis, but the pre-authentication vector and network reachability of AMQP services make this a realistic threat to messaging infrastructure.
Pre-authentication denial of service in Apache Qpid Proton-Dotnet through version 1.0.0 allows remote unauthenticated attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values. Because the vulnerability is reachable before any authentication handshake completes, no credentials or prior access are required to trigger resource exhaustion. No public exploit or KEV listing is identified at time of analysis, but the pre-auth nature and low attack complexity make this a meaningful availability risk for any internet- or network-exposed AMQP endpoint using the affected .NET library.
Out-of-bounds read in SSSD's PAM responder allows a local low-privileged attacker to crash the SSSD process and disclose sensitive memory contents by sending a crafted protocol v1 authentication request. Affected systems span all major Red Hat Enterprise Linux releases (6 through 10) and OpenShift Container Platform 4, representing a broad footprint in enterprise Linux environments. No active exploitation is confirmed (not listed in CISA KEV), and the EPSS score of 0.14% at the 3rd percentile reflects a very low observed exploitation probability at time of analysis.
Privilege escalation in the Android kernel VPU (Video Processing Unit) driver stems from a use-after-free in vpu_ioctl.c, allowing an attacker to elevate to kernel-level privileges without any additional execution privileges or user interaction. It affects Google Android devices (per the Pixel security bulletin for 2026-08-01), and Android's advisory states no user interaction is required; SSVC rates the technical impact as total and the flaw as automatable. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the total-impact, no-interaction profile makes it a high-priority patch target.
Excessive heap allocation in Apache Qpid Proton-J's AMQP type parser exposes any network-accessible AMQP endpoint to unauthenticated denial-of-service before an authentication handshake completes. Malformed AMQP frames containing attacker-controlled size or count field values cause the Java library to allocate unbounded memory, leading to JVM heap exhaustion and service crash. No public exploit code has been identified and the vulnerability is not listed in CISA KEV at time of analysis, but the pre-authentication attack vector and zero-privilege requirement make this a high-priority patch target for any internet-exposed Proton-J deployment.
Resource exhaustion leading to denial of service in Apache Qpid Proton-J through 0.34.1 can be triggered by a pre-authentication attacker via unbounded AMQP symbol value caching. Any unauthenticated network peer capable of establishing an AMQP connection can send crafted frames that cause the library to cache symbol values without bound, consuming memory until the hosting process becomes unavailable. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Denial of service in SnailJob 1.7.0 allows authenticated attackers to crash the JVM by exploiting the FuryUtil.deserialize helper's failure to validate the frame_content_size field in Zstandard-compressed frame headers before allocating memory. By storing a base64-encoded crafted payload with an arbitrarily inflated decompressed-size declaration in a retry task argument, an attacker causes an unbounded array allocation attempt when the task traverses the retry-task pipeline, resulting in an unrecoverable java.lang.OutOfMemoryError and full server crash. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog; a vendor patch has been released as vsj2.0.0.
Deserialization of untrusted data in NVIDIA Dynamo for Linux (versions 0 through v1.1.0) exposes unauthenticated remote attackers to denial-of-service conditions and data integrity compromise. The flaw is rooted in CWE-502 - unsafe handling of externally supplied serialized objects - and carries a CVSS 8.2 score driven by a fully unauthenticated, low-complexity network attack vector. No public exploit code and no active exploitation have been identified at time of analysis, but the absence of authentication and configuration prerequisites makes the attack surface broad for any internet-accessible Dynamo deployment.
Remote code execution, data tampering, denial of service, and information disclosure are possible through vulnerabilities in NVIDIA Dynamo for Linux examples and recipes, affecting all versions through v1.1.0. The root cause is CWE-1357 (Relies on Insufficiently Trustworthy Component), meaning the examples or recipes bundle or reference a dependency or component without adequate integrity or trust verification, enabling an attacker to exploit that trust boundary over a network. No public exploit code exists and no active exploitation has been confirmed; EPSS places probability at 0.36% (29th percentile) and SSVC confirms exploitation status as none with a non-automatable attack path, suggesting low near-term weaponization risk despite the high CVSS base score.
Out-of-bounds write in the multimodal serving topology of NVIDIA Dynamo for Linux allows remote unauthenticated attackers to corrupt memory, with a rated 9.8 CVSS potentially enabling remote code execution, privilege escalation, data tampering, information disclosure, and denial of service. NVIDIA (the reporting vendor) rates it critical with a network-reachable, no-privilege, no-interaction vector. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, so the score reflects potential rather than observed impact.
Out-of-bounds write in NVIDIA Dynamo for Linux enables remote unauthenticated attackers to cause denial of service or tamper with data via network-reachable attack surface, scoring CVSS 8.2 High. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no special conditions, and no user interaction are required for exploitation. No public exploit code has been identified and CISA KEV listing is absent at time of analysis, but self-disclosure by NVIDIA and a High CVSS score warrant prompt patching in AI inference infrastructure environments.
Path traversal in NVIDIA Triton Inference Server's MLflow plugin allows a low-privileged local user to read, write, or modify files outside the designated model repository by embedding traversal sequences in a model name parameter. All Linux deployments of Triton Inference Server through version 26.02 are affected. No active exploitation has been confirmed (not listed in CISA KEV), EPSS is 0.16% (6th percentile), and SSVC rates exploitation status as none - indicating this is a real but currently low-observed-risk vulnerability that warrants patching on a standard cadence rather than emergency response.
Memory exhaustion in jackson-core's non-blocking async parser allows remote unauthenticated attackers to exhaust JVM heap by streaming JSON integer digit sequences in small chunks without ever sending a terminator byte. The prior fix for GHSA-72hv-8253-57qq (CVE-2026-18401) failed to insert a `validateIntegerLength()` call on the `NOT_AVAILABLE` return path inside `MINOR_NUMBER_INTEGER_DIGITS`, allowing the internal `TextBuffer` accumulator to grow bounded only by `maxStringLength` (20 MiB default) rather than `maxNumberLength` (1000 chars default) - a ~20,000x amplification yielding approximately 40 MiB of heap pressure per connection due to Java's 2-byte char representation. Reactive frameworks that feed inbound HTTP or gRPC bytes incrementally to the async parser - Spring WebFlux/Reactor, Quarkus, Helidon, and Vert.x - are the primary risk surface; no public exploit identified at time of analysis.
Denial of service in Perspective 5.0.0 allows low-privileged remote attackers to render the server permanently unresponsive by submitting a crafted TableMakeViewReq message containing expression columns with unbounded for or while loop constructs. Because the Tornado IOLoop evaluates the expression once per table row with no iteration cap, deadline enforcement, or cancellation mechanism, a single malicious request stalls the entire event loop and blocks all connected clients. A publicly available proof-of-concept exploit exists, and the vulnerability is part of a batch of five CVEs disclosed against this version.
Unauthenticated remote denial-of-service in Perspective 5.0.0 crashes the server process by exploiting missing field validation in the VirtualServer protocol dispatcher. Attackers send syntactically valid but semantically incomplete protobuf messages - such as ViewToArrowReq without a viewport or MakeTableReq without a data field - triggering Rust unwrap() calls on None values at nine distinct code sites, each causing an immediate SIGABRT process abort. No public exploit is confirmed actively exploited (no CISA KEV listing), but a publicly available proof-of-concept exists via a researcher blog post, and the attack requires no authentication against a network-accessible endpoint.
Use-after-free in the Linux kernel rhashtable walk subsystem allows a local attacker with low privileges to dereference a stale pointer into freed slab memory, enabling kernel memory disclosure, crash, or potential privilege escalation. The defect is in rhashtable_walk_start_check(): when a hash table is freed during resize (iter->walker.tbl == NULL), the restart path clears slot and skip but omits clearing iter->p, leaving a dangling pointer that rhashtable_walk_next() then dereferences. Confirmed callers affected include netlink_diag and TIPC socket diagnostics. No public exploit or CISA KEV listing exists at time of analysis; EPSS is 0.15% (5th percentile), reflecting low current exploitation activity despite real kernel memory-safety impact.
Uncontrolled resource consumption in open62541 v1.5.5 and earlier allows remote unauthenticated attackers to crash OPC UA servers by sending crafted subscription-lifecycle requests. The affected request types - CreateSubscription, CreateMonitoredItems (Sampling mode), Publish, TransferSubscriptions, and DeleteSubscriptions - are core to OPC UA data exchange, meaning the vulnerability sits on a heavily-used protocol surface in industrial and IoT deployments. A POC exists per SSVC classification, the attack is rated automatable, and availability impact is rated High by NVD; however, EPSS stands at only 0.25% (16th percentile), indicating limited observed exploitation interest at this time.
Buffer overflow in open62541 1.5.5's Local Discovery Server (LDS) enables an unauthenticated remote attacker to crash the discovery service by sending a RegisterServer or RegisterServer2 request containing an abnormally large number of unique discoveryUrls, but only when the MDNSD multicast discovery backend is enabled at build time. The impact is a denial of service (A:H) with no confidentiality or integrity exposure. No active exploitation is confirmed (not in CISA KEV) and no public exploit code is identified at time of analysis.
Sandbox escape in Google Chrome's Media component on Windows (versions prior to 151.0.7922.109) lets a remote attacker break out of the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and CVSS 9.6 because a successful escape yields full confidentiality, integrity, and availability impact beyond the sandboxed process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though Chrome UAF media bugs are historically attractive targets.
Sandbox escape in Google Chrome for Android before 151.0.7922.109 stems from a use-after-free in the WebGL graphics component (CWE-416), letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Chromium rates this Critical and CVSS scores it 9.6 with a scope change (S:C), reflecting the cross-boundary sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but Chrome WebGL memory-corruption bugs are historically high-value exploitation targets.
Sandbox escape in Google Chrome's Web Authentication (WebAuthn) component before 151.0.7922.109 lets a remote attacker who lures a victim to a crafted HTML page corrupt memory via a use-after-free and potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 (scope-changed), it affects the vast installed base of desktop Chrome; Google has shipped a fixed Stable-channel build. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Use-after-free in the Chrome Extensions subsystem allows sandboxed arbitrary code execution in Google Chrome prior to 151.0.7922.109, requiring a victim to install a crafted malicious extension. The UAF (CWE-416) memory corruption condition is exploitable remotely but demands high attack complexity and active user interaction, resulting in code execution confined within Chrome's sandbox. No public exploit code or CISA KEV listing has been identified at time of analysis; Google has released a fix in the stable channel update of 01 August 2026.
Use-after-free exploitation in Google Chrome's Media component on Windows enables sandbox escape for attackers who have already compromised the renderer process. Chrome versions prior to 151.0.7922.109 on Windows are affected, with a crafted HTML page serving as the trigger mechanism to corrupt freed memory and break out of the renderer sandbox. SSVC rates current exploitation as none and non-automatable, though the total technical impact class reflects full OS-level compromise if the two-stage attack chain is completed successfully.
Use-after-free in the Views UI rendering component of Google Chrome (all versions prior to 151.0.7922.109) enables a remote attacker to corrupt heap memory via a crafted HTML page, requiring the victim to perform specific UI gestures. The CVSS:3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a fully network-delivered attack with no authentication barrier, though high attack complexity and mandatory user interaction substantially reduce opportunistic exploitation likelihood. No public exploit code or CISA KEV listing has been identified at time of analysis; Google rated this High severity internally and shipped a patch in the stable channel update.
Use-after-free in Google Chrome's Views UI framework on Windows, fixed in version 151.0.7922.109, exposes users to heap corruption with full confidentiality, integrity, and availability impact. Exploitation requires convincing a target to perform specific UI gestures while visiting a crafted HTML page, making this a social-engineering-dependent but high-consequence flaw. No public exploit code or CISA KEV listing has been identified at the time of analysis; however, the severity and platform breadth make patching urgent for Windows enterprise fleets.
Use-after-free in the Payments component of Google Chrome prior to 151.0.7922.109 enables a sandbox escape when an attacker has already compromised the renderer process. Exploitation requires chaining a prior renderer compromise with delivery of a crafted HTML page, placing this firmly in the category of multi-stage browser exploitation. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and SSVC classifies exploitation status as none, though the technical impact is rated total due to the full sandbox escape capability.
Sandbox escape in Google Chrome on Android (prior to 151.0.7922.109) via a use-after-free vulnerability in the Skia graphics library allows a remote attacker who has already compromised the renderer process to break out of Chrome's sandbox through a crafted HTML page. The CVSS vector (S:C, C:H/I:H/A:H) confirms full cross-boundary compromise, elevating an attacker from renderer-level code execution to broader Android OS access. No active exploitation is confirmed at time of analysis (SSVC exploitation: none; not listed in CISA KEV), though Technical Impact is rated total by CISA's SSVC framework.
Remote code execution within the Chrome sandbox is possible in Google Chrome versions prior to 151.0.7922.109 due to a use-after-free vulnerability in the V8 JavaScript engine, triggerable by a remote attacker through a specially crafted HTML page. The attacker achieves arbitrary code execution confined to the Chrome renderer sandbox, requiring no privileges but necessitating user interaction to visit a malicious page. Google has released a fix in version 151.0.7922.109; SSVC assessment confirms no known active exploitation at time of analysis, and no public exploit code has been identified.
Sandbox escape in Google Chrome for Linux (versions before 151.0.7922.109) stems from a use-after-free in the Aura windowing subsystem, letting a remote attacker who lures a victim to a crafted HTML page corrupt memory and potentially break out of the renderer sandbox. Google rated the Chromium severity Critical (CVSS 9.6, scope-changed), but there is no public exploit identified at time of analysis and CISA's SSVC framework records exploitation status as 'none'. Because a full sandbox escape gives attacker code the privileges of the browser process on the host, this is a high-priority patch despite the absence of observed exploitation.
Sandbox escape in Google Chrome's Aura display layer on Linux allows a remote attacker with an already-compromised renderer process to break out of the Chrome sandbox via a crafted HTML page, achieving full system-level code execution. Affected versions are all Chrome builds prior to 151.0.7922.109 on Linux. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS scope-changed rating (S:C) and High across C/I/A reflect the severe post-exploitation impact of a successful sandbox escape in a privileged browser context.
Use-after-free in Google Chrome's Translate component (versions prior to 151.0.7922.109) enables remote attackers to execute arbitrary code within the browser's renderer sandbox by directing a user to a crafted HTML page. The CVSS 8.8 score reflects network-accessible, low-complexity exploitation gated only by a single user interaction - visiting an attacker-controlled page. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE primitive within one of the world's most widely deployed browsers represents a materially significant attack surface.
Use-after-free in Google Chrome's HTML engine (all versions prior to 151.0.7922.109) exposes users to potential heap corruption and code execution when they visit a crafted HTML page. The CVSS 8.8 score reflects unauthenticated, network-reachable exploitation requiring only a single user interaction - consistent with Chromium's own 'High' severity classification. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch (151.0.7922.109) has been released and is the primary mitigation.
Heap corruption via use-after-free in Google Chrome's Views UI framework (prior to 151.0.7922.109) can be triggered by a remote attacker who delivers a crafted HTML page and induces a user to perform specific UI gestures. Successful exploitation may lead to arbitrary code execution or denial of service within the browser process. No public exploit code or CISA KEV listing has been identified at time of analysis, and the CVSS AC:H rating signals non-trivial exploitation conditions that reduce real-world risk compared to the high severity label.
Use-after-free in Chrome's Resources component on Android enables sandbox escape for attackers who have already established a foothold in the renderer process. Affected versions are all Chrome for Android releases prior to 151.0.7922.109. The CVSS scope change (S:C) and High ratings across Confidentiality, Integrity, and Availability confirm that successful exploitation breaks out of the browser sandbox, exposing the underlying Android OS. No public exploit code or CISA KEV listing exists at time of analysis, though the chained exploit capability (renderer-to-sandbox-escape) represents a critical capability for advanced threat actors.
Sandbox escape via GPU use-after-free in Google Chrome prior to 151.0.7922.109 enables a remote attacker who has already compromised the renderer process to break out of the Chromium sandbox by delivering a crafted HTML page. The vulnerability resides in Chrome's GPU component and, if successfully chained after an initial renderer compromise, yields full confidentiality, integrity, and availability impact on the host system. No public exploit code has been identified at the time of analysis, and SSVC classifies exploitation status as none with automatable set to no, indicating no evidence of active or mass exploitation.
Use-after-free in the WebGL subsystem of Google Chrome for Android (prior to 151.0.7922.109) enables sandbox escape for an attacker who has already achieved renderer-process compromise. By directing a victim to a crafted HTML page, an adversary with existing renderer access can exploit freed memory corruption in WebGL to break out of Chrome's sandbox and reach OS-level execution on the Android device. No public exploit code or active exploitation has been identified; SSVC rates exploitation as none and automatable as no, though technical impact is assessed as total given the full scope change.
Heap corruption via mismatched memory management in llama.cpp's LLaMA-Android JNI wrapper affects builds b1886 through b7445, where new_1batch() allocates memory with malloc() but free_1batch() releases it using the C++ delete operator, triggering undefined behavior and heap metadata corruption. This mismatch guarantees denial of service via process crash and, depending on allocator state, may enable arbitrary code execution within the affected Android application process. No public exploit code has been confirmed and the vulnerability is not listed in CISA KEV; a vendor-released patch exists as build b7446.
CPU exhaustion via quadratic regex backtracking in rrrene/html_sanitize_ex, an Elixir HTML sanitization library, allows unauthenticated remote attackers to saturate the BEAM scheduler pool and render applications unresponsive. The CSS scrubber's declaration regex applies an unbounded greedy quantifier on the property-name token; a crafted 80 KB style body containing no valid CSS colon costs approximately 2.4 seconds of scheduler time per request, meaning a handful of concurrent requests fully deny service. Affected versions span 0.3.1 through 1.5.2 inclusive; impact is strictly availability — no confidentiality or integrity loss occurs. No public exploit or CISA KEV listing is identified at time of analysis.
Unauthenticated remote shutdown of OpenChamber 1.11.7 is possible by sending a single POST request to /api/system/shutdown, terminating the server process and instantly denying service to all active AI coding sessions. The flaw stems from the /api/system/shutdown route being registered before the authentication middleware in the Express handler chain within bootstrap-runtime.js, meaning authentication is never evaluated for that endpoint regardless of whether UI_PASSWORD is configured. No public exploit code or CISA KEV listing has been identified at time of analysis, though the attack requires no privileges or user interaction and is trivially reproducible against any network-exposed instance.
Deserialization-before-authentication in aiosend's WebhookHandler exposes all webhook integrations prior to version 3.0.7 to pre-authentication denial-of-service. An unauthenticated remote attacker can submit arbitrarily large or complex JSON payloads to any reachable aiosend webhook endpoint, forcing a full Pydantic model deserialization pass - including retention of attacker-supplied extra fields in memory due to CryptoPayObject's extra='allow' configuration - before the HMAC signature is checked and the request is rejected. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the attack requires no credentials and minimal skill.
Resource exhaustion via crafted DNS packet affects PowerDNS Authoritative Server, Recursor, and dnsdist, allowing remote unauthenticated attackers to degrade or deny DNS service by sending specially crafted DNS packets that trigger abnormal memory and CPU consumption. The vulnerability spans all three major PowerDNS software components, significantly broadening the attack surface for operators running mixed PowerDNS environments. No public exploit identified at time of analysis, and the flaw is not listed in the CISA KEV catalog, but the low exploitation barrier - any network-reachable DNS query - makes patching urgent for internet-facing DNS infrastructure.
Unauthenticated remote denial of service in LightFTP through version 2.4 exploits multiple data race conditions in ftpserv.c via the LIST/ABOR command sequence. The control thread closes shared data_socket and file_fd descriptors while worker threads concurrently reference the same fields in worker_thread_cleanup, enabling the OS to reassign stale descriptors to unrelated resources and producing undefined behavior. A publicly available proof-of-concept exists (GitHub issue #75); exploitation has not been confirmed in the wild (not in CISA KEV), but the unauthenticated attack surface and CVSS 4.0 score of 8.2 elevate urgency for exposed deployments.
Memory exhaustion denial-of-service in Sonic 3 A.I.R.'s UDP networking stack allows unauthenticated remote attackers to crash the multiplayer server process with a single crafted packet. The root cause is in ReceivedPacketCache::enqueuePacket() within the OxygenEngine netcore layer: the mUniquePacketID field is read directly from the UDP wire format without bounds validation, and when set to UINT32_MAX the server attempts to allocate one CacheItem per missing packet ID gap, exhausting host memory until an uncaught std::bad_alloc propagates to std::terminate(). No public exploit code and no CISA KEV listing exist at time of analysis, but the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H, score 8.7) reflects that the attack is trivially automatable from any network-reachable position.
Unsafe deserialization in Apache CXF's JMS transport allows any party able to publish to the service's JMS destination to achieve denial of service or, where a compatible deserialization gadget chain is present on the application classpath, remote code execution within the CXF process. All Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 are affected when the JMS transport is in use. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability class (CWE-502 with unrestricted ObjectInputStream) is well-understood and tooling such as ysoserial makes it routinely exploitable wherever gadget libraries are present.
Denial of service persists in Apache CXF due to an incomplete remediation of CVE-2026-50645, allowing unauthenticated network attackers to exhaust server resources by submitting messages containing an excessive number of MIME attachment headers. All Apache CXF deployments running versions prior to 4.2.3, 4.1.8, or 3.6.12 remain vulnerable despite having applied the prior patch. No public exploit code or active exploitation has been identified at time of analysis, but the bypass-of-fix nature of this vulnerability means any organization that patched CVE-2026-50645 and considered itself remediated must re-patch.
Uncontrolled resource consumption in Apache CXF's JAX-RS form parameter processing enables remote denial-of-service attacks against any exposed endpoint accepting form-encoded requests. The framework provides a 'maxFormParameterCount' configuration knob but sets no default ceiling, meaning unpatched deployments will parse arbitrarily large parameter sets until memory or CPU is exhausted. Fixed versions (4.2.3, 4.1.8, and 3.6.12) enforce a default cap of 500 parameters; no public exploit or CISA KEV listing has been identified at time of analysis.
Unbounded attachment ingestion in Apache CXF enables remote denial-of-service against any endpoint that processes multipart messages. Versions prior to 4.2.3, 4.1.8, and 3.6.12 imposed no default ceiling on the 'attachment-max-size' parameter, allowing attackers to exhaust server memory or processing capacity by submitting arbitrarily large attachments. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the low attack complexity makes this a realistic threat for internet-exposed CXF deployments.
Kernel crash vulnerability in the Linux SMB client subsystem results from a type mismatch in smb2_aead_req_alloc() where an unsigned 32-bit integer is incorrectly passed to ERR_PTR(), generating an invalid error pointer that causes a system panic upon dereference. Systems running the Linux kernel with the SMB client module (cifs) and SMBv2/v3 AEAD encryption enabled are affected across multiple stable branches, with patches available in versions 6.6.145, 6.12.96, 6.18.39, 7.1.4, and 7.2-rc1. No public exploit code exists and no CISA KEV listing applies; EPSS probability is extremely low at 0.16% (5th percentile), indicating this is primarily a kernel reliability fix with negligible active exploitation interest despite the high official CVSS score.
Use-after-free race condition in the Linux kernel brcmfmac Broadcom WiFi driver enables adjacent-network attackers to corrupt kernel memory during concurrent device removal and bus_reset work execution. Affected systems include any Linux host running brcmfmac on PCIe, SDIO, or USB Broadcom chipsets - including Raspberry Pi devices - on kernel versions since 5.2 through pre-7.1.6. No public exploit or CISA KEV listing exists at time of analysis, and EPSS probability is low at 0.14% (4th percentile), though the kernel-level impact class remains high.
Unbounded memory growth in GStreamer's RTP H.264 and H.265 depayloader elements allows a remote unauthenticated attacker to exhaust process memory and terminate any application consuming RTP video streams. The rtph264depay and rtph265depay elements in gst-plugins-good lack an upper bound on their internal reassembly buffer, meaning an attacker who continuously sends fragmented RTP packets while withholding the end-of-fragment marker can grow that buffer without limit. No public exploit has been identified at time of analysis, and CISA KEV listing is absent, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is trivially exploitable against any exposed GStreamer RTP pipeline.
NULL pointer dereference in HDF5's H5Pget_fill_value function (all versions before 2.1.1) enables denial of service by processing a specially crafted HDF5 dataset file. The flaw arises when a fill value message (format version 1 or 2) carries the 'defined' flag alongside a negative size field - a malformed state the library fails to normalize to its internal 'undefined' sentinel - allowing a NULL datatype pointer to reach H5T_path_find and crash the process. No public exploit identified at time of analysis; the CVSS 4.0 score of 8.2 reflects high availability impact, but the local file-parsing vector and user interaction requirement meaningfully constrain real-world exposure.
Unauthenticated remote denial-of-service in Nuxt's island/server-component SSR engine allows any attacker to crash a worker process with a single ~130-byte HTTP request. The island URL hash is a non-secret digest computed from public request parameters, so an attacker can forge valid island requests and supply an arbitrarily large integer as a v-for iteration prop - causing the SSR engine to allocate memory proportional to that integer. Reporter-confirmed measurements show count=40000000 or items=4000000 produces an out-of-memory worker crash; no public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the attack is self-evident and trivially reproducible from the advisory description.
Resource exhaustion in boringproxy through 0.10.0 allows any authenticated user to permanently consume server file descriptors, goroutines, and memory by repeatedly requesting the GET /loading endpoint with arbitrary id parameter values. The handler blindly attempts to receive from a nil channel - a Go-language primitive that blocks forever - with no map-lookup validity check, no HTTP server timeouts, no context cancellation, and no runtime reclamation, meaning each malicious request permanently holds one goroutine (~50 kB stack), one file descriptor, and associated heap memory. Once the server's file descriptor limit is exhausted, all listener Accept calls fail and tunnel traffic forwarding halts for every connected user. A public proof-of-concept writeup exists on GitHub; no CISA KEV listing has been identified at time of analysis.
Unauthenticated denial of service in Milvus through 2.6.22 and 3.0.0 allows any remote attacker with network access to port 9091 to immediately terminate core service components - proxy, datanode, or querynode - by issuing a single crafted HTTP GET request. The management server's /management/stop endpoint is not protected by the REST API authentication middleware, making exploitation trivial with a publicly available proof-of-concept. No CISA KEV listing exists at time of analysis, but the combination of zero-prerequisite exploitation, public PoC, and CVSS 4.0 score of 8.7 represents a high real-world availability risk for any Milvus deployment with port 9091 reachable beyond localhost.
Broken access control in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to inject arbitrary graph data into the shared execution cache for flows they do not own, via the deprecated POST /api/v1/build/{flow_id}/vertices endpoint. The endpoint performs no ownership validation, enabling cross-user cache pollution that can corrupt other users' workflow state, trigger unauthorized execution of foreign flows, or produce denial of service across a shared platform instance. No public exploit code exists and CISA KEV does not list this vulnerability; EPSS (0.20%, 10th percentile) and SSVC (exploitation: none, automatable: no) collectively indicate low immediate exploitation risk despite the high CVSS score.
Denial-of-service via malformed XMCP packets forces unexpected reloads of Cisco IOS and IOS XE devices, exploitable by any remote unauthenticated attacker. The CVSS scope change (S:C) reflects that the reload impacts the entire device, not just the XMCP subsystem, bringing down all services simultaneously. No public exploit or CISA KEV listing exists at time of analysis, but the zero-authentication, low-complexity attack vector - combined with Cisco's ubiquitous enterprise footprint - makes this a high-priority patching target for network operations teams.
Denial-of-service in Cisco IOS XE Software's Blocks Extensible Exchange Protocol (BEEP) feature allows an unauthenticated remote attacker to force an unexpected device reload by sending a specially crafted BEEP SOAP request. The CVSS 8.6 score with Changed scope (S:C) reflects that a device reload disrupts all network services downstream of the affected device, amplifying impact beyond the immediate target. No public exploit or CISA KEV listing has been identified at time of analysis, though the low-complexity, no-authentication attack vector makes this a credible automated threat against any internet- or network-exposed IOS XE device running the BEEP feature.
Denial of service in Cisco IOS XE Software's SNMP subsystem allows an authenticated remote attacker to force an affected device to reload by sending a malformed SNMP request, disrupting all traffic transiting the device. The vulnerability spans all three SNMP protocol versions (1, 2c, and 3) and affects an exceptionally broad version range across both the 3.x, 16.x, and 17.x release trains. No public exploit or CISA KEV listing has been identified at time of analysis, but the scope-change rating (S:C) reflects that a device reload cascades into a network outage for all downstream systems dependent on the affected device.
Denial of service in Apache Answer through 2.0.1 allows unauthenticated remote attackers to exhaust CPU resources by sending a specially crafted Accept-Language HTTP header that triggers runaway parsing logic. The root cause is improper handling of a length parameter inconsistency (CWE-400) during header processing, meaning any unauthenticated HTTP request reaching the application can be weaponized for resource exhaustion. No public exploit code or CISA KEV listing has been identified at time of analysis, and the Apache Software Foundation has released a remediated version 2.0.2.
Memory exhaustion denial-of-service in OpenSSL 3.6.0-3.6.3 and 4.0.0-4.0.1 allows a malicious TLS server to leak attacker-tunable amounts of heap memory per handshake in connecting client applications that have explicitly enabled OCSP staple verification. By delivering a syntactically valid BasicOCSPResponse containing an empty SingleResponse sequence - optionally padded with bogus certificates to amplify each allocation - the server causes the internal OCSP_BASICRESP structure to be allocated but never freed, bypassing the cleanup path. No public exploit has been identified at time of analysis and no CISA KEV listing exists; risk is bounded by the non-default OCSP flag requirement.
Out-of-bounds heap/stack write in nanoMODBUS through v1.23.0 lets an unauthenticated network client corrupt memory in the Modbus server via a single crafted Read File Record (FC 0x14) request. The server-side handle_read_file_record() function validates per-request and per-sub-request sizes but never checks the cumulative response size, and a uint8_t accumulator (response_data_size) silently overflows, allowing swap_regs() to write up to ~8490 bytes past the 260-byte receive buffer. There is no public exploit identified at time of analysis, but the flaw yields reliable denial of service and, on embedded/bare-metal targets lacking memory protection, potential remote code execution.
Use-after-free race condition in the Linux kernel's RDMA/rxe (SoftRoCE) subsystem allows a local unprivileged user to trigger a kernel crash or achieve page-level memory corruption. The race occurs between rxe_mmap() - which releases pending_lock while a rxe_mmap_info kref is still live - and a concurrent DESTROY_CQ ioctl that drops the kref to zero, causing vfree() to clear vmalloc PTEs mid-walk in remap_vmalloc_range_partial(). No CISA KEV listing exists and EPSS is 0.16% (5th percentile), reflecting the race's very narrow exploitation window; however, the C:H/I:H/A:H impact and confirmed upstream patch make this a priority update for any environment with RDMA/rxe loaded.
Unbounded memory allocation in Rancher Manager's API audit logging middleware enables unauthenticated remote attackers to crash the Rancher management plane via memory exhaustion. When API audit logging is enabled, the audit copyReqBody middleware - positioned ahead of Rancher's APIBodyLimitingHandler in the handler chain - reads entire HTTP request bodies into memory on public login endpoints with no size cap, bypassing the default 1 MiB limit. An attacker sending a small number of concurrent oversized requests to these endpoints can exhaust server memory and terminate the Rancher Manager process, rendering the Rancher API and UI unavailable and severing management control of all downstream Kubernetes clusters. No public exploit has been identified at time of analysis.
Integer underflow in the raster Rust crate's crop() function enables remote process crash via a single crafted request. When offset_x or offset_y exceeds the source image dimension, the signed subtraction wraps to a large negative i32 in release builds; that value is then cast to usize and passed to Vec::with_capacity(), triggering an unrecoverable capacity-overflow panic that kills the host process. No active exploitation is confirmed (not in CISA KEV) and no public POC is listed, but the AV:N/AC:L/PR:N/UI:N CVSS vector indicates zero-friction denial-of-service for any application that exposes the crop() call to untrusted input.
Process crash in imagecli's seam-carving pipeline allows denial of service via a negative ratio argument to the `carve` operation. The `Carve::apply()` function in `src/image_ops.rs` validates only that `ratio <= 1.0`, omitting a positivity check; a negative input saturates to zero through Rust's defined float-to-uint cast, which is forwarded to `imageproc::seam_carving::shrink_width` - a function that panics on widths below 2, terminating the process. No public exploit code exists and the vulnerability is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) reflects that any application exposing imagecli pipeline construction to untrusted input is exploitable with no authentication or interaction.
Uncontrolled memory allocation in imagecli's `scale` pipeline operation allows remote unauthenticated denial-of-service against any application embedding the library with user-controlled pipeline input. Supplying a large ratio value (e.g., `scale 100000`) causes Scale::apply() in src/image_ops.rs to compute output dimensions that trigger an attempted allocation of hundreds of terabytes, aborting the host process immediately. No active exploitation (CISA KEV) has been identified, but the attack is self-describing from the public GitHub issue and requires no authentication per the CVSS vector (PR:N, AC:L).
Unauthenticated remote denial of service in Apache Qpid Broker-J (all versions through 10.0.1) is achievable by exploiting uncontrolled recursion during type-nesting processing, which exhausts the JVM call stack and triggers a StackOverflowError. The attack requires no credentials and no user interaction against any reachable broker instance. No public exploit identified at time of analysis; EPSS of 0.19% (9th percentile) indicates low real-world exploitation probability. Vendor-released patch: 10.1.0.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows unauthenticated remote attackers to crash the service by sending AMQP messages with deeply nested type structures that exhaust the JVM call stack via a StackOverflowError. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial, unauthenticated network exploitation with no user interaction required, targeting availability exclusively. No active exploitation has been confirmed - this vulnerability is absent from CISA KEV and carries a low EPSS score of 0.21% (11th percentile) - but the zero-prerequisite attack path warrants prompt patching for any internet-facing AMQP deployment.
Unauthenticated denial-of-service in Apache Qpid Broker-J through 10.0.1 allows any network-reachable attacker to crash or hang the broker by sending crafted AMQP protocol messages that exploit improper type size/count validation, triggering unbounded memory allocation. The flaw resides in the pre-authentication protocol parsing path, requiring no credentials, user interaction, or special configuration. No active exploitation is confirmed by CISA KEV, and the EPSS score of 0.19% (9th percentile) indicates minimal observed exploitation activity despite the straightforward attack vector.
Remote unauthenticated denial of service in Apache Qpid Broker-J (all versions through 10.0.1) is achievable by exploiting unbounded symbol value caching in the AMQP message processing layer. A pre-authentication attacker can exhaust broker resources without supplying any credentials, crashing or hanging the service. No active exploitation is confirmed (not in CISA KEV), and EPSS at 0.21% (11th percentile) indicates low exploitation probability at time of analysis, though the network-accessible, zero-complexity attack path keeps it a meaningful patching priority for exposed deployments.
Remote unauthenticated denial of service in OpenStack Swift through 2.38.0 allows any network-reachable attacker to exhaust all proxy worker threads with a trivially crafted HTTP Accept header. The proxy server's Accept header parser employs a qdtext regex pattern susceptible to catastrophic backtracking (CWE-1333), where a payload of just 32 backslash-character pairs stalls a single worker for over 30 seconds. Repeated concurrent requests consume all available proxy workers, causing complete and sustained service unavailability — no authentication, session, or account is required. No public exploit or CISA KEV listing has been identified at time of analysis, though the description itself constitutes a functional attack recipe.
Stack-based buffer overflow in OpenSIPS versions prior to 3.6.6 and 4.0.0-rc1 allows a remote unauthenticated attacker to crash worker processes by exploiting the watcherinfo XML generation path in the presence module. The attacker sends a SIP SUBSCRIBE with a From URI exceeding 200 characters, establishing an oversized watcher entry, then triggers presence.winfo generation to overflow a fixed-size stack buffer in create_winfo_xml() within notify.c. No public exploit has been identified at time of analysis, but the unauthenticated network vector and straightforward two-step attack path make this a credible denial-of-service risk for any SIP infrastructure exposing presence services.
Remote unauthenticated denial of service in Systerel S2OPC Toolkit 1.7.3 is exploitable via the OPC UA AddNodes service, triggering a classic buffer overflow (CWE-120) in address_space_bs.c and sopc_node_mgt_helper_internal.c that crashes the server. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms this is reachable from the network without credentials or user interaction, making it trivially automatable against exposed OPC UA endpoints. No public exploit code or CISA KEV listing has been identified at time of analysis, though the impact is particularly acute in OT/ICS environments where S2OPC is deployed, as availability loss in industrial control infrastructure can translate to physical process disruption.
Stack-based buffer overflow in Systerel S2OPC 1.7.3 enables remote denial of service against OPC UA client applications. A malicious or compromised OPC UA server can send a crafted DeleteMonitoredItemsResponse message that triggers an overflow in LockedStaMac_ProcessMsg_DeleteMonitoredItemsResponse and SOPC_StaMac_NewDeleteMonitoredItems within the client_wrapper state machine, crashing the client process. No public exploit or active exploitation has been identified at time of analysis, though source code references confirm the vulnerable code path exists in the published repository.
Server-side use-after-free in open62541 1.5.5 allows a remote attacker to crash an OPC UA server process, causing denial of service. The flaw arises in the local MonitoredItem subscription path where UA_Subscription_localPublish continues dereferencing a UA_Notification object after a callback has already freed it by calling UA_Server_deleteMonitoredItem on the active item. No public exploit or CISA KEV listing has been identified; impact is limited to availability with no confidentiality or integrity exposure.
Denial-of-service (NULL pointer dereference) in the open62541 OPC UA server v1.5.5 lets remote attackers crash the server by sending an AddReferencesRequest whose target uses an empty targetServerUri combined with a non-zero targetNodeId.serverIndex; the server's AddReferences handler fails to validate this non-local ExpandedNodeId case, leaving the target node pointer NULL while execution continues and dereferences it. Publicly available exploit code exists (SSVC exploitation: poc); it is not listed in CISA KEV and EPSS is low at 0.27% (19th percentile). Note that although the input CVSS is scored 9.8 with full C/I/A impact, the underlying flaw class (CWE-476) is consistent with a crash/DoS rather than confidentiality or code-execution impact.
Uncontrolled resource consumption in open62541 v1.5.5 and earlier allows unauthenticated remote attackers to crash or exhaust resources on OPC UA servers by sending crafted NodeManagement type-instantiation requests. The flaw resides in the server-side node management service logic and is exploitable over the network with no privileges or user interaction under the default access control configuration. No CISA KEV listing exists as of analysis, but the SSVC framework classifies the attack as automatable with a proof-of-concept present; the EPSS score of 0.25% (16th percentile) indicates limited observed exploitation in the wild despite that automation potential.
Out-of-bounds read in S2OPC Toolkit 1.7.3's RepublishResponse message handler enables unauthenticated remote attackers to crash the OPC UA service via a crafted network message, resulting in denial of service. The vulnerable code paths span the subscription publish service layer (msg_subscription_publish_bs.c, msg_subscription_publish_ack_bs.c) and the common encoder module (sopc_encoder.c). No public exploit code or CISA KEV listing exists at time of analysis, but the CVSS:3.1 AV:N/AC:L/PR:N/UI:N vector indicates low-barrier remote exploitation requiring no authentication against reachable OPC UA endpoints.
Denial-of-service via buffer overflow in open62541 v1.5.5 allows a remote, unauthenticated attacker to crash an OPC UA server by sending a crafted Service_Call request with malformed input arguments. The flaw resides in the method-call service handler (ua_services_method.c), where input arguments are validated against runtime-resolved InputArguments metadata without proper bounds enforcement. No active exploitation or CISA KEV listing has been identified at time of analysis, but the network-accessible attack surface and zero-privilege requirement make this a meaningful availability risk for any OPC UA server deployment based on this library version.
Heap-based buffer overflow in Systerel S2OPC Toolkit 1.7.3 enables remote denial of service by sending a crafted OPC UA PublishResponse containing malformed EventNotificationList data to the Alarm/Conditions client wrapper. The affected code paths - libs2opc_client_alarm_conditions.c, state_machine.c, and sopc_event_manager.c - process incoming subscription notification data without adequate bounds checking, allowing a malicious or compromised OPC UA server to crash any connected S2OPC client. No public exploit identified at time of analysis, and no CISA KEV listing; however, the CVSS 7.5/High rating and unauthenticated network vector make this a meaningful risk in OPC UA-enabled industrial environments.
Denial of service in Systerel S2OPC 1.7.3 allows remote unauthenticated attackers to crash or render unavailable an OPC UA server by sending crafted requests that trigger uncontrolled resource consumption in the event monitored-item queue resize handling. Affected source code is confirmed across subscription_core.c and monitored_item_notification_queue_bs.c. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Denial of service in OpenSIPS SIP server versions prior to 3.6.6 allows an unauthenticated remote attacker to crash worker processes by sending a SIP request containing a malformed SDP bandwidth line that omits the required colon delimiter. The crafted payload triggers a null pointer dereference (CWE-476) in the SDP parsing layer; when dialog or QoS modules subsequently clone the corrupted SDP state, the worker process terminates abnormally. No active exploitation is confirmed at time of analysis, though publicly readable patch commits expose the exact byte-level trigger, significantly lowering the barrier to exploit construction.
Buffer overflow in open62541 1.5.5's client-side high-level attribute reading logic crashes OPC UA client processes when handling maliciously crafted server responses, resulting in denial of service. The flaw resides in `src/client/ua_client_highlevel.c` and is reachable whenever a client built on open62541 1.5.5 reads node attributes from an attacker-controlled or compromised OPC UA server. No public exploit code has been identified and EPSS at 0.21% (11th percentile) reflects low current exploitation probability; no CISA KEV listing.
Remote denial-of-service in open62541 v1.5.5 is achievable by exploiting a buffer overflow in the OPC UA Discovery/Local Discovery Server (LDS) handling code. An unauthenticated remote attacker can send a specially crafted OPC UA discovery request to crash the affected server process, resulting in full availability loss. No public exploit code has been confirmed and this vulnerability has not been added to the CISA KEV catalog at the time of analysis.
Denial of service in OpenSIPS versions 3.4.0 through 3.6.5 and 4.0.0-beta allows remote attackers to crash the server with a single crafted SIP PUBLISH request targeting the presence module. The crash stems from a NULL pointer dereference in handle_publish() triggered when enable_sphere_check=1 is configured: get_content_type() is invoked without first calling parse_content_type_hdr(), leaving Content-Type parsing state uninitialized and producing a segmentation fault via either a NULL parsed sub-pointer or a NULL content_type pointer. No public exploit has been identified at time of analysis, but the attack mechanics are fully described in the vendor advisory (GHSA-h3ww-hchh-x2g9), and the fix is available in 3.6.6 and 4.0.0-rc1.
Uncontrolled resource consumption in Apache Qpid ProtonJ2 through version 1.1.0 allows authenticated AMQP clients to cause denial of service by sending deliveries composed of an unbounded number of transfer frames. Because the library imposed no upper limit on how many AMQP transfer frames could constitute a single incoming delivery, a malicious but authenticated client can force unbounded heap accumulation, leading to excessive memory usage and potential JVM failure. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patch version 1.2.0 is available.
Denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a remote unauthenticated attacker to crash the messaging service by sending AMQP messages with maliciously crafted type nesting that triggers an uncontrolled recursive call stack, resulting in a StackOverflowError. The flaw (CWE-674) is exploitable without authentication over the network with low attack complexity, making it trivially reachable against any exposed ProtonJ2 endpoint. No active exploitation has been confirmed (not in CISA KEV) and EPSS sits at 0.21% (11th percentile), suggesting minimal observed exploitation activity at time of analysis despite the ease of triggering the condition.
Remote unauthenticated denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a network attacker to exhaust server memory by sending AMQP messages with maliciously crafted type size or count fields, triggering uncontrolled allocation. The vulnerability (CWE-789) requires no authentication or user interaction and is exploitable directly over the network with low complexity, making it trivially reachable in any exposed deployment. No active exploitation has been confirmed in CISA KEV, and the EPSS score of 0.21% (11th percentile) suggests limited real-world exploitation interest at time of analysis; a vendor-released fix is available in version 1.2.0.
Denial of service in Apache Qpid ProtonJ2 through 1.1.0 allows unauthenticated remote attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values during pre-authentication message processing. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials or user interaction are required, and the attack can be executed at low complexity from any network-accessible position. No public exploit or CISA KEV listing exists at time of analysis, though the trivial exploitation conditions make this a realistic threat against any Qpid ProtonJ2 endpoint exposed to untrusted networks.
Denial of service in Apache Qpid Proton-Dotnet 1.0.0 and earlier allows a pre-authentication remote attacker to crash the AMQP service by submitting messages with deeply nested type structures, triggering a StackOverflowError. The CVSS 7.5 (High) reflects a fully network-exposed, unauthenticated attack path with complete availability impact. No active exploitation has been confirmed (EPSS: 0.19%, 9th percentile; no CISA KEV listing), and the vendor has released a direct fix in version 1.1.0.
Excessive memory allocation in Apache Qpid Proton Dotnet through 1.0.0 enables pre-authentication denial of service via crafted AMQP messages. The .NET AMQP client library fails to properly validate type size or count fields during message parsing, allowing a remote unauthenticated attacker to trigger unbounded memory allocation and exhaust available resources. No public exploit code has been identified at time of analysis, but the pre-authentication vector and network reachability of AMQP services make this a realistic threat to messaging infrastructure.
Pre-authentication denial of service in Apache Qpid Proton-Dotnet through version 1.0.0 allows remote unauthenticated attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values. Because the vulnerability is reachable before any authentication handshake completes, no credentials or prior access are required to trigger resource exhaustion. No public exploit or KEV listing is identified at time of analysis, but the pre-auth nature and low attack complexity make this a meaningful availability risk for any internet- or network-exposed AMQP endpoint using the affected .NET library.
Out-of-bounds read in SSSD's PAM responder allows a local low-privileged attacker to crash the SSSD process and disclose sensitive memory contents by sending a crafted protocol v1 authentication request. Affected systems span all major Red Hat Enterprise Linux releases (6 through 10) and OpenShift Container Platform 4, representing a broad footprint in enterprise Linux environments. No active exploitation is confirmed (not listed in CISA KEV), and the EPSS score of 0.14% at the 3rd percentile reflects a very low observed exploitation probability at time of analysis.
Privilege escalation in the Android kernel VPU (Video Processing Unit) driver stems from a use-after-free in vpu_ioctl.c, allowing an attacker to elevate to kernel-level privileges without any additional execution privileges or user interaction. It affects Google Android devices (per the Pixel security bulletin for 2026-08-01), and Android's advisory states no user interaction is required; SSVC rates the technical impact as total and the flaw as automatable. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the total-impact, no-interaction profile makes it a high-priority patch target.
Excessive heap allocation in Apache Qpid Proton-J's AMQP type parser exposes any network-accessible AMQP endpoint to unauthenticated denial-of-service before an authentication handshake completes. Malformed AMQP frames containing attacker-controlled size or count field values cause the Java library to allocate unbounded memory, leading to JVM heap exhaustion and service crash. No public exploit code has been identified and the vulnerability is not listed in CISA KEV at time of analysis, but the pre-authentication attack vector and zero-privilege requirement make this a high-priority patch target for any internet-exposed Proton-J deployment.
Resource exhaustion leading to denial of service in Apache Qpid Proton-J through 0.34.1 can be triggered by a pre-authentication attacker via unbounded AMQP symbol value caching. Any unauthenticated network peer capable of establishing an AMQP connection can send crafted frames that cause the library to cache symbol values without bound, consuming memory until the hosting process becomes unavailable. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Denial of service in SnailJob 1.7.0 allows authenticated attackers to crash the JVM by exploiting the FuryUtil.deserialize helper's failure to validate the frame_content_size field in Zstandard-compressed frame headers before allocating memory. By storing a base64-encoded crafted payload with an arbitrarily inflated decompressed-size declaration in a retry task argument, an attacker causes an unbounded array allocation attempt when the task traverses the retry-task pipeline, resulting in an unrecoverable java.lang.OutOfMemoryError and full server crash. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog; a vendor patch has been released as vsj2.0.0.
Deserialization of untrusted data in NVIDIA Dynamo for Linux (versions 0 through v1.1.0) exposes unauthenticated remote attackers to denial-of-service conditions and data integrity compromise. The flaw is rooted in CWE-502 - unsafe handling of externally supplied serialized objects - and carries a CVSS 8.2 score driven by a fully unauthenticated, low-complexity network attack vector. No public exploit code and no active exploitation have been identified at time of analysis, but the absence of authentication and configuration prerequisites makes the attack surface broad for any internet-accessible Dynamo deployment.
Remote code execution, data tampering, denial of service, and information disclosure are possible through vulnerabilities in NVIDIA Dynamo for Linux examples and recipes, affecting all versions through v1.1.0. The root cause is CWE-1357 (Relies on Insufficiently Trustworthy Component), meaning the examples or recipes bundle or reference a dependency or component without adequate integrity or trust verification, enabling an attacker to exploit that trust boundary over a network. No public exploit code exists and no active exploitation has been confirmed; EPSS places probability at 0.36% (29th percentile) and SSVC confirms exploitation status as none with a non-automatable attack path, suggesting low near-term weaponization risk despite the high CVSS base score.
Out-of-bounds write in the multimodal serving topology of NVIDIA Dynamo for Linux allows remote unauthenticated attackers to corrupt memory, with a rated 9.8 CVSS potentially enabling remote code execution, privilege escalation, data tampering, information disclosure, and denial of service. NVIDIA (the reporting vendor) rates it critical with a network-reachable, no-privilege, no-interaction vector. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, so the score reflects potential rather than observed impact.
Out-of-bounds write in NVIDIA Dynamo for Linux enables remote unauthenticated attackers to cause denial of service or tamper with data via network-reachable attack surface, scoring CVSS 8.2 High. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no special conditions, and no user interaction are required for exploitation. No public exploit code has been identified and CISA KEV listing is absent at time of analysis, but self-disclosure by NVIDIA and a High CVSS score warrant prompt patching in AI inference infrastructure environments.
Path traversal in NVIDIA Triton Inference Server's MLflow plugin allows a low-privileged local user to read, write, or modify files outside the designated model repository by embedding traversal sequences in a model name parameter. All Linux deployments of Triton Inference Server through version 26.02 are affected. No active exploitation has been confirmed (not listed in CISA KEV), EPSS is 0.16% (6th percentile), and SSVC rates exploitation status as none - indicating this is a real but currently low-observed-risk vulnerability that warrants patching on a standard cadence rather than emergency response.
Memory exhaustion in jackson-core's non-blocking async parser allows remote unauthenticated attackers to exhaust JVM heap by streaming JSON integer digit sequences in small chunks without ever sending a terminator byte. The prior fix for GHSA-72hv-8253-57qq (CVE-2026-18401) failed to insert a `validateIntegerLength()` call on the `NOT_AVAILABLE` return path inside `MINOR_NUMBER_INTEGER_DIGITS`, allowing the internal `TextBuffer` accumulator to grow bounded only by `maxStringLength` (20 MiB default) rather than `maxNumberLength` (1000 chars default) - a ~20,000x amplification yielding approximately 40 MiB of heap pressure per connection due to Java's 2-byte char representation. Reactive frameworks that feed inbound HTTP or gRPC bytes incrementally to the async parser - Spring WebFlux/Reactor, Quarkus, Helidon, and Vert.x - are the primary risk surface; no public exploit identified at time of analysis.
Denial of service in Perspective 5.0.0 allows low-privileged remote attackers to render the server permanently unresponsive by submitting a crafted TableMakeViewReq message containing expression columns with unbounded for or while loop constructs. Because the Tornado IOLoop evaluates the expression once per table row with no iteration cap, deadline enforcement, or cancellation mechanism, a single malicious request stalls the entire event loop and blocks all connected clients. A publicly available proof-of-concept exploit exists, and the vulnerability is part of a batch of five CVEs disclosed against this version.
Unauthenticated remote denial-of-service in Perspective 5.0.0 crashes the server process by exploiting missing field validation in the VirtualServer protocol dispatcher. Attackers send syntactically valid but semantically incomplete protobuf messages - such as ViewToArrowReq without a viewport or MakeTableReq without a data field - triggering Rust unwrap() calls on None values at nine distinct code sites, each causing an immediate SIGABRT process abort. No public exploit is confirmed actively exploited (no CISA KEV listing), but a publicly available proof-of-concept exists via a researcher blog post, and the attack requires no authentication against a network-accessible endpoint.
Use-after-free in the Linux kernel rhashtable walk subsystem allows a local attacker with low privileges to dereference a stale pointer into freed slab memory, enabling kernel memory disclosure, crash, or potential privilege escalation. The defect is in rhashtable_walk_start_check(): when a hash table is freed during resize (iter->walker.tbl == NULL), the restart path clears slot and skip but omits clearing iter->p, leaving a dangling pointer that rhashtable_walk_next() then dereferences. Confirmed callers affected include netlink_diag and TIPC socket diagnostics. No public exploit or CISA KEV listing exists at time of analysis; EPSS is 0.15% (5th percentile), reflecting low current exploitation activity despite real kernel memory-safety impact.
Uncontrolled resource consumption in open62541 v1.5.5 and earlier allows remote unauthenticated attackers to crash OPC UA servers by sending crafted subscription-lifecycle requests. The affected request types - CreateSubscription, CreateMonitoredItems (Sampling mode), Publish, TransferSubscriptions, and DeleteSubscriptions - are core to OPC UA data exchange, meaning the vulnerability sits on a heavily-used protocol surface in industrial and IoT deployments. A POC exists per SSVC classification, the attack is rated automatable, and availability impact is rated High by NVD; however, EPSS stands at only 0.25% (16th percentile), indicating limited observed exploitation interest at this time.
Buffer overflow in open62541 1.5.5's Local Discovery Server (LDS) enables an unauthenticated remote attacker to crash the discovery service by sending a RegisterServer or RegisterServer2 request containing an abnormally large number of unique discoveryUrls, but only when the MDNSD multicast discovery backend is enabled at build time. The impact is a denial of service (A:H) with no confidentiality or integrity exposure. No active exploitation is confirmed (not in CISA KEV) and no public exploit code is identified at time of analysis.