Use-after-free in the Linux kernel's TIPC (Transparent Inter-Process Communication) subsystem lets a local actor trigger a write to freed slab memory via the accept() error path of tipc_sk_create(). When socket insertion into the per-netns rhashtable fails, sock->sk is left dangling instead of NULLed, so tipc_release() bypasses its own NULL guard and calls lock_sock() on the freed sk. It affects kernels using the AF_TIPC protocol across many stable branches (fixes backported to 5.4.x through 6.18.x and mainline 7.x); there is no public exploit identified at time of analysis and it is not in CISA KEV, with a low EPSS of 0.18%.
Incorrect checksum computation in the Linux kernel's s390 (IBM Z mainframe) architecture code causes csum_partial() to read from memory address zero instead of the intended source buffer on machines lacking the vector (VX) facility. Affects s390 systems running the buggy kernel builds; the practical effect is corrupted checksums and potential leakage of kernel memory contents near address zero into computed checksums. Rated CVSS 9.8 by automated scoring, but this is a local architecture-specific correctness bug with no public exploit identified at time of analysis and a low EPSS (0.18%, 7th percentile).
Use-after-free in the Linux kernel's Phonet PEP (Pipe End Point) receive path lets an attacker trigger memory corruption via crafted Phonet packets. In pep_get_sb(), a call to pskb_may_pull() can reallocate the skb data buffer, but the code keeps dereferencing the now-stale header pointer, producing a slab use-after-free read confirmed under KASAN. The flaw affects kernels from 2.6.28 through the fixed stable releases and is tagged as an information-disclosure issue; no public exploit identified at time of analysis and it is not listed in CISA KEV, with a low EPSS score (0.18%).
Local kernel memory corruption in the Linux net/x25 subsystem allows an attacker to trigger a slab-use-after-free in x25_kill_by_neigh() by racing a neighbour (X.25 link) teardown against a socket close. The function drops x25_list_lock before calling lock_sock() without holding a socket reference, so a concurrent x25_release() can free the struct sock/x25_sock that the teardown path then dereferences, leading to a crash or potential privilege escalation. No public exploit identified at time of analysis; a KASAN reproducer under QEMU confirmed the flaw, and EPSS exploitation probability is very low (0.18%).
Kernel panic (denial of service) in the Linux kernel networking GRO path affects systems that forward or aggregate traffic. skb_gro_receive_list() is missing the NAPI_GRO_CB(skb)->flush validation that skb_gro_receive() already has, so flush-marked, already-aggregated frag_list packets get re-aggregated, corrupting the frag_list chain; a later skb_segment() on the TX path then dereferences a NULL/corrupted pointer and crashes the kernel. No public exploit identified at time of analysis and EPSS is low (0.18%), but a stable patch is available. Despite the NVD CVSS of 9.8, the described impact is availability-only (crash), not code execution.
Slab use-after-free in the Linux kernel's ILA (Identifier Locator Addressing) IPv6 module allows a remote attacker to trigger memory corruption by sending crafted IPv6 packets through a configured ILA csum-adjust-transport route or receive-side mapping. The flaw stems from ila_csum_adjust_transport() and ila_update_ipv6_locator() caching a stale IPv6 header pointer across a pskb_may_pull() call that can reallocate the skb head, leading to reads and a locator write through freed memory. No public exploit is identified at time of analysis, and EPSS exploitation probability is low (0.18%); the issue is patched upstream.
Length-underflow in the Linux kernel's Open vSwitch (openvswitch) datapath lets a truncation delta be reused across GSO segments, so a segment can reach queue_userspace_packet() with a stored cutlen larger than skb->len and pass an underflowed length to skb_zerocopy(). The affected code is the OVS_ACTION_ATTR_TRUNC (packet truncate) path feeding userspace upcalls, and the flaw is tagged Information Disclosure, consistent with an out-of-bounds copy of adjacent kernel memory into the userspace listener (and/or a kernel crash). It is fixed in stable kernels 6.6.148, 6.12.101, 6.18.42 and 7.1.6; there is no public exploit identified at time of analysis and EPSS is low (0.18%).
Client-side data-integrity failure and bounded out-of-bounds read in the Linux kernel SMB/CIFS client (smb3_simple_fallocate_range) allows a malicious or compromised SMB server to cause the client to skip zero-filling holes during fallocate, so a range the client reports as successfully allocated is left as an un-zeroed hole and a later write can fail with ENOSPC; a malformed server-supplied range length can additionally trigger an out-of-bounds read of the zero buffer. Affected systems are Linux hosts that mount SMB3 shares and call fallocate on them; the fix is merged upstream and backported to stable trees. There is no public exploit identified at time of analysis, no CISA KEV listing, and EPSS is 0.17% (6th percentile).
Use-after-free in the Linux kernel's in-kernel SMB server (ksmbd) allows the async oplock/lease break notification worker to operate on a freed ksmbd_conn object when connection teardown races with a pending break notification. Affected kernels span the 6.6.x through 6.18 stable series (fixed in 6.6.148, 6.12.101, 6.14, 6.18.42 and related patch releases); the fix pins a real conn reference for the queued work item. Rated CVSS 9.8 by the automated feed, but this is a timing-dependent race with no public exploit identified at time of analysis and a low EPSS score (0.17%, 6th percentile).
Memory corruption in the Linux kernel's AMT (Automatic Multicast Tunneling) driver stems from multiple receive and transmit paths caching skb-head pointers (ip_hdr, ipv6_hdr, eth_hdr, and AMT message headers) that are then invalidated by pull/reallocation helpers, leaving dangling pointers that are dereferenced as a use-after-free of the freed skb head. Systems acting as AMT gateways or relays that process attacker-supplied tunneled multicast packets are affected across kernels from 5.16 up to the fixed stable releases. There is no public exploit identified at time of analysis and EPSS is low (0.17%, 6th percentile), but the flaw is a network-reachable kernel UAF that could enable denial of service or, potentially, code execution.
Use-after-free in the Linux kernel's IPsec transmit path (xfrm) occurs when validate_xmit_xfrm() processes a GSO segment list and async crypto offload steals the final segment via -EINPROGRESS, leaving the list head's ->prev pointing at a segment now owned (and potentially freed) by the crypto engine. validate_xmit_skb_list() then writes through that stale tail pointer, corrupting freed memory; the practical impact is kernel memory corruption and likely crash on systems using IPsec with asynchronous crypto. No public exploit identified at time of analysis, EPSS is low (0.16%), and it is not listed in CISA KEV, so this is a patch-and-move-on issue rather than an active-exploitation emergency.
OS command injection in Dokploy self-hostable PaaS versions prior to 0.29.13 lets an authenticated user with application create or update permission achieve arbitrary command execution on the build host. The dockerImage field is interpolated unquoted into shell commands in buildRemoteDocker() (packages/server/src/utils/providers/docker.ts) and validated only as an optional string, so shell command substitution such as $(...) or backticks runs on the local build host or a remote SSH build target. The upstream fix and its regression test publicly demonstrate working injection payloads, so publicly available exploit code exists, though there is no public exploit identified as weaponized and no CISA KEV listing; EPSS was not provided.
Cross-tenant authorization bypass in fosrl Pangolin through v1.20.0 lets an authenticated user reuse an access token minted for one resource to authenticate against any other resource in any organization. Because the authWithAccessToken.ts handler validates the token without binding it to the requested resourceId, a token scoped to resource X in organization A is accepted for resource Y in organization B, collapsing multi-tenant isolation. Rated CVSS 9.6 (CWE-639); no public exploit identified at time of analysis, though the vulnerable code path is disclosed in the referenced source file.
OS command injection in Dokploy self-hosted PaaS (versions prior to 0.29.13) lets an authenticated admin/owner execute arbitrary commands on the underlying host, not merely inside a managed container. The backup/restore, destination, volume-backup, certificate, and mount code paths build bash -c/sh -c strings by directly interpolating user-controlled, database-backed fields (S3 credentials, paths, volume names) and run them through child_process.exec(). No public exploit is identified at time of analysis, but the fix in 0.29.13 confirms multiple confirmed injection sinks, and the container-to-host scope escape makes successful exploitation a full host compromise.
Cross-tenant authorization bypass in Dokploy 0.29.8 and earlier lets an authenticated organization member with backup permissions reach another organization's S3 backup destinations by supplying a client-controlled destinationId that is never checked against their active organization. Because the referenced destination's S3 accessKey and secretAccessKey are materialized on the attacker's service host, the attacker can read a victim tenant's backup objects and redirect or poison backups across tenant boundaries. No public exploit identified at time of analysis, but the flaw is trivially reachable and breaks the core multi-tenant isolation of the platform (CVSS 9.6, scope-changed).
Kernel heap out-of-bounds write in the Linux MCTP serial driver (drivers/net/mctp/mctp-serial.c) lets an attacker on the serial/tty channel corrupt memory adjacent to the netdev private area on any host where an mctpserialN interface has been configured. The receive state machine accepts a zero-length frame, sets rxlen=0, and enters STATE_DATA, so the 'rxpos == rxlen' terminator never fires and every subsequent inbound byte becomes a 1-byte attacker-controlled OOB heap write past the fixed 74-byte rxbuf, continuing effectively unbounded until a frame or escape byte resets the parser. No public exploit is identified at time of analysis and EPSS is low (0.19%), but the flaw was reproduced with KASAN/UBSAN and carries high memory-corruption impact.
OS command injection in Dokploy self-hosted PaaS before 0.29.8 allows an authenticated user with project access to run arbitrary commands on the Dokploy host. The getRegistryCommands() function in packages/server/src/utils/cluster/upload.ts builds a `docker login` shell string by interpolating the attacker-controlled registry password and URL without escaping, so malicious credentials are executed when a swarm deployment runs. No public exploit identified at time of analysis, but the root cause and fix are fully disclosed in the vendor advisory (GHSA-prwq-2mcm-mvhr), PR #4579, and the v0.29.8 release.
Malicious code injection into the use-reducer-async GitHub repository (a small React useReducer-with-async-actions helper by dai-shi) turned developer workstations into remote-code-execution targets during npm install. Between 2026-05-18 16:29:52 and 2026-05-19 15:26:07 UTC the default branch carried attacker-planted commits (da72edb through df07d57) that added src/install.js, wired it into the postinstall hook, fetched an attacker-hosted second-stage payload over TLS-verification-disabled HTTPS, and eval'd it with require available. The malicious version was never published to npm and the commits were force-pushed away, but any local clone, fork, or direct-SHA checkout still triggers the payload on install; there is no CISA KEV listing and no public exploit identified at time of analysis for the reconstructable payload itself.
Software supply-chain compromise of react18-use, a small React 19 `use`-hook shim maintained by dai-shi, in which malicious commits pushed to the GitHub default branch between 2026-05-19 01:07:01 and 15:20:43 UTC added a `postinstall` script (`src/install.js`) that runs attacker-controlled remote code on developer machines during `npm install`. The malicious commits were later removed by force-push and the package was never published to npm, but local clones, forks, and direct-SHA URLs still carry them, so any `npm install` against an affected checkout still executes the payload today. There is no public exploit identified at time of analysis and it is not on CISA KEV, but the embedded code itself constitutes working malware (CWE-506); anyone who ran `npm install` on a developer workstation on or after 2026-05-19 01:07:01 should assume full host compromise.
SQL injection in the web server of TBEA TLogger (TBEA Communication Box 3rd Generation), firmware V2.1.0.0B0.0.0.0, lets a remote unauthenticated attacker inject SQL through multiple HTTP endpoints that build SQLite queries from attacker-controlled parameters. Successful exploitation allows reading, altering, or deleting all records in the device's on-board CCU.db database, giving full compromise of the logger's stored data. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS 4.0 base score of 9.3 and the unauthenticated network vector make it a high-priority defect for affected operational-technology deployments.
Malicious code injection in the react-tracked source repository (GitHub dai-shi/react-tracked) allowed attacker-controlled remote code execution on developer machines during dependency installation. Between 2026-05-18 19:26:36 and 2026-05-19 15:22:45 UTC the default branch carried booby-trapped commits (6978272 through 949f1a3) that added a postinstall hook fetching and evaluating a second-stage payload from an attacker HTTPS endpoint. The malicious commits were force-pushed away and the package was never published to npm, so npm registry consumers are unaffected, but anyone who ran `npm install` against a poisoned checkout, fork, or direct-SHA clone still executes the code today. No public exploit identified at time of analysis and the flaw is not on CISA KEV, though the incident is a confirmed real compromise rather than a theoretical bug.
Supply-chain compromise of the use-context-selector React library (npm package dai-shi/use-context-selector) planted attacker-controlled malicious code that runs during `npm install`. Between 2026-05-18 15:57:18 and 2026-05-19 15:24:34 UTC the GitHub default branch carried malicious commits (9d8481a through 6f2dae0) that added `src/install.js`, wired it into the `postinstall` hook, fetched a second-stage JavaScript payload from an attacker HTTPS endpoint with TLS verification disabled, and evaluated it with `require` available - but only on developer workstations (execution was deliberately skipped on CI and cloud/serverless). The commits were force-pushed out and the package was never published to npm, so there is no public exploit or CISA KEV entry, but any local clone, fork, or direct-SHA checkout retaining those commits will still execute the code on `npm install` today.
Root-level device takeover in TBEA TLogger V2.1.0.0B0.0.0.0 (the TBEA Communication Box 3rd Generation) stems from a hard-coded/default root credential exposed over the device's SSH service, letting remote attackers authenticate as root and gain full administrative control. The static root password can be derived from the /etc/shadow hash and, being shared across devices, works fleet-wide once recovered. There is no public exploit identified at time of analysis and no CISA KEV listing, but the flaw was independently reported by ICS researcher CyberDanube and carries a critical CVSS 4.0 base score of 9.3.
Unauthenticated arbitrary file read in NCEAS Metacat (all 1.x and 2.x through 2.19.1) lets a remote attacker retrieve any file readable by the Tomcat process via a path-traversal in the archiveEntryName parameter of the legacy 1.x action=read endpoint. A single unauthenticated GET request can exfiltrate credentials, DataONE client certificates and private keys, and embargoed research data. Publicly available exploit code exists (POC demonstrated and verified); the issue is fixed only in Metacat 3.0.0, and 2.x will not be backported.
Unauthenticated XML External Entity (XXE) injection in TIBCO/Jaspersoft JasperReports Server (9.0.0 before HF-9 and 10.0.0 before HF-10) allows a remote attacker to submit crafted XML that the server's parser resolves, enabling local file disclosure and server-side request forgery against internal systems. The vendor rates it CVSS 4.0 9.3 (Critical) and no authentication is required. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the unauthenticated network vector makes it a high-priority patch.
Unauthenticated SQL injection in ReadyEcommerce before 4.5.2 lets remote attackers inject into the MySQL HAVING clause of the public products listing API, because the rating parameter is concatenated into the query without parameterization in ProductController.php. Any anonymous internet user can perform time-based blind extraction of the entire database - including user records and administrator password hashes - and, because the database connection runs as root, may pivot to file-system access on the DB host. No public exploit identified at time of analysis, but the flaw is trivially reachable (AV:N/AC:L/PR:N) and reported by VulnCheck.
Arbitrary file read and SSRF in Firecrawl before 2.11.32 lets an API caller exfiltrate files from the extraction worker and reach internal/external HTTP endpoints by abusing JSON-schema dereferencing. The extract feature passes user-supplied schemas to the json-schema-ref-parser library with default resolvers, so a $ref placed inside default, const, or enum fields (which AJV does not traverse) is resolved against the local filesystem or network; a deliberately triggered dereference error then leaks the resolved file contents back through the extraction API's persisted error message. No public exploit or CISA KEV listing is identified at time of analysis, but the fix commit ships security regression tests demonstrating the file:// and metadata-endpoint attack paths.
Authentication bypass in the web management server of TBEA TLogger (firmware V2.1.0.0B0.0.0.0), a data-logging communication box used with TBEA power/photovoltaic equipment, lets an unauthenticated remote attacker reach the protected /index.asp endpoint once any legitimate user has previously authenticated to the device. The attacker can then view and alter device configuration and data intended only for authenticated users, and triggering a logout from the bypassed session can crash the web server. Rated CVSS 4.0 9.2 (Critical); no public exploit identified at time of analysis and not listed in CISA KEV.
Arbitrary file deletion in the cube-root/directory-serve Node.js utility (all versions through 1.3.7) lets an unauthenticated remote attacker remove files anywhere on the host by supplying ../ sequences in the file query parameter of the file-remove middleware. Exploitation requires the server to be started with the --delete option, and the CVSS 3.1 score of 9.1 (I:H/A:H) reflects the potential for destruction of configuration, data, or system files. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the flaw is trivially reproducible from the disclosed source path.
Improper authorization in Daptin through v0.12.34 lets unauthenticated remote guests perform full CRUD (read, create, update, delete) on all usergroup records, effectively bypassing access control on the platform's group and permission objects. The flaw arises because permission checks treat a null/zero UserId as a valid ownership match, so a guest whose session UserId is null is granted owner-level rights over ownerless usergroup rows. No public exploit identified at time of analysis, but the CVSS of 9.1 (network, no auth, no interaction) reflects that manipulating usergroups can be leveraged to escalate privileges and corrupt the platform's authorization model.
Out-of-bounds read in the Linux kernel's SMB/CIFS client DFS referral parser (parse_dfs_referrals) affects systems that mount SMB shares using DFS. A malicious or compromised SMB server can return a referral response whose PathConsumed value exceeds the search name length, causing later DFS path parsing to advance past the end of the buffer and leak adjacent kernel memory or crash the client. Tagged as Information Disclosure with a 9.1 CVSS; EPSS is low (0.18%, 7th percentile) and there is no public exploit identified at time of analysis.
Directory-traversal / share escape in the Linux kernel's in-kernel SMB3 server (ksmbd) lets an authenticated SMB client create files, directories, or hardlinks outside the exported share. The SMB2 open lookup is correctly rooted at the share with LOOKUP_BENEATH, but ksmbd_vfs_kern_path_create() built an absolute path via convert_to_unix_name() and resolved it from AT_FDCWD, so a '..' component walked from the real filesystem root and escaped the export. It is exploited through a TOCTOU race and has no public exploit identified at time of analysis; EPSS is low (0.17%, 6th percentile) and it is not in CISA KEV.
Arbitrary file write in OpenCart 4.2.0.0 lets an attacker plant a PHP web shell in the webroot by abusing the extension installer, which extracts uploaded .ocmod.zip archives without validating that extracted paths remain inside the target directory (a classic Zip-Slip / path traversal). Because a web shell grants command execution, this escalates to full remote code execution on the store server. There is no public exploit identified at time of analysis, EPSS is low (0.17%, 6th percentile), and it is not on CISA KEV.
Command injection in Apache Ranger versions 0.6 through 2.8 allows attackers to inject and execute operating-system commands through improperly neutralized special elements (CWE-77), yielding full compromise of the host running the Ranger service. The NVD CVSS vector scores it 9.8 (network, low complexity, no privileges, no user interaction) with high confidentiality, integrity, and availability impact, meaning a successful exploit can read, alter, and destroy data on the affected component. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV; EPSS estimates a 1.01% 30-day exploitation probability (60th percentile).
Arbitrary file read on the Jenkins controller affects Jenkins through LTS 2.555.3, where an authenticated attacker holding Item/Configure permission can exfiltrate any file readable by the Jenkins process user by uploading a crafted tar archive containing a symlink. This is an incomplete-fix bypass of CVE-2026-33001: the prior patch validated where a symlink is placed during extraction but not where it points, so a link staged inside the workspace can still resolve to paths outside it. There is no public exploit identified at time of analysis, and the flaw is not listed in CISA KEV, but it directly exposes secrets/master.key, credentials.xml, and other sensitive configuration.
Remote code execution in Apache Ranger versions up to and including 2.8.0 stems from unsafe script evaluation in the GraalScriptEngineCreator component, letting an attacker inject and execute arbitrary code (CWE-94) on the Ranger host. Because Ranger is the central authorization and data-governance layer for Hadoop-ecosystem services, compromise can undermine access control across an entire big-data platform. There is no public exploit identified at time of analysis, it is not on CISA KEV, and EPSS is modest (0.34%, 26th percentile), but the 9.8 CVSS rating reflects the potential for full host compromise once conditions are met.
SQL injection in Apache Ranger allows remote attackers to inject arbitrary SQL through the application's data-access layer, exposing the backing policy/audit database to full read, modification, and destruction. Because Ranger is the centralized authorization and access-control service for Hadoop and related big-data platforms, compromise here can undermine security policy enforcement across an entire data estate. Rated CVSS 9.8; no public exploit identified at time of analysis, EPSS is low (0.21%, 12th percentile), and the flaw is fixed in version 2.9.0.