Out-of-bounds write in Chrome's V8 JavaScript engine allows remote attackers to execute arbitrary code within the renderer sandbox by directing a user to a crafted HTML page. All Google Chrome versions prior to 153.0.8010.36 are affected across desktop platforms. Impact is bounded by Chrome's renderer sandbox - an attacker achieves control over the renderer process and can access browser-stored data such as session cookies and saved credentials, but reaching the host OS would require a separately chained sandbox escape exploit. No public exploit identified at time of analysis.
Remote code execution in FireBox - WooCommerce Popup Builder (all versions ≤ 3.1.10) allows authenticated Author-level attackers to execute arbitrary PHP on the server by injecting unsanitized PHP expressions into campaign condition rules via the `firebox_meta` REST endpoint. The plugin's `Executer::allowedToRun()` blacklist (Executer.php L231) uses a trivially bypassable regex that permits WordPress core functions such as `wp_insert_user`, `update_option`, and `file_put_contents`, which the `value` function in the PHP Conditions class then evaluates directly. Critically, sites migrated from any version prior to 3.1.10 are automatically subjected to `Migrator::preserveCampaignRoleAccess()`, which grants Author-role users `edit_fireboxes` and `publish_fireboxes` capabilities, making exploitation reachable from any registered Author account with no further privilege requirements. No public exploit code or CISA KEV listing has been confirmed at time of analysis.
Unauthenticated LAN access to the ESPHome Device Builder dashboard on Home Assistant add-on deployments allows any device on the local network to gain host-equivalent control with no credentials. The ingress site, which deliberately skips authentication because the HA supervisor is supposed to authenticate upstream, was bound to 0.0.0.0 instead of loopback and the supervisor gateway. Because the add-on uses host networking for mDNS, this exposed the no-auth site on the host's LAN interface, directly bypassing the supervisor's authentication layer. An attacker with LAN access can run arbitrary Python via external_components at compile time, execute arbitrary shell through compile/validation subprocesses, and read or write arbitrary files in the config and data directories. No public exploit has been identified at time of analysis.
Unauthenticated remote task execution in @yeger/turbo-graph ≤ 2.8.8 allows any adjacent-network attacker to invoke arbitrary Turborepo tasks with the victim developer's OS-level privileges. Two independent implementation flaws combine: the embedded Next.js server omits the hostname argument to Node.js `.listen()`, causing the process to bind on all interfaces (`0.0.0.0`/`::`), while the `/api/run` HTTP endpoint reads task names from an attacker-controlled query string and passes them directly to `spawn()` with no authentication, CSRF protection, or allowlist check. No public exploit database entry or CISA KEV listing was identified, but a fully functional PoC with containerized end-to-end reproduction is included in the GitHub Security Advisory GHSA-2r5q-h53f-9rp3, significantly lowering the bar to exploitation.
Local file inclusion in MaxSite CMS through 109.6 allows unauthenticated remote attackers to execute privileged PHP handler files by supplying base64-encoded path traversal sequences to the ajax and require-maxsite dispatcher endpoints. The encoding technique bypasses the dispatchers' path validation logic, enabling attackers to reach admin-gated handler actions entirely without credentials. A public proof-of-concept exploit was published on 2026-09-08; the vulnerability spans essentially the entire version history of the product (0.78 through 109.6), and no patched release has been confirmed at time of analysis.
Unauthenticated remote denial-of-service in PocketMine-MP before 5.41.1 allows any actor who can reach the server's Minecraft Bedrock port to crash the process with a single crafted LoginPacket. The server's JsonMapper is configured to log unexpected clientData JWT properties using PHP's `var_export()` without any size or depth bounds; an attacker embeds a deeply nested or massive object structure in an unknown property, causing the PHP process to exhaust all available memory during serialization. A proof-of-concept is publicly available in the GHSA advisory; no CISA KEV listing at time of analysis, but the zero-authentication, pre-auth attack vector and public PoC make this a high-priority patch for any publicly reachable PocketMine-MP instance.
Stored cross-site scripting in Open WebUI's terminal port preview feature allows an authenticated attacker sharing a terminal server with a victim to execute arbitrary JavaScript in the victim's browser at the Open WebUI origin, enabling full account takeover. The vulnerability affects versions 0.8.11 through 0.11.1 and stems from a dangerous iframe sandbox configuration that combines `allow-scripts` with `allow-same-origin`, which together nullify sandbox isolation when content is served from the application's own origin. No public exploit code has been identified at time of analysis, and no active exploitation is confirmed, but the attack is straightforward for any authenticated user on a shared terminal deployment.
Unauthenticated remote denial-of-service in PocketMine-MP before 5.43.1 allows any network client to crash the Minecraft Bedrock server by sending a malformed Certificate field during offline login. The LoginPacketHandler fails to validate the Certificate JSON structure before mapping it to an internal auth chain object, leaving PHP class properties uninitialized and triggering a fatal error that terminates the server process. A publicly available proof-of-concept is referenced in the vendor's GitHub Security Advisory (GHSA-g2fj-p69p-9chp); no CISA KEV listing is confirmed at time of analysis.
Unauthenticated SQL injection in the ELEX WooCommerce Request a Quote WordPress plugin (all versions before 2.4.1) allows remote attackers to extract arbitrary data from the underlying WordPress database without credentials or user interaction. The flaw stems from a user-controlled parameter passed directly into a SQL query without sanitization or escaping, and the CVSS scope change reflects that the injection can reach any table in the shared MySQL/MariaDB instance - including WordPress user credentials, WooCommerce order records, and PII. A publicly available exploit exists per WPScan; the vendor has released a fix in version 2.4.1, and no active exploitation is confirmed in CISA KEV at this time.
Unauthenticated SQL injection in the Quentn WP WordPress plugin before version 1.2.15 allows remote attackers to extract arbitrary data from the underlying database without any credentials. The vulnerability stems from a request parameter that is passed directly into an unprepared SQL query without escaping, enabling full database read access including user credentials, configuration data, and any content stored in the WordPress database. A publicly available exploit exists per WPScan, and the CVSS scope-change indicator (S:C) reflects that the impact crosses into the database component beyond the plugin itself.
Out-of-bounds write in Samsung's Keymaster trustlet - a Trusted Execution Environment (TEE) component running in ARM TrustZone that handles cryptographic key operations - allows local attackers with high privileges to corrupt memory within the secure world, potentially compromising key material or TEE integrity. Affected devices run Android 14 through 17, with a fix delivered in Samsung's SMR Sep-2026 Release 1. No public exploit code or active exploitation has been identified at time of analysis.
OAuth and SCIM identity confusion in Open WebUI 0.6.41-0.10.x (SQLite-backed deployments only) allows unauthenticated remote attackers to hijack arbitrary stored user accounts, including administrator accounts, by presenting an OAuth subject claim containing SQL LIKE wildcard characters. SQLAlchemy's `JSON.contains()` on SQLite compiles to a substring LIKE match rather than an exact equality check, so a crafted `sub` claim such as `%admin%` can resolve to a different stored identity and cause the server to issue the attacker a valid session token for that identity. Vendor-released patch is available in version 0.11.1; no active exploitation has been confirmed.
Denial of service in Open WebUI versions 0.9.0-0.11.0 allows unauthenticated remote attackers to stall the application server and amplify traffic to the configured identity provider by submitting requests to the backchannel-logout OAuth endpoint. The handler fetches the OIDC discovery document and signing keys on every inbound request-including invalid ones-before performing any token validation; additionally, the original synchronous PyJWKClient call blocks the asyncio event loop, so each malicious request can render the single-worker instance unresponsive. No public exploit code has been identified at time of analysis; the issue is fixed in version 0.11.1.
Unauthenticated information disclosure in the Loops & Logic WordPress plugin (all versions before 4.3.0) exposes arbitrary user records - including email addresses and role assignments - and arbitrary site configuration options to any unauthenticated visitor. The plugin's public template-data AJAX action fails to enforce access controls, permitting unauthenticated HTTP requests to retrieve data restricted to privileged users. A publicly available proof-of-concept exists per the WPScan advisory; however, EPSS at 0.17% (7th percentile) and SSVC 'exploitation: none' indicate no confirmed active exploitation at time of analysis.
Memory exhaustion denial of service in PocketMine-MP before 5.32.1 allows any authenticated Bedrock client to crash the server by sending a single crafted ResourcePackClientResponsePacket. The server iterates the client-supplied packIds array without deduplicating UUIDs, so a custom client supplying hundreds of copies of a valid pack UUID causes the server to transmit ResourcePackDataInfoPacket repeatedly, rapidly exhausting PHP process memory. No public KEV listing, but exploit details are publicly available via GHSA-fqqv-56h5-f57g.
Improper privilege management in Open WebUI 0.10.0 through 0.11.0 allows any authenticated low-privilege user with write access to a knowledge base to delete administrator-owned external connection configurations shared across the entire instance. The DELETE /api/v1/knowledge/{id}/delete endpoint in knowledge.py correctly validated the user's write access to their own knowledge base but then cascaded the delete to the underlying shared external connection without verifying admin role or checking whether other knowledge bases depended on that connection. This means a single non-admin user can render all other knowledge bases on the instance that share the same external vector store connection permanently unavailable. No public exploit has been identified at time of analysis; vendor-released patch is available in version 0.11.1.
Memory and CPU exhaustion in PocketMine-MP before 5.39.2 allows any authenticated in-game player to render the game server unresponsive by sending a ModalFormResponsePacket with an arbitrarily large JSON payload. The server processes incoming form response data without enforcing any size limit, enabling an attacker to exhaust server memory and CPU with JSON arrays containing millions of elements. A public proof-of-concept Node.js script is confirmed in vendor advisory GHSA-788v-5pfp-93ff; no public exploit identified at time of analysis in CISA KEV.
Authentication bypass in the shared wp-module-data module (bundled across four Newfold WordPress plugins) allows unauthenticated remote attackers to gain full administrator-level access to any affected WordPress site that lacks a stored Hiive connection token. The defect degenerates the HMAC-style Bearer token verification into a trivially forgeable computation: when the stored connection token is absent, PHP coerces `strrev(false)` to `strrev('')`, reducing the secret salt to the publicly known SHA-256 empty-string hash `e3b0c44...`, while all remaining inputs (HTTP method, URL, body, and the attacker-supplied X-Timestamp header) are fully attacker-controlled, enabling offline token pre-computation. No public exploit code has been confirmed and the vulnerability is not listed in CISA KEV at time of analysis, but full technical details including source code references are publicly disclosed by Wordfence, substantially lowering the barrier to exploitation.
Path traversal in the knowns npm documentation tool (versions ≤ 0.29.1) enables remote unauthenticated attackers to read, create, overwrite, or delete arbitrary files with a .md extension anywhere on the host filesystem, and to create arbitrary directories via os.MkdirAll. The Document API's sanitization function cleanDocPath() strips slashes and .md suffixes but leaves ../ sequences intact, allowing filepath.Join() to resolve paths outside the intended documents directory. In the default deployment - where the Management API binds to all interfaces without authentication - this is directly exploitable with a single crafted HTTP request, and the arbitrary-write primitive may be chained toward code execution. No confirmed active exploitation or public exploit code identified at time of analysis.
Path traversal in Samsung's ImsService (IP Multimedia Subsystem Service) on Android 14 through 17 permits remote unauthenticated attackers to create image files at arbitrary filesystem paths under system server privilege. Reported by Samsung Mobile and patched in SMR Sep-2026 Release 1, the flaw is reachable over LTE and Wi-Fi networks with no user interaction required, as reflected in the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) scoring 8.8. No public exploit code has been identified at time of analysis, and the vulnerability does not appear in the CISA KEV catalog.
Heap-based buffer overflow in Google Chrome's WebRTC component (all versions prior to 153.0.8010.36) enables a remote unauthenticated attacker to potentially execute arbitrary code within the Chrome renderer sandbox by luring a target to a crafted HTML page. The vulnerability is classified CWE-122 and carries a CVSS base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); however, Chromium's own internal severity rating is 'Low,' which is notably discordant and implies that exploitation is constrained to within-sandbox code execution rather than full OS compromise. No public exploit code and no CISA KEV listing have been identified at the time of analysis.
Out-of-bounds read in Google Chrome's Media component (versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a specially crafted HTML page. The vulnerability stems from improper bounds checking during media processing, allowing a remote attacker to read memory beyond intended buffer limits and leverage the resulting data to achieve arbitrary code execution. No public exploit has been identified at time of analysis and EPSS is low (0.35%), but the attack surface is broad given Chrome's ubiquity.
Memory corruption in the Codecs component of Google Chrome prior to 153.0.8010.36 enables remote unauthenticated attackers to execute arbitrary code inside the browser sandbox by delivering a crafted HTML page containing malformed media content. The flaw is classified CWE-119 (improper bounds restriction), rated 'High' by Chromium Security, and carries a CVSS 8.8 base score with a network attack vector requiring only passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, and EPSS stands at a low 0.35% (29th percentile), indicating theoretical rather than observed exploitation.
Out-of-bounds read in zstd-jni versions 1.2.0 through 1.5.7-13 allows attackers who can supply dictionary constructor parameters to crash the JVM and potentially read limited native heap memory. The ZstdDictCompress constructor passed unvalidated offset and length values directly to the C JNI layer, where out-of-range values cause the native code to read beyond the allocated Java heap array. No CISA KEV listing or public exploit has been identified; the CVSS 4.0 score of 8.8 reflects high availability impact via reliable JVM crash and limited confidentiality exposure from native heap reads.
Type confusion (CWE-843) in Chrome's XML processing component allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by enticing a target to visit a crafted HTML page. All Chrome desktop versions prior to 153.0.8010.36 are affected across Windows, macOS, and Linux. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; the impact is further bounded by Chrome's sandbox architecture, which prevents direct OS-level code execution without a secondary sandbox-escape primitive.
Use-after-free in Google Chrome's DevTools component (versions prior to 153.0.8010.36) enables arbitrary code execution within the renderer sandbox when a victim is socially engineered into visiting a crafted HTML page. The CVSS score of 8.8 reflects full C/I/A impact, but Chromium's own internal severity classification of 'Low' signals that exploitation is sandboxed - OS-level compromise requires an additional chained sandbox escape. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Privilege escalation in YITH WooCommerce Waitlist Premium for WordPress (versions ≤3.35.0) allows any subscriber-level authenticated user to manufacture a new WordPress administrator account, achieving full site takeover. The vulnerable AJAX handler add_user_in_waiting_list() is exposed to all logged-in users with no nonce or capability check, and applies parse_str() plus extract() to attacker-supplied POST data before passing the injected variables directly to wp_create_user() and $user->set_role(). No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack mechanics are trivially derivable from the Wordfence disclosure.
Site isolation bypass in Google Chrome's FileAPI component allows a remote attacker who has already compromised the renderer process to escape Chrome's cross-origin isolation boundary via a crafted HTML page. Affected versions are all Chrome releases prior to 153.0.8010.36. This is a second-stage exploit - the FileAPI race condition (CWE-367, TOCTOU) enables escalation from a sandboxed renderer compromise into full cross-origin data access, making it a critical link in a multi-stage sandbox escape chain. No public exploit or CISA KEV listing is identified at time of analysis; EPSS is 0.24% (16th percentile), consistent with the high complexity of the required exploit chain.
Heap-based buffer overflow in the WebRTC component of Google Chrome prior to 153.0.8010.36 allows a remote unauthenticated attacker to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. The RCE is sandbox-confined (CVSS S:U), meaning a chained sandbox-escape exploit would be needed for full host-level compromise. No public exploit or active exploitation has been identified at time of analysis, and EPSS sits at a low 0.24% (15th percentile), consistent with Chromium's own 'Medium' severity designation despite the 8.8 CVSS base score.
Type confusion in V8 (CWE-843) in Google Chrome prior to 153.0.8010.36 allows a remote attacker to achieve arbitrary code execution within the Chrome renderer sandbox by delivering a crafted HTML page. All desktop Chrome installations on unpatched versions are affected, exploitable via drive-by browsing without any authentication or special privileges beyond convincing the victim to visit a malicious page. No public exploit or CISA KEV listing has been confirmed at time of analysis; SSVC rates technical impact as total but exploitation as none, consistent with a low EPSS of 0.23%.
Use-after-free in the Linux kernel Bluetooth ISO stack allows an adjacent unauthenticated attacker to corrupt kernel memory and potentially execute arbitrary code. The flaw is a race condition in iso_conn_ready(): when a BIS listener socket is concurrently closed while an incoming Bluetooth Isochronous connection is being processed, a child socket is allocated that holds a dangling pointer to the now-freed parent socket, which is later dereferenced during disconnect via iso_chan_del() and bt_accept_unlink(). Patches are available across multiple stable kernel branches (6.12.109, 7.2.4, 6.18.50, and 7.3-rc1); no public exploit code or active exploitation has been identified at time of analysis.
Use-after-free in Chrome's Chromecast component allows remote attackers to execute arbitrary code inside the browser sandbox by luring a user to a crafted HTML page. Affected are all Google Chrome releases prior to 153.0.8010.36 across desktop platforms. Exploitation is sandboxed - code execution is confined to the renderer process - but the C:H/I:H/A:H impact rating reflects full compromise of data accessible within that context. No active exploitation has been confirmed and no public proof-of-concept code is known at time of analysis.
Remote code execution inside the Chrome sandbox is possible in Google Chrome versions prior to 153.0.8010.36 via a use-after-free vulnerability in the V8 JavaScript engine, triggered by a specially crafted HTML page. An unauthenticated remote attacker who can lure a user to a malicious page can execute arbitrary code within the Chrome renderer process sandbox - a significant foothold even without a sandbox escape. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.21% reflects low observed exploitation activity, though V8 UAF primitives are historically attractive to threat actors.
Use-after-free in V8, Chrome's JavaScript engine, enables remote code execution within the browser's renderer sandbox when a victim visits a crafted HTML page. All Chrome releases prior to 153.0.8010.36 are affected across desktop platforms. No public exploit has been identified and EPSS sits at 0.21% (12th percentile), but SSVC rates the technical impact as total, and the Chromium security team classified this as High severity.
Use-after-free in Chrome's Input component enables in-sandbox remote code execution against all Chrome versions prior to 153.0.8010.36. The vulnerability is triggered when a victim visits a crafted HTML page, requiring no authentication and no special configuration - only a single browse action. Google has rated this High severity, the patch is available in 153.0.8010.36, and no public exploit has been identified at time of analysis, with EPSS at 0.21%.
Use-after-free in Chrome's Platform component (all versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a crafted HTML page. The Chromium team rated this 'High' severity - consistent with the CVSS 8.8 score and distinguishing it from Critical-rated full sandbox-escape vulnerabilities addressed in the same release cycle. No public exploit code has been identified, and the EPSS score of 0.21% (12th percentile) reflects limited observed exploitation activity at this time; no CISA KEV listing exists.
Use-after-free in Chrome's V8 JavaScript engine allows a remote attacker who can socially engineer a victim into installing a crafted Chrome extension to execute arbitrary code within the browser's renderer sandbox, affecting all Chrome versions prior to 153.0.8010.36. The vulnerability is constrained to in-sandbox execution - it does not constitute a standalone sandbox escape - which aligns with the S:U CVSS metric and Chromium's internal 'Medium' severity rating despite the 8.8 base score. No public exploit code or active exploitation has been identified at time of analysis, and Google has shipped a patch in the stable channel.
Double-free memory corruption in PDFium (Chrome's PDF rendering engine) on Windows allows remote code execution within the Chrome renderer sandbox when a user opens a crafted PDF file. Affected versions are all Chrome releases on Windows prior to 153.0.8010.36, where CWE-415 double-free in the PDFium component enables an attacker-controlled allocation state. No public exploit or CISA KEV listing is confirmed at time of analysis, and EPSS remains low at 0.20% (10th percentile), suggesting exploitation is not yet widespread despite the network-reachable vector.
SQL injection in Siam Ordering (siam-server) 1.0.0 allows remote authenticated attackers to execute arbitrary SQL commands against the backend database. The vulnerability stems from unsafe `${}` string concatenation in MyBatis Mapper files - including AdminMapper.java, MerchantWithdrawRecordMapper.java, and MemberWithdrawRecordMapper.java - which bypasses parameterized query protections. Successful exploitation yields full confidentiality, integrity, and availability impact on the underlying database, confirmed by a proof-of-concept published on GitHub.
Memory corruption in V8, Chrome's JavaScript engine, allows an attacker who can get a user to install a crafted Chrome extension to execute arbitrary code confined within the Chrome sandbox, affecting all Chrome versions prior to 153.0.8010.36. Despite the CVSS 8.8 base score, Chromium's own security team rates this 'Low' severity, reflecting that exploitation is bounded by Chrome's sandbox and does not constitute a full OS-level compromise without a separate sandbox escape primitive. No public exploit code or active exploitation has been identified at time of analysis. Vendor-released patch is available.
Missing authorization in the Views UI framework of Google Chrome prior to 153.0.8010.36 allows remote attackers to bypass system access restrictions via a crafted HTML page requiring social engineering. The vulnerability (CWE-862) resides in Chrome's cross-platform UI layer rather than web content rendering, with full confidentiality, integrity, and availability impact per CVSS C:H/I:H/A:H. No public exploit code or active exploitation has been identified at time of analysis; EPSS of 0.18% (7th percentile) corroborates low current weaponization despite the 8.8 CVSS score.
Site isolation bypass in Google Chrome prior to 153.0.8010.36 allows a remote attacker who has already compromised the renderer process to escape Chrome's cross-site isolation boundary via a crafted file combined with social engineering. The flaw is rooted in incorrect authorization (CWE-863) within the SiteIsolation component, meaning the browser fails to properly enforce origin-based access controls once the renderer is under attacker control. Vendor-released patch 153.0.8010.36 is available; no public exploit has been identified and EPSS sits at 0.16% (6th percentile), consistent with the Chromium team's 'Medium' severity rating despite the CVSS 8.8 base score.
Sandbox escape in bubblewrap prior to 0.12.0 allows a local, low-privileged user to write files or directories to arbitrary host paths outside the sandbox boundary by exploiting symlink resolution during the pre-execution setup phase (CWE-59). The escape occurs via /oldroot - bubblewrap's bind-mounted original root - before the sandboxed process ever starts, meaning no code execution inside the sandbox is needed to trigger it. Distributions including Red Hat Enterprise Linux 8, 9, and 10 and Debian are confirmed affected; the upstream fix is available as bubblewrap 0.12.0 and no public exploit code has been identified at time of analysis.
Unauthorized cryptographic hardware access in KVM for s390 (IBM Z) nested virtualization allows a low-privileged nested guest to access AP queues (hardware crypto devices) that were explicitly revoked from its allocation. When the KVM VSIE subsystem shadows a format0 APCB (Adjunct Processor Control Block) from a crycb type 0 or 1 structure, it only copies bits 0-63 but leaves bits 64-255 unchanged from whatever stale state existed in the vsie shadow page. A nested (L2) guest exploiting this retains access to cryptographic devices beyond those granted by the host hypervisor, potentially exposing cryptographic keys and operations belonging to other workloads. No public exploit has been identified at time of analysis and no CISA KEV listing exists.
Out-of-bounds memory reads in zstd-jni versions 1.1.1 through 1.5.7-13 allow unauthenticated remote attackers to crash the JVM or extract arbitrary frame-size data from unintended memory regions by supplying crafted Zstandard-compressed input with negative or integer-overflowing offset values. Three JNI native methods - findDirectByteBufferFrame, decompressedDirectByteBuffer, and getDirectByteBufferFrame - perform 32-bit signed bounds checks without first validating that src_offset or src_size are non-negative, allowing values near Integer.MIN_VALUE to pass the comparison and drive native code to read unmapped memory. The CVSS 4.0 score of 8.8 reflects a high availability impact (JVM termination) and limited confidentiality impact; no public exploit or KEV listing has been identified at time of analysis.
Unauthenticated remote directory deletion in Chainlit through 2.12.0 allows any network-accessible attacker to recursively destroy arbitrary filesystem directories reachable by the service process. The flaw resides in the socket.io session handler, which accepts a client-supplied sessionId without path sanitization and uses it directly in file system operations - permitting absolute and relative path traversal sequences to escape the intended upload directory. With a CVSS 4.0 score of 8.8 (AV:N/AC:L/AT:N/PR:N/UI:N), exploitation requires no authentication or user interaction; no public exploit or CISA KEV listing has been identified at time of analysis.
Deserialization in t-digest 3.1 through 3.3 allows remote attackers to inject IEEE 754 NaN values as centroid means via crafted byte streams passed to MergingDigest.fromBytes(), bypassing absent validation checks. The injected NaN values corrupt the internal total-ordering invariant of the centroid list, causing sort comparisons to return inconsistent results and degrading subsequent merge operations from O(n log n) to O(n²) algorithmic complexity. The result is severe CPU exhaustion and service delays for any application that deserializes attacker-controlled t-digest payloads; no public exploit code or CISA KEV listing exists at time of analysis.
Arbitrary code execution in GitPython before 3.1.60 is possible when a victim application calls index.commit() on an attacker-controlled repository. The root cause is insufficient validation of the git directory location: GitPython trusts tracked files such as gitdir, commondir, and HEAD to resolve the effective git directory, allowing a crafted repository to redirect that resolution to an attacker-controlled path containing a malicious pre-commit hook. No public exploit has been identified at time of analysis, but the attack is realistic in any Python-based DevOps pipeline, CI/CD system, or tooling that opens and commits to externally sourced repositories.
Remote unauthenticated retrieval of expired one-time secrets in PasswordPusher before 2.11.1 is enabled by a TOCTOU race condition in the expire_after_views view-limit enforcement logic. By issuing multiple simultaneous HTTP requests to the show endpoint, an attacker can read a secret that was configured to self-destruct after a single view, defeating the core confidentiality guarantee the tool is designed to provide. No active exploitation has been confirmed (not in CISA KEV), and no public exploit code has been identified, though the technique requires only basic HTTP concurrency tooling.
SQL injection in SiYuan's fullTextSearchBlock endpoint (versions before v3.8.2) allows read-level database access to the entire blocks table by injecting UNION SELECT statements into the method=1 query parameter. The vulnerability bypasses publish-access controls, exposing document content and sensitive block attributes that the operator intended to keep private. No public exploit or CISA KEV listing is confirmed at time of analysis, but the straightforward UNION-based injection pattern and availability of a GitHub security advisory make reproduction low-effort.