Authorization bypass in Zalando Skipper before 0.27.37 lets unauthenticated remote attackers slip an oversized request body past an Open Policy Agent body-inspection policy: when the opaAuthorizeRequestWithBody filter truncates the body at maxBodyBytes, Skipper derives the input.truncated_body signal from Content-Length rather than the bytes actually read, so an HTTP/1.1 chunked or Content-Length-less HTTP/2 request is evaluated by OPA as non-truncated, allowed, and then forwarded in full to the protected upstream (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, CWE-863). Exploitation is gated on a non-default deployment: the filter must be active and the policy must explicitly allow requests when input.truncated_body == false, the pattern recommended as the prior mitigation for CVE-2026-50197, while installations that do not inspect bodies or do not key on truncated_body are unaffected and requests carrying an accurate Content-Length are correctly flagged as truncated and denied. No public exploit identified at time of analysis.
Denial of service in HAPI FHIR core (org.hl7.fhir.core) before 6.9.12: remote attackers who can reach an endpoint that parses Smart Health Card content can submit a JWT whose header declares zip:"DEF" with an empty or truncated raw-DEFLATE payload, driving SHCParser.decodeJWT() into a non-terminating Inflater loop that pins a JVM worker thread indefinitely. The trigger is unauthenticated and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), and because each malformed request consumes a validation worker permanently, concurrent submissions can exhaust the entire worker pool and make legitimate FHIR validation unavailable. No public exploit code has been identified at time of analysis, and the risk is bounded: a deployment that never feeds untrusted Smart Health Card data into SHCParser (directly or through ResourceChecker file-format detection) is not remotely exploitable despite the network attack vector, with impact limited to availability only - no confidentiality or integrity loss.
Unbounded DEFLATE decompression in HAPI FHIR's SHCParser (org.hl7.fhir.core prior to 6.9.12) allows an unauthenticated remote attacker to exhaust heap memory by submitting a small Smart Health Card JWT whose header sets zip:"DEF" and whose compressed payload inflates to an arbitrarily large size, resulting in severe garbage-collection pressure, request failure, process instability, or process termination. The issue is confined to the decompression path in SHCParser.decodeJWT(), SHCParser.inflate() and SHCParser.decompress(), which accumulate all output in a ByteArrayOutputStream before any size check occurs; no public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV), though no EPSS estimate was supplied in the source data. The practical exposure is bounded by reachability: any application, validator service, or API endpoint built on org.hl7.fhir.core that accepts attacker-supplied SHC/JWT content and routes it through SHCParser before 6.9.12 is affected, while deployments that never expose SHC parsing to untrusted callers have effectively no network attack surface.
Unauthenticated DNS UPDATE injection through CoreDNS's encrypted and gRPC listeners lets a remote client smuggle RFC 2136 dynamic-update messages into an upstream nameserver in CoreDNS versions prior to 1.14.7. The DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC code paths unpack queries without applying dns.DefaultMsgAcceptFunc, so they accept an opcode UPDATE that UDP, TCP, and DoT reject; when CoreDNS is running the proxy or forward plugin against an update-capable upstream that trusts CoreDNS's source address and does not require an attacker-unknown end-to-end TSIG, the UPDATE appears to come from CoreDNS itself and can add, replace, or delete records, hijack names, or alter mail routing in the writable zone. Exploitation is unauthenticated with no user interaction and no public exploit identified at time of analysis, but the exposed CVSS 7.5 (AV:N/AC:L) figure overstates practical reach: the assessed vector raises the bar to AC:H and S:C because the attacker must also find an update-capable upstream that trusts CoreDNS without TSIG enforcement, which substantially narrows the real attack surface.
Memory-exhaustion denial of service in CoreDNS prior to 1.14.7 lets a remote unauthenticated attacker terminate the server by sending crafted queries over the DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, or DNS-over-gRPC transports. Those request paths call dns.Msg.Unpack on attacker-controlled DNS section counts before dns.DefaultMsgAcceptFunc validates the fixed header, so name compression and excessive section counts amplify allocation ahead of the plugin chain, meaning plugin-level rate limiting cannot stop concurrent requests from exhausting memory. There is no public exploit identified at time of analysis, but the flaw is rated CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and is only reachable when one of those non-default transports is enabled - deployments using only the ordinary UDP and TCP listeners are not affected.
Denial of service in Square Wire (the gRPC/protobuf runtime for Kotlin, Java, Swift, and Android) affects all releases before 6.4.5 and the 7.0.0 pre-release line before 7.0.0-alpha04, where attacker-supplied protobuf bytes containing an oversized length-delimited field can crash or exhaust memory in the decoder. The flaw is remotely reachable and unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5), with impact limited strictly to availability - the vendor states there is no confidentiality, integrity, or code-execution consequence. Exploitation requires that a target service actually decodes untrusted Wire protobuf messages; no public exploit code was identified at time of analysis and the issue does not appear in CISA KEV, so risk is concentrated in network-facing endpoints that parse arbitrary protobuf payloads.
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).
Sandbox escape in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated Jenkins user who is permitted to define and run sandboxed scripts - including Pipeline jobs - to break out of the Groovy sandbox and execute arbitrary code on the Jenkins controller. The flaw is a protection-mechanism failure (CWE-693): the sandbox's call-site interception does not cover methods that are added dynamically to a class at runtime, so a crafted script can invoke such a method and run code that should have been blocked. Exploitation requires script-authoring privileges (PR:L) and a deliberately crafted script (AC:H) with no user interaction, giving high confidentiality, integrity, and availability impact on the controller; no public exploit code was identified at the time of analysis, and the practical risk is concentrated in multi-tenant Jenkins deployments where lower-trust users are delegated Pipeline authoring.
Arbitrary code execution in the Jenkins Script Security Plugin (versions up to and including 1415.v9a_f9b_3a_c253d) lets an authenticated attacker who holds permission to define classpath entries run attacker-supplied code inside the Jenkins controller JVM. The plugin downloads the URL-specified JAR twice - it verifies approval against the first response but then loads classpath entries from the second - so an attacker who controls the hosting server can present a benign, approvable JAR on request one and a malicious JAR on request two. The assessed CVSS 3.1 vector (7.5, AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects this time-of-check/time-of-use race: the flaw is remotely reachable but requires an authenticated classpath-defining user and a reliably won race; there is no public exploit code and no confirmed active exploitation identified at time of analysis.
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.
Server-Sent Events (SSE) sessions in djust versions before 1.0.7 are keyed solely by a client-chosen session_id with no binding to the authenticated user, so an unauthenticated remote attacker who learns or is leaked a valid victim session_id can connect to the message endpoint and dispatch event handlers that execute with the victim's identity and state, rated 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, CWE-384). The WebSocket transport enforces this principal binding but the control was dropped on the SSE path, and obtaining a valid session_id first is the limiting factor that accounts for the high attack complexity despite the absence of an authentication requirement (PR:N). Vendor-released patch: 1.0.7, which binds each SSE session to its owning principal, rejects cross-principal access, and caps session creation per principal; no public exploit identified at time of analysis, and the overall risk is moderate-to-serious but not an emergency.
Denial of service in Cisco Secure Firewall ASA and FTD Software allows a network-adjacent, unauthenticated attacker to reload the device by flooding crafted EIGRP update messages, triggering a memory leak that accumulates until the appliance restarts. The flaw is only reachable when EIGRP dynamic routing is configured and active on an interface - it is not present in default configurations - and the attacker must sit within the same Layer-2 broadcast domain/EIGRP adjacency, so the attack cannot be launched across the internet. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; the independent assessment rates this a genuine but bounded availability risk (CVSS 7.4, AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H) because sustained, high-rate traffic is required rather than a single packet.
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.
Local privilege escalation in the Dell Update Package (DUP) Framework (versions prior to 26.07.03) allows an attacker who already holds low-privileged access on a host to inject operating system commands that execute in the elevated context of the update framework, resulting in high impact to confidentiality, integrity and availability. Exploitation also requires user interaction - a trusted user or an automated process must actually run a Dell Update Package - as reflected in the assessed CVSS 3.1 vector AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H (7.3 High), which is local-only and carries no network vector. There is no public exploit identified at time of analysis, and Dell has published a fixed release (26.07.03) in advisory DSA-2026-417.
Uninitialized stack memory in the Linux kernel's LoongArch KVM DMSINTC interrupt-injection path can let a local user who is able to create or control a KVM virtual machine - or code running inside a guest - have non-deterministic stack contents consumed while injecting a dynamic message-signaled interrupt. The vendor rates this 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N), while our independent assessment keeps the local, low-privilege, scope-changing profile but lowers the impact components to C:L/I:L/A:L because the leaked data is not reliably attacker-controlled; the affected surface is limited to LoongArch hosts with KVM enabled and DMSINTC in use. Vendor fixes are available as upstream stable commits, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Unauthenticated stored cross-site scripting in the WP-Lister Lite for eBay WordPress plugin affects every release up to and including 3.8.9, allowing an attacker to inject arbitrary JavaScript through the plugin's AJAX cron handler request parameter because input is not sanitized and output is not escaped. The injected payload is persisted and executes in the browser of any user — including administrators — who later views the affected page, enabling session theft, credential harvesting, or full site takeover via an admin session. No public exploit code has been identified and the flaw is not listed in CISA KEV, but the unauthenticated network-reachable attack path makes it a realistic target for automated scanning; an upstream fix was committed in WordPress.org plugin changeset 3638342.
Authenticated users with only read access can delete RBAC relationships in Yeti through 2.11.0, revoking owner grants and locking legitimate owners out of objects. The flaw resides in the DELETE /api/v2/rbac/{id} endpoint, which omits a caller-permission check (CWE-862). No public exploit code or active exploitation has been identified at time of analysis; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H) indicates high integrity and availability impact with no confidentiality loss, consistent with a genuine but bounded risk.
Prototype pollution in Builder.io Gen2 SDKs at versions ≤5.2.11 (React, Vue, Svelte, Solid) and ≤0.25.13 (Qwik, Angular, React Next.js) lets an attacker who can supply a malicious content block - for example an authenticated content editor or author with write access to a Builder.io space - inject binding keys containing __proto__, prototype, or constructor paths that the deep-set helper processes during block rendering without validation. The result is pollution of Object.prototype with high integrity impact (VI:H) and limited confidentiality/availability impact (C:L/A:L): every object created later in the same process inherits the tainted properties, so in multi-tenant or shared SSR/rendering deployments one tenant's crafted content can contaminate other tenants' renders. Exploitation requires a low-privileged position (PR:L, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L), and single-tenant sites that render only trusted first-party content have substantially reduced practical exposure; no public exploit identified at time of analysis and the issue is not listed in CISA KEV, making this a genuine but conditional risk rather than a top-tier emergency.
Cross-site request forgery in Yahoo CMAK (Cluster Manager for Apache Kafka) through 3.0.0.6 allows an attacker to make a logged-in operator's browser silently submit forged POST requests that delete topics or change cluster configuration, riding the operator's existing HTTP Basic credentials or play-basic-authentication cookie. The root cause is a confirmed missing CSRF filter combined with an authentication cookie that has no SameSite protection, so no per-request token stands between the forged request and destructive state-changing endpoints. The attacker needs no account of their own, but exploitation does require a valid authenticated operator session plus user interaction (luring that operator to attacker-controlled content), and no public exploit code has been identified at time of analysis.
Path traversal in the Cisco Identity Services Engine (ISE) REST API allows an attacker with valid administrative credentials to write files to arbitrary filesystem locations and ultimately execute commands as root on the appliance. The flaw stems from insufficient validation of file paths in upload or copy operations (CWE-23), and exploitation requires network reachability to the ISE REST API plus high-privileged credentials (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, score 7.2), so it is gated to authenticated insiders or post-compromise attackers rather than unauthenticated outsiders. No public exploit code or confirmed active exploitation was identified in the provided intelligence at time of analysis.
SQL injection in the Tanium Asset module lets a high-privilege authenticated console user execute arbitrary SQL against the Asset data store, with the potential to read, modify, or destroy data the module manages (CVSS 3.1 base 7.2, AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). The flaw is remotely reachable and requires no user interaction, but it is gated on two conditions: the optional Asset module must be deployed, and the attacker must already hold an elevated Tanium console session - a self-service or low-privilege account is insufficient. Affected builds are Asset before 1.33.326, before 1.36.174, and before 1.39.153; Tanium has released fixed versions and there is currently no public exploit identified at time of analysis, though the EPSS score is minimal and no CISA KEV listing applies.
Authenticated attackers holding a default 'User' role account on Scirius 3.8.0 and earlier can write attacker-controlled JSON files to arbitrary filesystem paths through the PCAP filestore upload endpoint, which derives the destination filename from a user-supplied document _id field. Scored 7.2 both under CVSS 4.0 (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N) and CVSS 3.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H), the flaw delivers high integrity and availability impact with no confidentiality loss, and because files are written with a forced .json extension the damage comes from poisoning JSON configuration data or consuming disk rather than planting executable code; if the Scirius service runs as root, writes can land in privileged locations. Exploitation requires network reachability to the upload endpoint plus a low-privileged authenticated account (no user interaction), and no public exploit code was identified at time of analysis, with no CISA KEV listing and no EPSS signal provided in the available data.
Privilege escalation in Red Hat Build of Keycloak allows an account already holding the realm 'impersonation' role to impersonate a realm administrator and thereby seize full administrative control over that realm, including management of users, clients, and roles. Affected builds are 26.4 before 26.4.16 and 26.6 before 26.6.7. This is an access-gated issue rather than a pre-authentication takeover: the CVSS vector (PR:H) confirms the attacker must be an authenticated, privileged sub-administrator or holder of a compromised delegated-admin credential before exploitation is possible, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Authenticated path traversal in Apache NiFi Registry 0.4.0 through 2.11.0 allows a user who is authorized to both write and delete extension bundles in a bucket to upload a NAR whose manifest carries crafted parent-directory group, artifact, or version coordinates, causing the default file persistence provider to perform file system operations outside the configured persistence directory. Impact is limited to integrity and availability (files created, overwritten, or deleted outside the storage root) rather than confidentiality or remote code execution, and exploitation requires a valid account with write-plus-delete bundle privileges on a deployment using the default file persistence provider. There is no public exploit identified at time of analysis and no CVSS-vector indication of unauthenticated reach; upgrading to Apache NiFi Registry 2.12.0 closes the vector by rejecting parent-directory coordinates and enforcing a normalized strict-child path check.
QDomDocument, Qt's DOM-based XML parser, crashes when processing maliciously crafted XML with extreme element nesting depth, exploiting uncontrolled recursion (CWE-674) to exhaust the call stack and terminate the host application. Any Qt-based application that passes attacker-influenced content to QDomDocument is affected across the Qt version range identified by cpe:2.3:a:qt:qt:*. No public exploit or active exploitation has been identified at time of analysis; the Qt Project has issued a patch via its code review platform.
The @jitsi/electron-sdk package before 10.0.5 bridges the getDesktopSources() API into the meeting page and lets any script running there invoke the jitsi-screen-sharing-get-sources IPC route to pull desktop thumbnails of every screen and window, without a getDisplayMedia() picker being open and without any OS-level screen-recording permission prompt or user consent. The flaw (CWE-862, missing authorization) affects the Jitsi Meet Electron desktop client and any application embedding the SDK, and it is reachable unauthenticated from inside a meeting by a malicious participant or injected script. The vendor fix is a merged upstream PR (PR #516) shipping in 10.0.5; no public exploit code or CISA KEV listing was identified at time of analysis.
Improper validation of parameters in GitLab CE/EE's Terraform state upload functionality allows an authenticated user holding project-level permissions to read restricted file contents on the server or cause denial of service. Affected releases are all versions from 18.2.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2, with fixes published in the 19.3.2 patch release. Public exploit details exist via a HackerOne report, but the CVSS base score is only 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N); there is no CISA KEV listing and no EPSS data was provided.
Premature expiry of multicast forwarding state in Arista EOS can be triggered by a specially crafted packet sent by an unauthenticated attacker who is positioned on the same Layer 2 or otherwise adjacent network segment, causing temporary loss of multicast traffic on the affected interfaces. This is an availability-only denial of service (CVSS 4.0 reports VA:H with VC:N/VI:N; the CVSS 3.1 assessment is AV:A/AC:L/PR:N/UI:N with impact limited to A:H), so the 'Information Disclosure' tag attached to the record does not reflect the actual impact. Exploitation additionally requires that multicast forwarding (PIM/IGMP) is actively configured on the targeted interface - a default, non-multicast deployment is not exposed - and the disruption is transient, since traffic resumes once forwarding state is rebuilt. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Out-of-bounds reads in the Linux kernel's ksmbd in-kernel SMB3 server can leak kernel memory or crash the system when a local low-privileged attacker can influence the netlink IPC share-configuration response produced by the userspace ksmbd.mountd daemon. The flaw lies in unvalidated variable-length share-config fields - an over-long veto list and a path length that fails to account for the separator byte - and affects kernel series where the fix boundaries listed by EUVD are 5.16, 6.2, 6.7, and 6.9, plus the 7.2.6/7.3-rc2 lines. It is not confirmed actively exploited, no public exploit code has been identified at time of analysis, and EPSS is low at 0.19% (9th percentile); a vendor patch is available. Impact is bounded by the fact that ksmbd is non-default on most distributions (which ship userspace Samba) and the vector is local (AV:L) with low privileges (PR:L) and no user interaction.
Cross-site request forgery in AVideo (WWBN/AVideo) through 29.0 lets an attacker who lures an authenticated, upload-capable user to a crafted page fire cross-origin requests at objects/videoAddNew.json.php and silently rewrite video records. The endpoint disables AVideo's automatic CSRF guard and same-domain check whenever 'user' and 'pass' parameters merely appear in $_REQUEST, and because User::loginFromRequestIfNotLogged() returns early for an existing session, those attacker-supplied credentials are never validated and are simply discarded. A successful attack can transfer video ownership via setUsers_id and alter deletion of user-group access restrictions, can_download, can_share, only_for_paid, video_password, rating, status, creation date, and view count; when the victim has administrator or Permissions::canAdminVideos() rights, any video on the site can be modified, including stripping group restrictions from private content. No public exploit code was identified at time of analysis, no vendor-released patch was available as of the advisory, and the attacker requires no authentication of their own (CVSS PR:N), though the victim must be a logged-in user with upload rights who is induced to visit the attacker's page (UI:P).
Any attacker within Bluetooth Low Energy range can connect to a TCH QRing model R20_B006 smart ring running firmware RT09R20_1.00.00_250318 without pairing, authentication, or user approval, because the device exposes the Nordic UART Service with no client authentication or command authorization. From roughly 10 meters of a worn, powered ring, the attacker bypasses the official companion app and its cloud authentication to read battery status, activate live heart-rate monitoring, and pull stored historical heart-rate and blood-oxygen records. The impact is confidentiality-only (adjacent-vector, unauthenticated per PR:N) with no described ability to modify device state or cause denial of service; no public exploit identified at time of analysis and no vendor-released patch identified.