2026-09-16
Incorrect node-block validation in the Linux kernel's f2fs filesystem causes f2fs_sanity_check_node_footer() to be invoked with the wrong folio index, so the sanity check re-validates the same nid instead of the node actually being read, allowing a local user who is permitted to mount a crafted or corrupted f2fs volume to bypass the intended footer validation and trigger out-of-range metadata access - most plausibly a kernel crash or denial of service. The affected code path is reachable only when an attacker-influenced f2fs image is mounted (CVSS AV:L, PR:L), and exploitation requires supplying malicious on-disk metadata, which raises real attack complexity. Vendor patches are available in stable releases 6.18.51 and 7.2.5 (plus mainline 7.3-rc1); no public exploit identified at time of analysis, and the CNA's boilerplate 7.8 HIGH score (AV:L/AC:L/PR:L/UI:N/C:H/I:H/A:H) overstates the issue relative to the assessed vector AV:L/AC:H/PR:L/UI:N/C:L/I:L/A:H, whose dominant impact is availability loss.
Out-of-bounds memory access in the Linux kernel's drm/panthor driver for Arm Mali CSF-class GPUs, caused by 32-bit offset arithmetic wrapping before a bounds check in panthor_init_cs_iface() and panthor_init_csg_iface(). A local attacker with low privileges on a system that has CONFIG_DRM_PANTHOR loaded and a Mali CSF GPU present could influence firmware-provided control-interface strides/offsets to escape the mapped region, yielding potential information disclosure and memory corruption (high confidentiality, integrity, and availability impact per the assessed vector). Exploitation requires the ability to supply malicious or compromised firmware content and is rated high complexity in our independent assessment (AV:L/AC:H/PR:L/UI:N); no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation.
A race condition in the Linux kernel's Direct Rendering Manager (DRM) core allows a local low-privileged user to trigger use-after-free-style resource teardown by issuing an ioctl on a partially registered DRM device node. When drm_dev_register() fails after one minor (for example the render minor) has already been registered and opened by userspace, the error path tears down device resources without first setting the unplugged flag, so an in-flight drm_dev_enter() critical section can continue operating on freed state. The vendor rates this CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); our independent assessment keeps the same CIA and local/low-privilege prerequisites but raises attack complexity to High because the attacker must win a narrow window during a probe or hot-plug registration failure that is not normally under their control. No public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV); vendor patches are available across the supported stable branches.
Missing validation of the plane degamma LUT size in the Linux kernel's AMD display driver (amdgpu/DC) lets a local, authenticated user who can submit DRM atomic commits supply a malformed AMD_PLANE_DEGAMMA_LUT blob - for example a single-entry LUT - and drive the kernel into a divide-by-zero in __is_lut_linear() or an out-of-bounds read in __drm_lut_to_dc_gamma(). The practical consequence is a kernel crash or denial of service and, via the out-of-bounds read, potential disclosure of kernel memory contents; there is no evidence of memory corruption leading to code execution, and this is a local-only issue. Reachability is narrow: the vulnerable property is exposed only on kernels built with AMD_PRIVATE_COLOR (not enabled in mainstream distribution kernels) and only on systems with an AMD GPU using the amdgpu/DC display path. No public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor patches are available in the stable trees (6.12.110, 6.18.51, 7.2.5) and in mainline 7.3-rc1.
Memory corruption in the Linux kernel's TTM pool for Intel Xe graphics allows a local attacker with access to the DRM render node to trigger a stale restore state, leading to kernel crashes or potential privilege escalation. The flaw affects Linux 6.15 through the fix in 7.2.5/7.3-rc1 and requires the TTM backup/restore path (memory pressure or suspend/resume) to be exercised; no public exploit code or active exploitation has been identified at time of analysis.
An out-of-bounds array access in the Linux kernel's AMDGPU driver (drm/amdgpu) lets a local user who can submit GPU work trigger a kernel fault when a ring that was never assigned to a compute partition (AMDGPU_XCP_NO_PARTITION, i.e. ~0) is used on the SDMA isolation-enforcement or VM-flush paths. The access is caught by UBSAN and can crash the kernel, giving a denial-of-service condition with only limited memory-disclosure potential; because the trigger requires local access to an affected AMD GPU running with partition isolation active, exploitation is hardware- and configuration-dependent rather than universally reachable. The vendor has released patches (Linux 6.18.51, 7.2.5 and 7.3-rc1), and no public exploit code was identified at time of analysis; the independent assessment scores this locally as CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H, i.e. availability-weighted with low confidentiality impact.
Memory corruption in the Linux kernel's AMD KFD (amdkfd) driver allows a local user with access to the GPU compute interface to corrupt kernel page state when a GPU Shared Virtual Memory (SVM) page migration from device memory to system RAM fails. The error-path cleanup derives the struct page from a DMA/bus address instead of the page's physical address (pfn), so on systems with an enabled IOMMU it releases and unlocks system-RAM pages that the migration never pinned, while the genuinely allocated pages are leaked and their DMA mappings are not torn down correctly. The vendor assigns CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); our independent assessment keeps the same impact but raises attack complexity to AC:H because the faulty cleanup is reachable only after a device-to-system-RAM migration has already failed and requires IOMMU plus an active ROCm/HSA SVM workload. No public exploit identified at time of analysis and it is not confirmed actively exploited (CISA KEV).
Linux kernel AMD KFD (amdkfd) SVM migration code can use an uninitialized return value when migrating a VM range whose CPU side is a hole, causing the driver to tear down all VRAM pages it has just allocated and leaving memory state inconsistent. Affected are Linux kernel builds using the AMD GPU compute path (SVM/HMM migration to VRAM on ROCm/HSA-capable AMD hardware); the flaw affects code reachable from the commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 baseline and is fixed in 6.18.51, 7.2.5 and 7.3-rc1. Triggering requires a local user holding a GPU device handle and hitting a racy, non-default memory-layout condition, and no public exploit code was identified at time of analysis; the vendor's CVSS 3.1 score of 7.8 is assessed as overstated relative to this local, condition-gated error-handling defect.
A use-after-put in the Linux kernel's DRM pagemap device-memory migration code (drm_pagemap_migrate_populate_ram_pfn) lets a local, low-privileged user who can drive the GPU/device-private-memory migration path corrupt kernel memory and potentially escalate privileges. The defect has two parts: higher-order (THP) folio allocations lack __GFP_NOWARN and any order-0 fallback, and the free_pages error path computes folio_order(page_folio(page)) after put_page(page) has already dropped the reference, so corrupting state occurs when that put released the last reference. Exploitation requires the DRM pagemap subsystem (new in Linux 6.18) to be built and actively used on supported hardware, plus attacker-induced memory pressure to force the allocation failure, and the severity is moderated by the AC:H assessment in the authoritative analysis; there is no public exploit code and no confirmed active exploitation (no CISA KEV listing) at time of analysis.
Use-after-free in the Linux kernel's in-tree nouveau DRM driver lets a local user who can access the nouveau device node on a Fermi-generation or newer NVIDIA GPU potentially corrupt memory during channel teardown. The bug is an ordering flaw in nouveau_channel_del(): the channel's fence context is freed by context_del() before the channel-kill event subscription is dropped, so a kill event delivered in that narrow window makes nouveau_channel_killed() call nouveau_fence_context_kill() on an already-freed fence context. No public exploit code has been identified at time of analysis, and although the CNA assigned CVSS 7.8 (AV:L/AC:L/PR:L), our assessment raises attack complexity to High because a kill event must land in a very tight race window - and on current kernels nothing actually kills a channel on this path, making real-world triggerability very low.
Linux kernel builds containing the open-source Nouveau GPU driver (drm/nouveau/uvmm) fail to clear op->reg on two error paths in nouveau_uvmm_bind_job_submit()'s OP_UNMAP_SPARSE arm, so a job that never created a sparse region can drop the region's only reference in nouveau_uvmm_bind_job_cleanup() and free a live object; a second job still owning that region then performs a use-after-free. Exploitation requires local access to the DRM/render device node and the ability to submit VM_BIND jobs (PR:L), plus a trigger of the -ENOENT busy-region check or an -ENOMEM failure from drm_gpuvm_sm_unmap_ops_create(), with the full use-after-free needing a concurrent job holding the same region. No public exploit code or confirmed active exploitation was identified at time of analysis, and systems running the proprietary NVIDIA driver rather than Nouveau are not affected.
A preemption-handling defect in the Linux kernel's BPF stack-collection path (bpf_get_stackid) allows a local attacker who can load and attach a BPF program to race the perf callchain buffer, where the kernel accesses trace entries after get_perf_callchain returns without preemption disabled; the race can corrupt or leak kernel memory, yielding high confidentiality and integrity impact plus availability loss. Affected kernels span roughly 4.6 up to the fixes shipped in 6.18.51, 7.2.5, and 7.3-rc1, with vendor CVSS 3.1 scored 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); our independent assessment keeps the same impact triad but raises the attack complexity from Low to High (AC:H) because success depends on hitting a narrow timing window, and the practical attack surface is further gated by CAP_BPF/CAP_PERFMON or by a system built with unprivileged BPF enabled. There is no evidence of active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, so risk should be treated as a hardening/patch-priority issue rather than an emergency.
Mis-enforced authorization in Arista EOS allows an authenticated gNMI user to read or write management paths that an active gNSI Pathz policy is meant to deny, specifically when a single Pathz policy contains both a group rule and a user rule referencing the same path. Exposure is limited to EOS deployments that combine OpenConfig, a running gNMI server, and gNSI Pathz authorization - a non-default, advanced management-plane configuration - and the attacker must already hold valid gNMI credentials, consistent with the assessed vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N (confidentiality and integrity High, no availability impact). No public exploit code exists and there is no confirmed active exploitation (not in CISA KEV); the supplied CVSS 4.0 score of 7.7 overstates day-to-day risk given the narrow prerequisite stack.
Stored cross-site scripting in Concrete CMS versions below 9.5.4 allows an attacker to persist a JavaScript payload in the user timezone field (uTimezone), which the Dashboard user-management page renders without output encoding so that the script runs inside an administrator's authenticated session - enabling theft of CSRF tokens, creation of rogue administrator accounts, or modification of site settings. Exploitation is conditionally gated rather than a broad drive-by threat: it requires the non-default setting concrete.misc.user_timezones to be enabled, and the unauthenticated write path exists only in 9.5.3 and only when public registration is also enabled, while versions below 9.5.3 permit only an authenticated user to write the field via the account profile editor; an administrator must subsequently view the malicious user record. No public exploit code was identified at time of analysis, and the vendor's CVSS v4.0 score of 7.7 is substantially moderated by these stacked non-default preconditions, which our independent assessment reflects with a higher attack-complexity and user-interaction-dependent CVSS 3.1 vector.
Cross-tenant data disclosure in djust before 1.0.7 allows an authenticated low-privileged user who holds a WebSocket or SSE connection to read every tenant's rows, because the tenant-isolation manager failed open on the live path rather than rejecting the unscoped query. Only applications using the djust.tenants multi-tenancy feature and serving data over WebSocket/SSE mount or event dispatch are affected; pure HTTP requests remained correctly tenant-scoped. There is no public exploit code identified at time of analysis and the issue is not listed in CISA KEV - the vendor's fix is djust 1.0.7, and there is no workaround on the live path short of upgrading.
Out-of-bounds array indexing in the Linux kernel's USB Type-C UCSI DisplayPort alternate-mode driver (drivers/usb/typec/ucsi/displayport.c) can crash the kernel when the UCSI platform firmware returns a GET_CURRENT_CAM response that exceeds UCSI_MAX_ALTMODES without being 0xff. All Linux kernels exposing the ucsi_displayport code path - introduced around 5.2 and present on modern USB-C laptops with DisplayPort alt-mode - are potentially affected; the vector is local (CVSS:3.1/AV:L/AC:L/PR:N/UI:N) and requires either rogue/buggy PPM firmware or a malicious USB-C DisplayPort partner to steer the alternate-mode negotiation, so stock systems with honest firmware are not reachable. Impact is limited to a kernel crash (denial of service); no confidentiality or integrity impact is supported by the assessed vector, and no public exploit code or CISA KEV entry has been identified at time of analysis.
Missing cryptographic signature verification of firmware update packages in FERMAX VEO and VEO-XS Wi-Fi monitors running firmware prior to 01.48.001 allows anyone who controls the delivery of an update to install unauthorized, attacker-supplied firmware on the device. The attacker must be on the adjacent network (typically the same LAN or Wi-Fi segment as the monitor) and positioned to substitute or serve the update package, such as through an on-path man-in-the-middle position or a rogue update server; no authentication or user interaction is required once that delivery-control precondition is met, and the flaw is not exploitable across the open Internet. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); devices already updated to 01.48.001 or later are not affected.
Signature-verification bypass in Kong API Gateway Enterprise lets an unauthenticated remote attacker present a forged JWT that the gateway accepts as valid, defeating token-based authentication for the MCP OAuth2 and DataKit integration code paths. The vulnerable logic fails to confirm that the JWT's declared signing algorithm is compatible with the key type actually used for verification, so an attacker who can reach a protected endpoint that relies on these integrations can slip through as an authenticated principal; the independent assessment scopes the impact to the backend resources the gateway protects (C:H/I:H under a changed-scope CVSS:3.1 vector) rather than to the gateway host itself. Exposure is gated by configuration - gateways that do not enable MCP OAuth2 or DataKit JWT validation are not reachable - and no public exploit code or confirmed active exploitation was identified at time of analysis.
SAML authentication bypass in Kong Enterprise Gateway allows an unauthenticated remote attacker to impersonate arbitrary users, including administrators, by submitting a crafted SAML response containing an unsigned assertion. Exploitation is strictly gated by a non-default configuration: the Kong SAML plugin's validate_assertion_signature option must have been explicitly set to false, since it defaults to true - default deployments are not affected. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; patch status is Vendor-released patch: Kong Gateway 3.15.0.3.
Firmware update downloads on Fermax VEO and VEO-XS Wi-Fi monitors (DUOX Plus range) running firmware prior to 01.48.001 are not validated against a TLS certificate, so an attacker who already holds a man-in-the-middle position on the network segment carrying that traffic can deliver a spoofed update and have the device install it. The practical result is full loss of integrity, confidentiality and availability on the device, since attacker-supplied firmware runs with the monitor's privileges; the assessed severity is 7.7 (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (CISA KEV), and exploitation is conditional: the attacker must be network-adjacent, must catch or induce a firmware update event, and cannot succeed against monitors already updated to 01.48.001 or later. This is a supply-chain/update-integrity weakness rather than a drive-by remote takeover, and no device credentials are required (PR:N).
Command injection in the web management API of Pepperl+Fuchs ICE2/ICE3 IO-Link master devices and Phoenix Contact IOL MA8 enables an authenticated admin-level attacker to execute arbitrary OS commands as root via a crafted PUT request to the /api/iodd/config endpoint. All firmware versions of at least nine Pepperl+Fuchs ICE2/ICE3 hardware variants and the Phoenix Contact IOL MA8 PN DI8 are confirmed affected across three CERT@VDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028). No public exploit code or active exploitation is identified at time of analysis, but full root compromise of an industrial field device represents a significant ICS/OT risk.
Path traversal in the PHP web management interface of Pepperl+Fuchs ICE2/ICE3 series and Phoenix Contact IOL MA8 IO-Link master devices allows unauthenticated remote attackers to read arbitrary files via the /index.php/view_uploaded_iodd_file endpoint. The most critical disclosed impact is exfiltration of the SSH server's private key, which could enable decryption of captured SSH sessions or device impersonation. Three separate CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) indicate the vulnerability affects a shared firmware/software base across multiple vendor OEM implementations. No public exploit or KEV listing identified at time of analysis.
Authenticated low-privilege users of FileRise before version 3.28.0 can obtain unauthorized read and write access at administrator level through the WebDAV interface by supplying valid Basic-Auth credentials alongside an active administrator PHPSESSID cookie, because the WebDAV layer inherits the elevated privileges of the ambient web session rather than authenticating each request independently as RFC 4918 requires. Exploitation is not trivial and depends on a co-occurring privileged session: the attacker must already hold valid low-privilege credentials (PR:L) and obtain the session cookie of a live administrator session, which is the basis for the high attack complexity (AC:H) in the CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N, base 7.6) and the assessed CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N); availability is unaffected. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at the time of analysis, and the vendor has released FileRise 3.28.0, whose changelog describes refined, more consistent WebDAV request handling.
Blind SQL injection in Themeum's WP Mega Menu WordPress plugin (versions through 1.4.2) allows an attacker who already holds a high-privilege, administrator-level account to feed crafted input into a vulnerable plugin parameter that is not neutralized before reaching a SQL query, letting them infer database contents one query at a time. Exploitation is privilege-gated (CVSS PR:H) and the injection is blind, so extraction is slow and no anonymous or low-privileged user can reach it; user interaction is not required (UI:N). The CVE carries a CVSS 3.1 base score of 7.6, but the effective risk is lower than that number implies given the authentication prerequisite, and no public exploit code has been identified at time of analysis.
Unauthenticated attackers can read the complete AI booking conversation transcript of any Bookly customer — including names, email addresses, phone numbers and appointment details — because the plugin's 'conversation_id' parameter is never checked against an owner, and conversation IDs are sequential integers that can simply be incremented. The same endpoint also allows arbitrary messages to be injected into a victim's conversation, which are then replayed to the Cloud AI worker together with the full private history, enabling data poisoning and prompt-injection against the assistant. The flaw affects all versions of the Online Scheduling and Appointment Booking System – Bookly plugin through 28.1; no public exploit code or CISA KEV listing was identified at time of analysis.
Heap buffer overflow in NLnet Labs Unbound 1.26.0 and earlier can be triggered when a resolver processing a large TCP-framed DNS response encounters an RRSet whose owner name reaches the 255-byte maximum, crashing the resolver process and yielding a denial of service (availability-only impact, C:N/I:N/A:H). An attacker must either operate an authoritative name server that the victim resolver queries or hold an on-path position to tamper with an incoming DNS response, and the malicious answer must be delivered over TCP, be large, and carry the maximal-length owner name; crafting and delivering that payload raises practical complexity above the vendor's AC:L rating, which is why our assessment uses AC:H. No public exploit code or confirmed active exploitation has been identified at time of analysis, and because canonicalisation runs before DNSSEC validation, signature validation does not mitigate the issue. NLnet Labs has published an advisory at https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-81634.txt.
Command injection in SSH.NET's ScpClient (Renci.SshNet, all releases prior to 2026.0.0) lets a remote attacker who can influence the remote path supplied by a calling application execute arbitrary commands as the authenticated SSH user on a shell-based server. The default RemotePathTransformation.DoubleQuote cannot safely quote every remote command interpreter, so shell metacharacters that survive the transformation are parsed by the server's shell when the scp command line is assembled. Exploitation is conditional rather than automatic: the target must be a shell-based SSH server and the path must be crafted for that shell's parsing rules, and the assessed vector (AV:N/AC:H/PR:L/UI:N) requires an authenticated SSH session; no public exploit code or active exploitation has been identified at time of analysis, and applications using SftpClient, non-shell-based servers, or fully neutralizing transformations such as ShellQuote against POSIX shells are not affected.
Unauthenticated remote attackers can terminate the Control iD iDSecure service by sending a single HTTP request to the /api/dguardintegration/dguardVersion endpoint, knocking the system offline until the process is restarted. All iDSecure builds prior to 4.8.3.0 are affected; the crash occurs when the DGuard integration login state is unset and an unhandled null-reference exception escapes from a fire-and-forget asynchronous routine. The CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) confirms a pure availability impact with no credentials or user interaction required; no public exploit code and no confirmed in-the-wild exploitation were identified at time of analysis, and the vendor has released a fix.
Unauthenticated repeated calls to the license-restart API in Control iD iDSecure versions prior to 4.8.3.0 allow any network-reachable attacker to hold the service in a continuous restart cycle, rendering the application unavailable. The exposed /api/license/restartService endpoint requires no credentials, no user interaction, and no non-default configuration to reach, and CVSS 3.1 scores the flaw 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with high availability impact while confidentiality and integrity remain unaffected. No public exploit code has been identified at time of analysis, and the issue is not confirmed actively exploited (CISA KEV), though the single-request nature of the technique makes it straightforward to reproduce wherever the management interface is exposed; the practical limiting factor is network reachability of the iDSecure HTTP API.
Unauthenticated remote memory exhaustion in Keycloak's theme localization endpoints allows any network-reachable attacker to crash the server by flooding the keycloak-services component with unique locale tags, each of which is retained indefinitely in an unbounded in-memory cache. The flaw affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7 deployments where those endpoints are exposed to untrusted networks, and requires no credentials or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5, CWE-400). Impact is availability-only with no data disclosure or integrity compromise, and no public exploit code has been identified at time of analysis, nor is there confirmed active exploitation (CISA KEV).
Native memory exhaustion in Keycloak's SAML Redirect Binding allows an unauthenticated remote attacker to degrade or halt the service by repeatedly sending malformed SAML requests that leak zlib-allocated native memory. Red Hat Build of Keycloak, Red Hat Single Sign-On 7, Red Hat Data Grid 8, and the Red Hat JBoss EAP Expansion Pack are all affected because they embed the same SAML handling code. There is no public exploit identified at time of analysis, and the assessed impact is availability-only (CVSS 7.5, C:N/I:N/A:H), consistent with a genuine but bounded denial-of-service condition; vendor errata (RHSA-2026:68276 through RHSA-2026:68280) address the flaw.
Unbounded memory growth in the stateful Streamable HTTP transport of the rmcp Rust SDK (crates/rmcp, all versions prior to 2.0.0) lets remote, unauthenticated attackers permanently leak session state and eventually crash the server. A crafted JSON-RPC POST that is either not an initialization request, or an initialization request whose MCP-Protocol-Version header disagrees with its body, causes StreamableHttpService::handle_post to call LocalSessionManager.create_session before the message is validated; when validation then fails, the handler returns without removing the inserted LocalSessionHandle, so each request leaves a permanent entry in the shared session table. Because exploitation requires sustained repetition to exhaust memory and degrade legitimate clients through lock contention, CISA SSVC rates it PoC-exploitable but not automatable, while publicly available exploit code exists and CVSS 3.1 scores it 7.5 HIGH (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), with availability as the only impacted security property.
Remote, unauthenticated denial of service affects react/http versions 0.6.0 through 1.11.0, where a malformed Transfer-Encoding: chunked body can trap React\Http\Io\ChunkedDecoder in a non-terminating loop; because ReactPHP is single-threaded and event-loop driven, one looping body halts the entire process rather than a single request. The decoder is used for inbound request bodies in React\Http\HttpServer and outbound response bodies in React\Http\Browser, so a malicious client can freeze a server and a malicious or compromised upstream server can freeze a client. No public exploit identified at time of analysis; a vendor-released patch exists in version 1.11.1.
Denial of service in ISC BIND 9 recursive resolvers affects versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and the subscription builds 9.11.3-S1 through 9.18.50-S1 and 9.20.9-S1 through 9.20.27-S1. A validating resolver can be crashed when an authoritative server it queries returns a valid wildcard answer with a signed NSEC3 proof immediately followed by an unsigned NSEC record at the same owner name, causing an unexpected program exit via a reachable assertion (CWE-617). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) rates this 7.5, availability-only, and exploitation requires the attacker to control or be on-path to the authoritative server answering the resolver's query, so an arbitrary external client cannot trigger the crash by sending queries alone; no public exploit code or CISA KEV entry was identified at time of analysis.
Denial of service in ISC BIND 9 allows a remote, unauthenticated attacker to terminate the named daemon by sending a single DNS query of QTYPE TKEY, causing an assertion failure and unexpected process exit, but only on servers loaded with a named.conf file that contains no global 'options' block. Affected builds are 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and 9.20.9-S1 through 9.20.27-S1; the CVSS 3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), reflecting availability-only impact with no confidentiality or integrity loss. The prerequisite configuration (missing global options block) is uncommon in production deployments, which meaningfully limits real-world exposure; no public exploit code and no confirmed active exploitation were identified at the time of analysis, though the trigger is trivial to send for anyone who can reach the resolver or authoritative port.
Denial of service in ISC BIND 9 allows remote, unauthenticated attackers to terminate the named resolver process when it processes a specifically malformed answer that interacts with the DNS64 synthesis feature. Only resolvers explicitly configured with the dns64 option are affected - a non-default, opt-in capability - but for those systems any client of the resolver loses name resolution when named exits. The bug is a use-after-free (CWE-416) reachable from the network with low complexity (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), affecting BIND 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and the corresponding -S1 subscription builds. No public exploit code has been identified at time of analysis and there is no indication of confirmed active exploitation; vendor patches are available as BIND 9.20.29 and 9.21.26.
Resource exhaustion in ISC BIND 9 recursive resolvers allows unauthenticated remote attackers to cause a denial of service by repeatedly triggering a memory leak through crafted SVCB/HTTPS AliasMode records that reference 14 or more ServiceMode records. Affected versions include 9.18.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and corresponding -S1 subscription builds; patched versions are 9.20.29 and 9.21.26. No public exploit code has been identified at time of analysis, but the vulnerability is remotely exploitable without authentication and can gradually exhaust resolver resources, disrupting recursive lookups.
Unauthenticated remote attackers can abort the `named` process in BIND 9 by sending a crafted DNS-over-HTTPS request that carries a cryptographically invalid SIG(0) record and then prematurely closing the transport connection, producing a null pointer dereference (CWE-476) that terminates the server. Affected versions are 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and the 9.20.9-S1 through 9.20.27-S1 subscription branch; the assessed CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5), meaning no authentication or user interaction and availability-only impact. Exploitation requires the targeted named instance to have the DoH transport enabled and to process SIG(0)-signed messages, so server deployments without DoH exposed to the attacker have no reachable attack surface; impact is limited to a process abort with no data disclosure or modification. No public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor patches are available (9.20.29 and 9.21.26).
Remote denial of service in ISC BIND 9 lets an attacker-controlled (or spoofing-capable) authoritative DNS server crash a recursive resolver by returning a negative answer of exactly 65536 bytes, which `named` caches as a zero-length entry and later aborts on when the entry is read. The flaw affects 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and the corresponding -S1 subscription releases, requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), and is present in default configurations, though reachability is limited to resolvers that actually recurse against attacker-influenced or spoofable zones and then read the poisoned cache entry. Vendor patches are available (9.20.29 and 9.21.26); no public exploit identified at time of analysis, and the impact is availability-only with no confidentiality or integrity loss.
CPU-exhaustion denial of service in ISC BIND 9 recursive resolvers (9.18.0-9.18.50, 9.20.0-9.20.27, 9.21.0-9.21.25, plus the 9.18.11-S1-9.18.50-S1 and 9.20.9-S1-9.20.27-S1 preview builds) can be triggered by a single remote, unauthenticated query for the root of an already-cached tree of SVCB/HTTPS AliasMode records. Once such an AliasMode chain is resident in the resolver cache, the triggering query causes the resolver to spend disproportionate CPU time constructing the response, degrading or stalling name resolution for all clients of that resolver; impact is availability-only with no confidentiality or integrity effect. The assessed CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) is well calibrated, but exploitation is conditional on the attacker first causing the SVCB/HTTPS AliasMode tree to be resolved and cached (for example from an attacker-controlled zone) before issuing the trigger query; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
Double free in the Linux kernel's NVMe-over-Fabrics Fibre Channel (nvme-fc) transport lets a privileged local user corrupt kernel memory when an nvme-fc controller creation attempt fails. The bug lives on an error path: nvme_fc_init_ctrl() jumps to out_put_ctrl: when nvme_add_ctrl() fails (reached when dev_set_name() cannot allocate memory), bypassing the pointer clear that nvme_fc_ctrl_free() relies on, so the transport frees the fabrics options and nvmf_create_ctrl() frees them a second time - KASAN reports a slab-use-after-free in nvmf_free_options(). Introduced by commit 1a9e218195a5 and present in kernels from 6.11 through the fixed stable releases, exploitation requires root/CAP_SYS_ADMIN, the non-default nvme-fc transport, and a narrow allocation-failure window (memory pressure or kernel fault injection); no public exploit identified at time of analysis, and the assessment rates availability impact high with confidentiality and integrity impact none.
Linux kernel NVMe zoned-block setup can be forced into an inconsistent state in which a zoned queue is committed with a zero zone size, causing a shift-out-of-bounds (ilog2(0)) and a kernel-side denial of service on the storage I/O path. The flaw affects Linux 6.9 and later kernels with NVMe ZNS support when a zoned namespace's device, firmware, or an attacker-controlled NVMe-oF target answers the Identify Namespace (I/O Command Set specific) or nvme_set_max_append() Identify Controller command with a POSITIVE NVMe status code rather than a negative errno; this requires a host administrator to have attached that device or target, giving an assessed vector of AV:N/AC:H/PR:H/UI:N with high availability impact only. There is no confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis; the issue was discovered by the FuzzNvme fuzzer, and the impact is availability/integrity of the block layer rather than memory corruption or remote code execution.
Remote, unauthenticated denial of service in the Linux kernel's NVMe-over-TCP target (nvmet-tcp) lets a permitted host wedge the target workqueue by racing an unsolicited H2CData PDU ahead of the target's Ready-to-Transfer message. A write command that takes the R2T path is completed twice, causing a response-list entry to point to itself and, depending on CONFIG_DEBUG_LIST, triggering a kernel BUG or an infinite loop/soft-lockup in the nvmet_tcp workqueue. Only hosts configured as NVMe/TCP targets (particularly subsystems using allow_any_host) are affected; no public exploit code has been identified at time of analysis, and the assessed CVSS 3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
A race condition in the Linux kernel's HDMI-CEC subsystem (media: cec) lets a local user who can open a CEC adapter character device (/dev/cecN) and register as an exclusive follower race message delivery against follower mode changes or adapter release, reading the follower pointer without the adapter lock and creating a window that can corrupt kernel state or leak data. The assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H) confirms this is a local, low-privilege issue requiring an actual CEC-capable adapter and precise timing, not the remote/unauthenticated scenario implied by the vendor's AV:A/PR:N score. No public exploit code and no confirmed active exploitation were identified at time of analysis; vendor patches are available across the maintained stable branches.
Kernel crash (NULL pointer dereference) in the Linux kernel's qla2xxx QLogic Fibre Channel HBA driver, in the EDIF (encrypted FC / FC security) RX security-association delete check, allowing a host using that driver and feature to be taken down by a kernel oops in interrupt context. Only systems with a QLogic FC adapter, the qla2xxx driver loaded, and EDIF/FC-SP encryption in use are exposed; the assessed vector is CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (integrity and confidentiality unaffected, availability high), which is considerably narrower than the vendor's published AV:N/AC:L/PR:N rating and reflects that triggering the fault depends on a driver-internal abort/return timing race rather than remotely supplied network input. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); vendor patches are already released for the affected stable branches.
Improper cryptographic signature verification in the VeloCloud Edge (Arista, formerly VMware/Broadcom SD-WAN) software update workflow allows an attacker who can either upload packages to VeloCloud Orchestrator or authenticate directly to an Edge to install unauthorized software on the appliance. Because the update workflow does not constrain which digest algorithm is used to verify artifacts, a bundle signed with an unexpected or weak digest can be accepted as legitimate, resulting in arbitrary code execution with the privileges of the update process on the SD-WAN edge node. No public exploit code and no CISA KEV listing were present in the provided intelligence, although the required access level (CVSS 4.0 PR:H) means the flaw is most dangerous to insiders or anyone who has already compromised an operator account.
OS command injection in Arista VeloCloud Edge management and configuration workflows allows input supplied through those workflows to be interpreted as an operating-system command, resulting in command execution with elevated privileges on the appliance. Exploitation requires a high-privileged management request or the ability to write a configuration value, so this is primarily a privileged-insider, compromised-admin-account, or post-compromise escalation risk rather than an unauthenticated internet-facing flaw. No public exploit code or active exploitation has been identified at time of analysis, and no EPSS score was supplied with the record.
Signature forgery in Sequoia OpenPGP (sequoia-openpgp) stems from incorrect key-flag inference for legacy OpenPGP certificates that lack a key-flags subpacket, letting an unauthenticated remote attacker bypass the back-signature check and bind an arbitrary subkey to their own certificate. This compromises cryptographic integrity for any application that uses the library to verify untrusted certificates, although exploitation requires the victim to process a crafted certificate (UI:R). No public exploit code or CISA KEV entry was identified in the provided data.
Unauthenticated remote attackers can read live Django view and session state and invoke server-side handlers through djust's observability endpoints when a deployment leaves DEBUG enabled and omits the optional localhost-restriction middleware. The exposure requires that specific documented-but-misconfigured combination, which is why the assessed base score of 7.4 carries AC:H despite being network-reachable with PR:N - the endpoints themselves enforced only DEBUG prior to version 1.0.7. No public exploit code has been identified at time of analysis, and the flaw (CWE-306, missing authentication for critical function) is fully neutralized by upgrading to 1.0.7, by setting DEBUG=False, or by installing the localhost-gating middleware.
Stored cross-site scripting in Concrete CMS before 9.5.4 allows an attacker to upload a plain XML document through a publicly reachable Form Block file-upload question; because uploads were validated by extension only and stored as inline-served, same-origin files, the XML can carry an xml-stylesheet processing instruction pointing at an attacker-controlled XSLT stylesheet. When a victim opens the stored file's URL directly in a browser, the stylesheet transforms the document into HTML and runs attacker JavaScript in the Concrete CMS origin - and if that victim is an authenticated administrator, the script acts with the admin session (the reporter demonstrated creating a new user in the Administrators group). Exploitation is conditional rather than opportunistic: the site must expose a file-upload Form Block question and the victim must be lured into opening the hostile file, and no public exploit code was identified at time of analysis; the flaw is fixed in 9.5.4.