Suse
Monthly
PowerShell smart-quote filename injection in rclone's SFTP backend allows an attacker who controls remote filenames to execute arbitrary PowerShell commands as the victim's SSH account on the server. All rclone versions prior to v1.75.0 are affected when the SFTP remote uses PowerShell as the SSH command shell and server-side hashing is invoked. A proof-of-concept was confirmed by the GHSA advisory author; no CISA KEV listing was present at time of analysis, but the specific attack conditions meaningfully constrain real-world exposure to Windows-hosted or PowerShell-shelled SFTP deployments.
Path traversal in rclone's `serve restic` REST API allows any attacker with network access to the endpoint to read, create, overwrite, or delete objects outside the operator-configured backend directory. The flaw spans rclone v1.40 through v1.74.4 and affects WebDAV, FTP, SFTP, HTTP, and Memory backends - but not S3-compatible or local filesystem backends, which encode `..` as literal filename characters. A fully functional, step-by-step proof of concept has been publicly released; no CISA KEV listing exists at time of analysis.
Unsafe class loading in the ORB (Object Request Broker) component of IBM WebSphere Application Server 8.5, 9.0, and Liberty Continuous Delivery allows a malicious or attacker-controlled IIOP server to force a WebSphere client/server to load and instantiate arbitrary Java classes over the network. Exploitation requires no authentication or user interaction (CVSS 9.8), and successful abuse can lead to loss of confidentiality, integrity, and availability, potentially culminating in remote code execution via dangerous class instantiation. There is no public exploit identified at time of analysis, and EPSS estimates only a 0.44% probability of exploitation in the next 30 days.
Unbounded memory allocation in Rancher Manager's API audit logging middleware enables unauthenticated remote attackers to crash the Rancher management plane via memory exhaustion. When API audit logging is enabled, the audit copyReqBody middleware - positioned ahead of Rancher's APIBodyLimitingHandler in the handler chain - reads entire HTTP request bodies into memory on public login endpoints with no size cap, bypassing the default 1 MiB limit. An attacker sending a small number of concurrent oversized requests to these endpoints can exhaust server memory and terminate the Rancher Manager process, rendering the Rancher API and UI unavailable and severing management control of all downstream Kubernetes clusters. No public exploit has been identified at time of analysis.
Remote denial-of-service in the brace-expansion npm library (all active version lines prior to 1.1.18, 2.1.4, 3.0.6, and 5.0.9) allows unauthenticated attackers to either crash the Node.js process via an uncatchable out-of-memory error with a ~25 KB crafted input, or stall the event loop for over two minutes with a ~400 KB padded-sequence input. Both attack paths bypass the incomplete mitigation introduced in version 5.0.8 for CVE-2026-14257, meaning applications that already patched that predecessor vulnerability remain fully exposed. Publicly available proof-of-concept code is included in the GitHub security advisory; no CISA KEV listing is present at time of analysis.
Path traversal in SiYuan's attribute-view read endpoints allows low-privileged users to read arbitrary JSON files outside the intended storage directory on versions before v3.7.3. The avID parameter is unsanitized across all code branches, enabling RoleReader-level authenticated users - or anonymous clients when publish authentication is disabled - to exfiltrate cross-scope database content stored as JSON on the server filesystem. No public exploit has been identified at time of analysis, and a vendor patch is available in v3.7.3.
SQL injection in SiYuan personal knowledge management (versions <= v3.7.2) lets attackers pass arbitrary SQL statements verbatim to the primary read-write siyuan.db handle via the /api/search/searchEmbedBlock endpoint. Because the endpoint is gated only by CheckAuth, it is reachable with the low-privilege publish RoleReader token - and by fully anonymous users when publish authentication is disabled - and the driver's support for stacked statements allows both reading and modifying content across all opened cleartext notebooks. No public exploit identified at time of analysis, but the flaw was reported by VulnCheck and carries a critical 9.9 CVSS 4.0 score; it is fixed in v3.7.3.
SQL injection in SiYuan's fullTextSearchAssetContent endpoint lets unauthenticated attackers and holders of publish RoleReader tokens execute arbitrary SQL against the read-write asset-content database in all versions before v3.7.3. Because the endpoint is reachable without authentication and the database is writable, attackers can read, alter, or delete data across notebooks - not merely exfiltrate it. No public exploit identified at time of analysis, but the flaw was reported by VulnCheck and carries a CVSS 4.0 base score of 9.9.
Information disclosure in SiYuan (a personal knowledge-management/note-taking application) before v3.7.3 lets anonymous readers or low-privilege publish RoleReader tokens read the full rendered content of documents that were explicitly marked publish-disabled. The getHeadingDeleteTransaction, getHeadingLevelTransaction, and getHeadingInsertTransaction endpoints return rendered block DOM without enforcing publish-access checks, so supplying a target heading block ID leaks restricted content. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis, and this is not listed in CISA KEV.
Broken access control in SiYuan versions before 3.7.3 lets publish-mode readers - including anonymous users when publish Basic Auth is disabled - retrieve the rendered content of publish-forbidden documents by calling the /api/ref/getBacklinkDoc and /api/ref/getBackmentionDoc endpoints directly with a target document ID. Although the corresponding backlink list endpoints correctly filter publish-forbidden documents, these two content endpoints are gated only by CheckAuth and omit the publish-access filter, exposing DOM content and a reference-existence oracle. Reported by VulnCheck; no public exploit identified at time of analysis and not listed in CISA KEV.
Authentication bypass in SiYuan (self-hosted knowledge-management/note-taking app) versions before v3.7.3 allows anonymous readers in publish mode to exfiltrate the full content of password-protected documents. While the primary getDoc endpoint enforces the publish-mode password, sibling content-returning endpoints (getHeadingChildrenDOM, the getHeading*Transaction family, and getBacklinkDoc) omit that check, so an attacker who harvests internal block IDs from reader-accessible endpoints can pull protected content directly. VulnCheck reported the issue and a vendor patch (v3.7.3) is available; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Server-side request forgery in bank-vaults vault-secrets-webhook (<= 1.22.2) lets a low-privileged tenant with ConfigMap or Secret create/update rights in any watched namespace force the cluster-wide admission webhook to make attacker-controlled outbound HTTP requests and exfiltrate ServiceAccount JWTs. The webhook trusts the vault.security.banzaicloud.io/vault-addr annotation with no scheme validation or host allowlist, then synchronously mints a SA token (via cluster-wide serviceaccounts/token:create) and POSTs it to the attacker's address, which can be replayed against the real Vault. A vendor patch (v1.23.1) exists and the reporter published a working PoC, but there is no public exploit identified in the wild and the flaw is not in CISA KEV.
DNS rebinding defeats `nltk.pathsec.urlopen()`'s SSRF filter in NLTK 3.9.4 and earlier, allowing unauthenticated remote attackers to reach loopback addresses, private networks, and cloud instance metadata endpoints - even with `ENFORCE = True` - and receive full, non-blind HTTP responses. The root cause is a TOCTOU gap: validation resolves the hostname once, but `urllib` independently re-resolves it at connect time via a separate `getaddrinfo` call, connecting to whatever the attacker's TTL-0 rebinding record returns on the second lookup. A working proof-of-concept is publicly available in the GHSA advisory, and the `lru_cache` annotation on `_resolve_hostname` creates a false assurance that rebinding is already mitigated, meaning operators who adopted this boundary believe themselves protected when they are not.
Quadratic ReDoS in NLTK ReviewsCorpusReader allows an unauthenticated attacker to hang any application that processes untrusted reviews corpora, by supplying a single crafted line of approximately 100,000 bracket-less words. All NLTK versions through 3.9.4 are affected; the calls reviews(), features(), and sents() are all vulnerable entry points. Publicly available exploit code (PoC) is included in the advisory; no confirmed active exploitation in CISA KEV at time of analysis.
Path traversal in NLTK's NKJPCorpusReader component (versions ≤ 3.9.4) allows attackers who control the `fileids` argument to read arbitrary files outside the configured corpus root, fully defeating the `nltk.pathsec` sandbox even when `ENFORCE=True` is active. The root cause is that `add_root()` builds file paths via plain string concatenation - not the hardened `FileSystemPathPointer` - and downstream code calls the Python builtin `open()` directly, bypassing the `validate_path()` check that NLTK's own SECURITY.md explicitly promises will block unauthorized access. A detailed public PoC is confirmed against nltk 3.9.4; no active exploitation is listed in CISA KEV at time of analysis.
Path traversal in NLTK's FramenetCorpusReader (versions ≤3.9.4) allows a caller-supplied frame name containing ../ sequences to escape the corpus root and read arbitrary XML files accessible to the process, silently bypassing the nltk.pathsec sandbox even when ENFORCE=True is explicitly enabled. Any web service or pipeline that routes user-controlled input into FramenetCorpusReader.frame() is directly exposed, with full parsed content of frame-shaped XML files returned to the caller and a file-existence oracle for all other XML paths. A working proof-of-concept is publicly available in the GitHub security advisory; the vulnerability is not listed in CISA KEV at time of analysis.
Pterodactyl Wings before v1.13.0 crashes when its SFTP handler receives a crafted packet with fewer than 4 bytes in the payload during the SSH connection handshake, triggering a Go runtime index-out-of-bounds panic that kills the Wings daemon. The crash is exploitable by any unauthenticated network attacker who can reach the SFTP port, requiring no credentials because the vulnerable slice operation executes prior to authentication. No public exploit code exists at time of analysis, but the patch diff makes the trigger trivially reproducible: any packet with a short payload in the SSH subsystem channel request is sufficient.
OS command injection in pgAdmin 4 (all versions before 9.18) lets an authenticated user with the commonly-granted tools_import_export_data permission run arbitrary commands on the pgAdmin server host. The Import/Export Data tool renders a user-supplied query into a psql \copy (...) command line; its hand-written parenthesis-balance validator (_is_query_parens_balanced) wrongly assumes standard_conforming_strings=off, treating a backslash-quote (\') as an escaped quote, so a payload like SELECT 'a\') TO PROGRAM 'echo pwned' x' passes validation while real psql (scs=on, the default on PostgreSQL 13-18) closes the string early and executes an attacker-chosen TO PROGRAM clause via popen(). No CISA KEV listing and no standalone public exploit, but the fix commit's regression test discloses a fully working RCE payload; EPSS not provided.
SQL injection sandbox escape in pgAdmin 4's AI Assistant (versions 9.13 through 9.16) lets an attacker break out of the read-only transaction wrapper on the execute_sql_query tool and run arbitrary write or OS commands on the backend PostgreSQL server. The flaw is an incomplete fix for CVE-2026-12045: the sqlparse-based validator disagrees with PostgreSQL over backslash-before-quote string escaping, so a crafted SELECT parses as one statement to the guard but executes as four statements (including a smuggled COMMIT) on the database. Delivery is via indirect prompt injection, and detailed PoC payloads exist publicly in the vendor's regression tests; there is no public exploit identified as used in the wild and no KEV listing, with EPSS data not provided.
Cross-tenant credential theft in pgAdmin 4 (9.0 through 9.16) lets an authenticated non-owner user hijack another user's shared server connection by abusing the Workspaces adhoc-connect endpoint (/misc/workspace/adhoc_connect_server), which clones a target server row verbatim - including its owner's stored database password and tunnel password - and reassigns ownership to the caller. The victim is typically an administrator whose shared server carries saved credentials, and the attacker gains use of those database credentials and any privileges they confer. There is no public exploit identified at time of analysis and it is not on CISA KEV, but the fix (pgAdmin 4 9.17) and the underlying commit are public, and EPSS was not provided.
Command injection in pgAdmin 4's MASTER_PASSWORD_HOOK feature exposes the pgAdmin service account to arbitrary OS command execution by any authenticated user whose identity originates from an external auth source (OAuth/OIDC, Kerberos, webserver headers). Affected deployments span versions 7.2 through 9.16, but only those with the hook configured to use the `%u` substitution token alongside an external IdP where usernames can be attacker-influenced. No public exploit code or CISA KEV listing exists at time of analysis; however, the commit diff publicly discloses the exact vulnerable code path, significantly lowering the barrier to independent exploit development.
SQL injection in pgAdmin 4 through an incomplete remediation of CVE-2026-12044 allows a low-privileged authenticated user to execute arbitrary SQL in a higher-privileged victim's database session. By creating a PostgreSQL object - table, index, publication, or subscription - with an apostrophe in its name (a character PostgreSQL legally permits in quoted identifiers), the attacker plants a payload that fires the moment any other pgAdmin user opens the object's Statistics or Dependencies tab, triggering raw Jinja2 template interpolation in coll_stats.sql, dependencies.sql, and get_position.sql without the qtLiteral escaping applied by the prior fix. The cross-user injection escalates impact well beyond the attacker's own database privileges, with the injected SQL executing under the victim's session credentials. No public exploit has been identified at time of analysis, and this CVE has not been added to the CISA KEV catalog.
Sensitive-credential disclosure leading to full node compromise in Pterodactyl Wings before v1.12.3 lets a low-privileged, authenticated panel user (a server owner or a subuser holding startup.update) smuggle a {{config.*}} placeholder through a user-editable egg variable, causing Wings to resolve it against its entire daemon configuration and write secrets - including the node daemon token, token_id, and Docker registry credentials - into a file the user can read via the file manager or SFTP. Because the daemon token is both the Panel⇆Wings API bearer and the HMAC signing key for every JWT the node issues, an attacker can then forge tokens and act against every server on the node. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS is 9.9 and the affected templating pattern is common across stock and community eggs.
Confidential Active Directory attribute disclosure in Samba's Active Directory Domain Controller allows an authenticated low-privilege domain user to read protected directory attributes by abusing how LDAP Compare requests are handled. Because Samba fails to validate user-supplied attribute names (LDAP filter injection, CWE-90) and runs the resulting internal search in a trusted context, normal ACL enforcement is bypassed; in gMSA-enabled deployments this permits extraction of msKds-RootKeyData and offline derivation of Group Managed Service Account passwords, which can escalate to full domain compromise. No public exploit identified at time of analysis and the issue is not listed in CISA KEV, but a vendor patch is available.
Memory-corruption remote code execution in Google Chrome's Dawn WebGPU graphics component affects all Desktop builds prior to 151.0.7922.72, where a crafted HTML page triggers a use-after-free (CWE-416) that lets a remote attacker run arbitrary code - though confined inside the renderer sandbox, which is why Chromium rated it Low despite the CVSS 8.8. Exploitation requires only that a victim load a malicious page (UI:R), with no authentication. There is no public exploit identified at time of analysis and the CVE is not on CISA KEV.
Remote code execution in Google Chrome's PDFium component (versions prior to 151.0.7922.72) allows a remote attacker to run arbitrary code - confined to the renderer sandbox - when a victim opens a maliciously crafted PDF. The flaw is a CWE-416 use-after-free reported by Google's own Chrome team and fixed in the July 2026 Stable channel update; Chromium rated its intrinsic severity Low because execution is contained within the sandbox, though NVD's CVSS scores it 8.8. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Local privilege escalation in the Google Chrome Updater on Windows (versions prior to 151.0.7922.72) lets a low-privileged local attacker win a race condition and substitute a malicious file to elevate privileges. The flaw carries a CVSS 7.0 score, and while Chromium rates its security severity as Low, the SSVC technical impact is Total. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Arbitrary code execution in Google Chrome's V8 JavaScript engine allows a remote attacker to run code inside the renderer sandbox when a victim visits a crafted HTML page, affecting all desktop builds prior to 151.0.7922.72. The flaw is a CWE-843 type confusion in V8 and carries a CVSS 8.8 due to network reach and high CIA impact, though execution is confined to the sandbox and Chromium rates the security severity as Low. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but a vendor patch is available.
Remote code execution in Google Chrome's V8 JavaScript engine (all versions prior to 151.0.7922.72) allows a remote attacker who lures a victim to a crafted HTML page to execute arbitrary code, though confined inside the renderer sandbox rather than achieving a full sandbox escape. Google rated the Chromium security severity as Low, and there is no public exploit identified at time of analysis and no evidence of active exploitation (CISA SSVC exploitation status: none). Exploitation hinges on winning a timing race, so despite the 7.5 CVSS score it is regarded as difficult to trigger reliably.
Remote code execution within the browser's renderer sandbox affects Google Chrome desktop builds prior to 151.0.7922.72, stemming from an inappropriate implementation in the Passwords component (CWE-269). A remote attacker who lures a victim to a crafted HTML page can execute arbitrary code, but execution is confined to the sandbox - which is why Chromium rated the underlying issue Low severity despite the CVSS 8.8. No public exploit identified at time of analysis, and the fix is already shipping in the Stable channel.
Sandboxed remote code execution in Google Chrome desktop before 151.0.7922.72 lets a remote attacker run arbitrary code within the renderer sandbox when a victim opens a crafted HTML page. The flaw stems from an inappropriate implementation in Chrome's Scheduling component; Google rated it Chromium-Low severity and no public exploit has been identified, though the NVD CVSS of 8.8 reflects the high per-system impact once triggered. Exploitation requires user interaction (visiting a malicious page) and, because code executes inside the sandbox rather than escaping it, real-world impact is constrained absent a chained sandbox-escape bug.
Sandbox-constrained arbitrary code execution in Google Chrome's V8 JavaScript engine affects all desktop builds prior to 151.0.7922.72, where a crafted Chrome extension abuses an inappropriate V8 implementation to run attacker code inside the renderer sandbox. Exploitation requires convincing a user to install a malicious extension, and Google internally rated the Chromium security severity as Low. There is no public exploit identified at time of analysis and CISA SSVC records exploitation status as 'none'.
Remote code execution in Google Chrome on macOS prior to 151.0.7922.72 stems from an inappropriate implementation in the Safe Browsing component, where a remote attacker can trigger arbitrary code execution by luring a victim into opening or downloading a malicious file. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R) requires no privileges but does require user interaction, and Google has shipped a fixed Stable channel build. Despite the 8.8 CVSS, Chromium rated the underlying issue Low severity, EPSS is only 0.20% (10th percentile), and there is no public exploit identified at time of analysis.
Memory-exhaustion denial of service in OliveTin (versions 3000.0.0 through 3000.16.x) allows a remote unauthenticated attacker to crash the service by repeatedly hitting the OAuth2 login endpoint. Each /oauth/login request permanently adds an entry to an in-memory registeredStates map that was never expired, deleted, or bounded, so sustained requests grow memory until the process is killed. No public exploit is identified at time of analysis, EPSS was not provided, and this is not in CISA KEV, but the flaw is trivially triggerable when OAuth2 authentication is enabled.
Server-side request forgery allowlist bypass in the V programming language standard library (net.urllib / net.http) through version 0.5.2 lets remote unauthenticated attackers reach internal network services that a host-based allowlist was meant to block. The flaw stems from a parser differential: net.urllib.parse() and net.http.get() disagree on how a backslash in a URL's authority is handled, so validation and connection resolve to different hosts. Publicly available exploit code exists and the issue was reported by VulnCheck, though it is not listed in CISA KEV (no public evidence of active exploitation at time of analysis).
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can create Flow/Output custom resources to break out of the generated fluent.conf and achieve remote code execution inside the shared Fluentd aggregator. Because the FluentRender renderer writes CRD values (e.g. record_transformer records) into the config without escaping newlines, an attacker injects a `<match **>` block using the core `@type exec` plugin to run arbitrary commands. A working proof-of-concept is published in the GitHub advisory (GHSA-mjqf-28ph-426h); publicly available exploit code exists, but there is no CISA KEV listing indicating active exploitation.
Improper authorization in Zitadel's user self-management API lets any authenticated user obtain the plaintext email/phone verification code for their own account and mark those contact details as verified without ever proving control of them. This is an incomplete-fix follow-up to CVE-2026-27946 (GHSA-282g-fhmx-xf54): that advisory blocked setting email.is_verified:true via UpdateHumanUser, but additional code paths still returned the verification code to the self-managing user. It affects Zitadel 2.43.0-2.71.19, 3.0.0-3.4.10, and 4.0.0-4.15.0, letting attackers claim ownership of emails/phones they do not control and bypass email-based security policies. No public exploit identified at time of analysis.
Server-side request forgery in Prebid Server (Go) versions before 4.4.0 lets remote unauthenticated attackers coerce the ad server into making HTTP requests to attacker-chosen destinations. Multiple bidder adapters (e.g. acuityads, adhese, bidmachine) interpolate an unvalidated user-supplied 'host'/'account' bid-request parameter directly into outbound URLs, enabling extraction of host-environment data and access to internal network services. No public exploit identified at time of analysis, but the fix commit and GHSA advisory are public; EPSS was not provided.
Denial of service in open-iscsi's bundled open-isns library (iSNS implementation) lets an unauthenticated man-in-the-middle attacker crash the iSNS client/server by triggering a double free in the attribute-decoding routines. The flaw stems from freed pointers not being nulled in isns_attr_type_string_decode and isns_attr_type_opaque_decode, so a crafted iSNS message causes the same allocation to be freed twice. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; impact is limited to availability, with no confidentiality or integrity effect.
Denial of service in the cJSON C library (versions through 1.7.19) arises from exponential algorithmic complexity in the cJSON_Compare() function, which recursively descends into each shared object subtree twice per level with no depth guard. Applications that call cJSON_Compare() on attacker-influenced JSON that is structurally equal to a reference document can be forced to burn hours of CPU on a document of only a few hundred bytes (nesting depth around 40), with cost roughly doubling per added level. No public exploit identified at time of analysis and the issue is not on CISA KEV; impact is compute exhaustion only, with no confidentiality or integrity effect.
Denial of service in cJSON (DaveGamble's C JSON parser) through version 1.7.19 lets a remote attacker crash any application that applies an untrusted RFC 6902 JSON Patch through cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive(). By combining add and copy operations that graft duplicated subtrees, an attacker inflates document nesting far beyond the parser's 1000-level limit, and the unbounded recursion in cJSON_Delete() (plus a permissive CJSON_CIRCULAR_LIMIT of 10000 in cJSON_Duplicate()) exhausts the thread stack. Reported by VulnCheck with a public technical write-up; there is no public exploit identified at time of analysis and it is not on CISA KEV.
Local privilege escalation in open-iscsi's iscsiuio component lets any unprivileged local user connect to the iscsiuio control socket and issue commands normally restricted to root, because the daemon validated peer credentials against the wrong file descriptor. The flaw (CWE-863 Incorrect Authorization) was reported by SUSE and fixed upstream in commit 668ca1df; there is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Out-of-bounds write in GNU binutils' BFD library (bfd/elf32-dlx.c) lets a crafted ELF/DLX object file corrupt memory and achieve arbitrary code execution when parsed by any BFD-consuming tool (objdump, readelf, strip, ld, nm, objcopy). Reported by Red Hat and tracked against RHEL 6-10, Hardened Images and OpenShift 4, the flaw is only reachable when binutils is compiled with the DLX backend (typically --enable-targets=all), so exposure is gated by a non-default build option. There is no public exploit identified at time of analysis (not in CISA KEV), though the researcher demonstrated code execution via a File Stream Oriented Programming (FSOP) attack on glibc FILE structures.
Remote file disclosure in openhole-server v0.1.1 and earlier allows unauthenticated attackers to read arbitrary files from tunneled local services. The server forwards URL-decoded request paths, causing percent-encoded dot-segments (%2e%2e) and slashes to be decoded into path traversal sequences (../) before reaching the backend. Exploitation requires a tunneled local service that resolves paths without canonicalization, and the vulnerability is fixed in v0.1.2 by preserving raw percent-encoding.
Remote denial of service in gotd/td versions before 0.145.1 allows unauthenticated attackers to exhaust memory and CPU by sending a crafted MTProto unencrypted packet with a maliciously inflated dataLen field, causing excessive allocation before length validation. No authentication or session is required, and the vulnerability is reachable during the handshake phase. There is no evidence of active exploitation and no public exploit has been identified.
Improper enforcement of the `--no-delete` flag in goshs WebDAV server allows unauthorized file deletion or overwrite. The `MOVE` handler incorrectly treats the verb as write-only without checking the delete restriction, permitting remote attackers using WebDAV clients to bypass the `--no-delete` boundary via a `MOVE` request with `Overwrite: T`. A public proof-of-concept exists, and the vendor has patched this in version 2.1.4.
An authorization bypass in goshs’s bulk zip-download route allows unauthenticated attackers to read any file protected solely by a per-folder .goshs ACL, circumventing both folder-based authentication and per-file block lists. The vulnerability affects goshs v2.x up to 2.1.0 and all v1.x versions. A proof-of-concept is publicly available, demonstrating the bypass against a patched version that had addressed a related ACL gap on write/delete routes but left the read path unprotected.
An incomplete fix for CVE-2026-40884 in goshs v2.1.3 allows unauthenticated attackers to bypass SFTP authentication and gain full file read, write, and delete access when the server is started with `-b 'user:' -sftp` and without the `-fkf` flag. Publicly available exploit code exists, and the root cause is a logic flaw in the password handler registration that was not fully addressed in the prior patch.
Denial of service in rouille 0.1.6 through 3.6.2 allows remote unauthenticated attackers to crash the server
Privilege escalation in Pterodactyl Wings allows authenticated subusers to upload arbitrary files without the required file.create permission by reusing lower-privilege panel-signed JWTs (e.g., from websocket authentication or file downloads). A public proof-of-concept demonstrates how a subuser with only websocket.connect can upload files to the server, potentially compromising its container. Patches introduce JWT scoping in Panel 1.12.3 and Wings 1.12.2.
Denial of service in GitHub MCP Server versions below 1.1.0 allows any unauthenticated attacker to crash the server by sending a malformed completion/complete JSON-RPC request with missing parameters. The nil pointer dereference occurs before authentication checks, making exploitation trivial. Publicly available exploit code exists, enabling immediate termination of the process.
Information disclosure in the Xen hypervisor's DM_OP (device model operation) hypercall handling allows a device model caller to leak uninitialized hypervisor stack memory because certain operations do not verify that the required number of buffers was supplied before reading them. Affected Xen builds process DM_OP requests using structures that may remain uninitialized ('stack rubble'), disclosing low-value memory contents (CWE-665) with limited integrity and availability side effects. No public exploit has been identified at time of analysis; SSVC records exploitation status as none, EPSS is low (0.26%, 18th percentile), and it is not on CISA KEV.
We are tasked to produce a comprehensive analysis JSON for CVE-2026-62432. We must synthesize all provided data: CVE description, CVSS, tags, SSVC, references, etc. The output must be plain-text strings per field, no arrays, no markdown. First, parse the input: - CVE ID: CVE-2026-62432 - Description: "The EVTCHNOP_expand_array hypercall checks for whether FIFO event channels are enabled, but without holding the correct lock. It can race with EVTCHNOP_reset, resulting in dereferencing a NULL pointer." - CVSS: 7.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L - CWE: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) - Reported by: security@xen.org - Tags: Denial Of Service, Race Condition - SSVC: Exploitation: none, Automatable: yes, Technical Impact: partial - ENISA EUVD ID: EUVD-2026-49785 - References include xenbits advisory, NVD, oss-security. No listed KEV status, no POC mention, no explicit patch version. The patch data is missing (we need to check references? Not provided explicitly. We must infer from multiple sources. The description mentions xen and hypercall, so it's a Xen hypervisor vulnerability. We need to fill out each field. Let's systematically analyze. - product_name: From description, "EVTCHNOP_expand_array hypercall" implies Xen hypervisor. The vulnerability is in Xen's event channel mechanism. So product is "Xen Hypervisor". Could also say "Xen", but "Xen Hypervisor" is 2 words. According to rule "1-3 words ONLY", "Xen Hypervisor" fits. - summary: Must be 2-3 sentence plain-language synthesis. Not copy description. Start with impact verb and product. Example: "Race condition in Xen Hypervisor can lead to denial of service via NULL pointer dereference." But also mention what attacker can do. The CVSS suggests partial impacts in C/I/A, so maybe more than DoS? But tags say Denial Of Service, Race Condition, and description says dereferencing NULL pointer, so likely denial of service (sys
A divide-by-zero vulnerability in Xen's Viridian periodic STIMER handling allows an attacker with guest VM access to crash the hypervisor, causing denial of service. The issue arises from an unchecked user-controlled divisor that can be set to zero, triggering a #DE fault. No active exploitation is known per SSVC, though the attack is automatable and requires no guest-level privileges.
Information disclosure in Xen hypervisor's CMOS emulation allows a guest VM to exploit a race condition in the index caching mechanism, leading to an out-of-bounds read of hypervisor memory. A malicious guest can repeatedly manipulate the CMOS index port while the hypervisor processes an access, potentially leaking sensitive data from the host or other VMs. No active exploitation or public exploit code is known at this time.
Privilege escalation in Xen hypervisor due to lock acquisition unfairness in platform operations allows authenticated control-domain users to bypass XSM/Flask permission checks. An attacker with low-privileged authenticated access can exploit the race condition to execute privileged operations, potentially gaining full control of the system. The vulnerability carries a CVSS 8.8 rating but has no known active exploitation or public exploit code.
Denial of service in Xen hypervisor running PV guests without hardware-assisted paging (HAP) or shim allows a malicious guest or remote attacker to monopolize CPU via long-running shadow paging operations, impacting host availability. This issue has been deprecated rather than patched, as modern alternatives (HAP, PVH, shim) eliminate
Denial-of-service in Xen's Xenstore component allows unprivileged guest domains to crash the host by triggering a bitmap teardown in an error path of the XEN_DOMCTL_get_domain_state operation. Exploit code is publicly available, though no active exploitation is confirmed. The attack is automatable, requiring no user interaction or guest authentication.
Use-after-free vulnerability in Safari’s web content processing allows remote attackers to execute arbitrary code on affected Apple devices when a user visits a malicious website. Affected versions include Safari prior to 26.6, iOS and iPadOS prior to 26.6, macOS Tahoe prior to 26.6, visionOS prior to 26.6, and watchOS prior to 26.6. No public exploit or active exploitation has been identified, and EPSS indicates a low probability of exploitation (0.13%).
Memory corruption in Apple Safari 26.x allows remote code execution via processing maliciously crafted web content. This buffer overflow (CWE-119) affects all Apple platforms—iOS, iPadOS, macOS, visionOS, and watchOS—requiring user interaction to visit a malicious webpage. While the CVSS score is critical (8.8), EPSS (0.13%) indicates low current exploitation probability and no KEV listing or public exploit exists.
Information disclosure in Apple Safari and OS-integrated WebKit allows websites to detect if a user has visited specific URLs. Safari, iOS, iPadOS, macOS, tvOS, visionOS, and watchOS prior to version 26.6 are affected. No public exploit code or active attacks have been reported, and the probability of exploitation is very low (EPSS 0.17%).
Out-of-bounds read in Apple Safari's web content processing can crash the browser and potentially leak sensitive memory contents. This vulnerability affects all Apple platforms where Safari rendering is used and is fixed in Safari 26.6, iOS/iPadOS 26.6, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6, and watchOS 26.6. Exploitation requires user interaction to visit a malicious site; no known active exploits or public proof-of-concept exist.
Reflected cross-site scripting in XMLRPC-C Library versions 1.07 through 1.67.01 allows unauthenticated attackers to execute arbitrary JavaScript when a victim clicks a crafted link, as the error page component reflects unsanitized user input. This can lead to theft of sensitive session data or other browser-accessible information from affected services. No public exploit code or active exploitation has been reported at this time.
Use-after-free in SQLite 3.41's JSON parser allows remote code execution. A remote attacker can deliver a crafted JSON payload; if a user or application processes it with SQLite, the vulnerability triggers memory corruption, potentially enabling full system compromise. A proof-of-concept advisory is publicly available, though no active exploitation has been confirmed.
Use-after-free in SQLite 3.41's expression-evaluation path lets an attacker who can submit a crafted SQL statement crash the process, leak adjacent memory, or potentially achieve code execution. The flaw stems from sqlite3ReleaseTempReg() prematurely freeing a temporary register that exprComputeOperands() then dereferences. Rated CVSS 7.5 (AV:N/AC:H/PR:L); publicly available exploit code exists per the CISA SSVC 'poc' determination, but it is not on the CISA KEV list and EPSS is low (0.24%, 16th percentile), indicating no evidence of widespread active exploitation.
Use-after-free in SQLite 3.41 expression parsing leads to memory corruption, allowing remote attackers to crash applications and leak sensitive memory contents via crafted SQL queries. Public proof-of-concept exists but there is no evidence of active exploitation. The vulnerability is triggered by sending malicious SQL statements that cause the parser to access a freed expression object.
Remote denial of service and heap memory leak in SQLite 3.41 via the json_remove() function allows attackers with the ability to execute SQL queries to crash the database process or leak sensitive heap data. A use-after-free in jsonRemoveFunc is triggered by malformed JSON and a deep path parameter; publicly available proof-of-concept code exists, and low EPSS risk indicates limited exploitation likelihood.
Memory corruption in SQLite 3.41's ORDER BY parsing allows remote attackers to crash the database process or leak sensitive data via crafted SQL queries. A use-after-free in ExprList handling, triggered by an ORDER BY clause with many items, can also lead to arbitrary code execution under specific memory conditions. A public advisory exists, but no active exploitation (KEV) or EPSS data is available.
Use-after-free in SQLite 3.41 allows remote attackers supplying crafted SQL to trigger memory corruption during parsing, leading to denial of service, sensitive information leakage, and potential arbitrary code execution.
Heap-based buffer overflow in LibRaw 0.21 allows remote code execution when a user opens a maliciously crafted RAW image file. The flaw resides in the stretch() and fuji_rotate() functions and requires user interaction, enabling a complete compromise of confidentiality, integrity, and availability. Proof-of-concept code exists, but no active exploitation has been confirmed.
Local privilege escalation in the Linux kernel's ARM FFA firmware interface allows an unprivileged local attacker to achieve arbitrary code execution by triggering an out-of-bounds write when processing PARTITION_INFO_GET descriptors. The kernel fails to validate firmware-supplied indices, enabling a heap buffer overflow that can corrupt memory. Patches are available, no public exploit exists, and EPSS indicates low exploitation probability (0.21%).
Use-after-free in the Linux kernel's usbio (USB I/O bridge) driver allows a local, low-privileged attacker to corrupt kernel slab memory during USB device disconnect, potentially achieving privilege escalation or triggering a kernel panic. The bug lies in usbio_disconnect(), which iterates the client list in reverse using list_for_each_entry_reverse() - a macro that reads client->link.prev after the loop body, but auxiliary_device_uninit() can free the current client before that read, dereferencing freed slab memory. Patches are confirmed in Linux stable branches 6.18.39, 7.1.4, and 7.2-rc3; no public exploit or active exploitation is identified at time of analysis.
Heap buffer overflow in the Linux kernel's rtl8723bs staging WiFi driver (rtw_cfg80211_set_wpa_ie()) allows a local low-privileged user to corrupt kernel memory by one byte via a crafted nl80211 connect request, enabling potential privilege escalation to kernel context. The 256-byte supplicant_ie array in struct security_priv overflows when a WPA IE with length 255 is supplied, writing 257 bytes and clobbering the adjacent last_mic_err_time field; a flawed length check in rtw_parse_wpa_ie() using u8 narrowing silently permits the overflow. Patches are available across all active stable kernels; EPSS is 0.23% and no public exploit or CISA KEV listing exists at time of analysis.
Use-after-free in the Linux kernel Bluetooth MGMT subsystem allows a local attacker with low privileges to trigger kernel memory corruption via a race condition between add_device and remove_device operations. The flaw exists in add_device_complete(), which dereferences a hci_conn_params pointer without holding hci_dev_lock, while a concurrent MGMT_OP_REMOVE_DEVICE path frees the same object under that lock. KASAN confirms exploitation as slab-use-after-free; no public exploit or active exploitation (CISA KEV) has been identified, and patches have been released across multiple stable branches.
Use-after-free memory corruption in the Linux kernel's netpoll subsystem allows a local attacker or concurrent kernel path to access freed memory during the netpoll shutdown sequence. The flaw exists because cancel_delayed_work() - called from softirq context during __netpoll_cleanup() - does not block until the TX worker finishes, permitting queue_process() to dereference a kfree'd npinfo struct via container_of(). KASAN confirms the UAF; patches are available across multiple stable kernel branches, and no public exploit or KEV listing exists at time of analysis.
Use-after-free memory corruption in the Linux kernel's NXP i.MX8 ISI (Image Sensing Interface) media driver is triggered during module removal (rmmod of imx8_isi), confirmed by KASAN slab-use-after-free reports. The root cause is an incorrect teardown order in mxc_isi_remove(): the crossbar cleanup frees media entity pads before the V4L2 cleanup has finished removing media links that reference those same pads, resulting in a dangling pointer dereference in __media_entity_remove_link(). No public exploit has been identified at time of analysis, and with EPSS at 0.21% (11th percentile), real-world weaponization appears unlikely despite the CVSS 7.8 score.
Out-of-bounds memory read in the Linux kernel's btnxpuart Bluetooth driver exposes kernel memory to a malicious or compromised NXP Bluetooth UART controller. The vulnerability exists in nxp_recv_fw_req_v3(), which handles firmware download requests during v3 controller initialization: when the controller supplies a crafted 32-bit offset or 16-bit length value that pushes past the end of the firmware image, the driver reads arbitrary kernel memory and transmits it back to the controller over UART. The parallel v1 path (nxp_recv_fw_req_v1()) already contained the equivalent bounds check; the v3 path lacked it. No active exploitation is confirmed (not in CISA KEV) and EPSS is 0.21% (11th percentile), consistent with the narrow local/hardware attack surface.
Memory leak in the Linux kernel's SMB client encrypted receive path (receive_encrypted_standard()) allows a local low-privileged user or a cooperative malicious SMB server to exhaust kernel heap memory, with potential for heap grooming-based privilege escalation. The bug was introduced with commit b24df3e30cbf and affects multiple stable kernel series from 4.19 onward. No public exploit code exists and EPSS is 0.22%, but the kernel team's classification of CWE-787 and a C:H/I:H/A:H CVSS score reflect the Linux security team's assessment that the leaked kernel buffer is exploitable beyond simple resource exhaustion.
Double-free memory corruption in the Linux kernel's Qualcomm CPU frequency hardware driver (qcom-cpufreq-hw) allows a local low-privileged attacker on Qualcomm SoC-based systems to trigger kernel heap corruption, potentially escalating privileges to root. The flaw originates in qcom_cpufreq_hw_cpu_exit(), which incorrectly calls kfree() on memory allocated via devm_kzalloc() - memory already tracked by the kernel's device resource management (devres) system. This results in a double-free when the platform device is subsequently detached and devres performs its own cleanup. No public exploit code exists and EPSS is low (0.21%), consistent with a static-analysis discovery rather than active exploitation.
Use-After-Free in the Linux kernel HID letsketch driver allows local exploitation during device unbind, potentially enabling kernel memory corruption and privilege escalation on affected systems. The letsketch_probe() function arms a per-device kernel timer (inrange_timer) with a 100 ms timeout, but no .remove callback exists to drain the timer before devm cleanup frees letsketch_data and input_dev structures on USB unplug or rmmod, producing a UAF read/write into freed kernel memory. Patches are backported across six stable kernel branches; no public exploit code exists and EPSS is 0.21% (12th percentile), reflecting the niche device requirement and race-condition complexity.
Use-after-free in the Linux kernel HID appleir driver allows a local attacker to corrupt kernel memory during device removal, potentially achieving privilege escalation. The race condition exists between the key_up_timer callback (armed by appleir_raw_event() on each keydown/key-repeat) and hid_hw_stop(), which frees the underlying input_dev before the timer is drained. A second race window, where a USB URB completion during hid_hw_stop() can re-arm the timer via mod_timer(), means a simple teardown reorder is insufficient — the fix introduces a spinlock-gated 'removing' flag combined with timer_shutdown_sync() to permanently disable further callbacks. No public exploit has been identified at time of analysis, and EPSS is 0.22% (13th percentile).
Use-after-free in the Linux kernel HID lg-g15 driver allows a local attacker to trigger kernel memory corruption by racing device input events against USB keyboard removal. The driver allocates lg_g15_data via devm and schedules work items from HID report handlers (backlight cycle key on G15, G15 v2, G510), but lacked a remove callback to cancel pending work before devres freed the allocation. On kernel versions from approximately 5.5 through the unfixed stable branches, unplugging the keyboard while a work item is pending causes the worker to dereference freed memory via container_of, potentially enabling local privilege escalation. No public exploit has been identified and EPSS is 0.22% (13th percentile), indicating no observed widespread exploitation.
Incorrect RCU lock annotations in the Linux kernel's BPF LPM trie map implementation (`kernel/bpf/lpm_trie.c`) cause lockdep false positives on debug kernels when sleepable BPF programs access `BPF_MAP_TYPE_LPM_TRIE` maps via lookup, update, or delete operations. The mismatch arises because sleepable BPF programs hold `rcu_read_lock_trace()` while the trie code asserts `rcu_read_lock_bh_held()` or `rcu_read_lock_held()`, producing repeated 'suspicious RCU usage' kernel warnings per distinct callsite. The Linux kernel developers explicitly state no actual use-after-free occurs, since Tasks Trace RCU already serializes against trie node reclaim; however, the incorrect annotation undermines lockdep's ability to detect future regressions and is increasingly impactful as sleepable BPF LSM programs become common in production security tooling. No public exploit exists and no CISA KEV listing has been issued.
Use-after-free and memory leak in the Linux kernel's EHCI and FOTG210 USB isochronous submit paths expose systems running kernel versions from 2.6.15 through 7.1.3 to local kernel memory corruption by a low-privileged user. When an isochronous URB submission fails before the staged schedule handoff - either because the host controller becomes inaccessible or usb_hcd_link_urb_to_ep() returns an error - the ehci_iso_sched allocation is not freed and urb->hcpriv retains a dangling pointer, creating a UAF condition. No public exploit exists and the EPSS score is 0.21% (12th percentile), but vendor-released patches across multiple stable branches are available and should be applied to eliminate the risk.
Use-after-free in the Linux kernel USB gadget UDC subsystem exposes systems with DWC3-based USB controllers to a race condition between usb_del_gadget() and gadget_match_driver(), enabling a NULL pointer dereference that can crash the kernel or enable privilege escalation on unpatched systems. The flaw affects all major Linux stable branches from 5.15.x through 7.1.x prior to the patched releases, and is particularly relevant for embedded Linux, Android-based devices, and IoT hardware that use USB gadget/device mode. No public exploit has been identified at time of analysis, and EPSS remains at 0.21% (12th percentile), reflecting current low exploitation interest.
Use-after-free in the Linux kernel's idmouse USB fingerprint driver allows a low-privileged local attacker to corrupt kernel memory by racing a device disconnect against a file-descriptor release, potentially enabling local privilege escalation to root. The bug stems from `mutex_unlock()` accessing the freed driver-data structure after the lock is released, a documented non-atomic behavior; the fix introduces a `kref` reference counter to correctly manage object lifetime. Patches are available across all active stable branches; no active exploitation or public exploit has been reported.
Use-after-free in the Linux kernel's USB ldusb driver allows a local unprivileged user to corrupt kernel memory by racing disconnect() against release() on a connected USB device. The root cause is that mutex_unlock() is documented as non-atomic and may access the mutex object after it logically releases the lock, creating a window where the driver data structure can be freed while still in use. No public exploit has been identified at time of analysis, and EPSS is low (0.22%), but the C:H/I:H/A:H CVSS impact vector reflects the potential for full kernel privilege escalation if successfully triggered.
Use-after-free in the Linux kernel's USB iowarrior driver exposes systems with Code Mercantile IO-Warrior USB devices to kernel memory corruption, potentially enabling local privilege escalation to root. The defect exists because submitted write URBs are not cancelled during close(), leaving them in-flight at disconnect time; the completion handler then fires against already-freed device structures. No public exploit code has been identified at time of analysis, and EPSS at 0.22% (13th percentile) reflects minimal observed exploitation pressure, though the C:H/I:H/A:H CVSS impact reflects genuine kernel-level consequence.
Use-after-free in the Linux kernel USB iowarrior driver allows a local unprivileged user to corrupt kernel memory when a USB device disconnect races with a file release operation. The root cause is that mutex_unlock() is documented as non-atomic and may access the mutex structure after releasing the lock, meaning the driver data object can be freed while mutex_unlock() is still executing. An attacker who can trigger the race - by opening the iowarrior device and simultaneously provoking a USB disconnect - may achieve kernel memory corruption leading to privilege escalation. No public exploit code exists and EPSS is low (0.21%), but the impact class is standard kernel UAF.
The Linux kernel's legousbtower USB driver contains a use-after-free race condition between the release() and disconnect() code paths, present since Linux 2.6.25. An authenticated local user with a LEGO USB Tower device attached can trigger the race at disconnect time to corrupt freed kernel memory, potentially gaining elevated privileges or crashing the system. Patches have been issued across all active stable branches (5.10, 5.15, 6.1, 6.6, 6.12, 6.18, 7.1); no public exploit code or CISA KEV listing exists at time of analysis.
PowerShell smart-quote filename injection in rclone's SFTP backend allows an attacker who controls remote filenames to execute arbitrary PowerShell commands as the victim's SSH account on the server. All rclone versions prior to v1.75.0 are affected when the SFTP remote uses PowerShell as the SSH command shell and server-side hashing is invoked. A proof-of-concept was confirmed by the GHSA advisory author; no CISA KEV listing was present at time of analysis, but the specific attack conditions meaningfully constrain real-world exposure to Windows-hosted or PowerShell-shelled SFTP deployments.
Path traversal in rclone's `serve restic` REST API allows any attacker with network access to the endpoint to read, create, overwrite, or delete objects outside the operator-configured backend directory. The flaw spans rclone v1.40 through v1.74.4 and affects WebDAV, FTP, SFTP, HTTP, and Memory backends - but not S3-compatible or local filesystem backends, which encode `..` as literal filename characters. A fully functional, step-by-step proof of concept has been publicly released; no CISA KEV listing exists at time of analysis.
Unsafe class loading in the ORB (Object Request Broker) component of IBM WebSphere Application Server 8.5, 9.0, and Liberty Continuous Delivery allows a malicious or attacker-controlled IIOP server to force a WebSphere client/server to load and instantiate arbitrary Java classes over the network. Exploitation requires no authentication or user interaction (CVSS 9.8), and successful abuse can lead to loss of confidentiality, integrity, and availability, potentially culminating in remote code execution via dangerous class instantiation. There is no public exploit identified at time of analysis, and EPSS estimates only a 0.44% probability of exploitation in the next 30 days.
Unbounded memory allocation in Rancher Manager's API audit logging middleware enables unauthenticated remote attackers to crash the Rancher management plane via memory exhaustion. When API audit logging is enabled, the audit copyReqBody middleware - positioned ahead of Rancher's APIBodyLimitingHandler in the handler chain - reads entire HTTP request bodies into memory on public login endpoints with no size cap, bypassing the default 1 MiB limit. An attacker sending a small number of concurrent oversized requests to these endpoints can exhaust server memory and terminate the Rancher Manager process, rendering the Rancher API and UI unavailable and severing management control of all downstream Kubernetes clusters. No public exploit has been identified at time of analysis.
Remote denial-of-service in the brace-expansion npm library (all active version lines prior to 1.1.18, 2.1.4, 3.0.6, and 5.0.9) allows unauthenticated attackers to either crash the Node.js process via an uncatchable out-of-memory error with a ~25 KB crafted input, or stall the event loop for over two minutes with a ~400 KB padded-sequence input. Both attack paths bypass the incomplete mitigation introduced in version 5.0.8 for CVE-2026-14257, meaning applications that already patched that predecessor vulnerability remain fully exposed. Publicly available proof-of-concept code is included in the GitHub security advisory; no CISA KEV listing is present at time of analysis.
Path traversal in SiYuan's attribute-view read endpoints allows low-privileged users to read arbitrary JSON files outside the intended storage directory on versions before v3.7.3. The avID parameter is unsanitized across all code branches, enabling RoleReader-level authenticated users - or anonymous clients when publish authentication is disabled - to exfiltrate cross-scope database content stored as JSON on the server filesystem. No public exploit has been identified at time of analysis, and a vendor patch is available in v3.7.3.
SQL injection in SiYuan personal knowledge management (versions <= v3.7.2) lets attackers pass arbitrary SQL statements verbatim to the primary read-write siyuan.db handle via the /api/search/searchEmbedBlock endpoint. Because the endpoint is gated only by CheckAuth, it is reachable with the low-privilege publish RoleReader token - and by fully anonymous users when publish authentication is disabled - and the driver's support for stacked statements allows both reading and modifying content across all opened cleartext notebooks. No public exploit identified at time of analysis, but the flaw was reported by VulnCheck and carries a critical 9.9 CVSS 4.0 score; it is fixed in v3.7.3.
SQL injection in SiYuan's fullTextSearchAssetContent endpoint lets unauthenticated attackers and holders of publish RoleReader tokens execute arbitrary SQL against the read-write asset-content database in all versions before v3.7.3. Because the endpoint is reachable without authentication and the database is writable, attackers can read, alter, or delete data across notebooks - not merely exfiltrate it. No public exploit identified at time of analysis, but the flaw was reported by VulnCheck and carries a CVSS 4.0 base score of 9.9.
Information disclosure in SiYuan (a personal knowledge-management/note-taking application) before v3.7.3 lets anonymous readers or low-privilege publish RoleReader tokens read the full rendered content of documents that were explicitly marked publish-disabled. The getHeadingDeleteTransaction, getHeadingLevelTransaction, and getHeadingInsertTransaction endpoints return rendered block DOM without enforcing publish-access checks, so supplying a target heading block ID leaks restricted content. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis, and this is not listed in CISA KEV.
Broken access control in SiYuan versions before 3.7.3 lets publish-mode readers - including anonymous users when publish Basic Auth is disabled - retrieve the rendered content of publish-forbidden documents by calling the /api/ref/getBacklinkDoc and /api/ref/getBackmentionDoc endpoints directly with a target document ID. Although the corresponding backlink list endpoints correctly filter publish-forbidden documents, these two content endpoints are gated only by CheckAuth and omit the publish-access filter, exposing DOM content and a reference-existence oracle. Reported by VulnCheck; no public exploit identified at time of analysis and not listed in CISA KEV.
Authentication bypass in SiYuan (self-hosted knowledge-management/note-taking app) versions before v3.7.3 allows anonymous readers in publish mode to exfiltrate the full content of password-protected documents. While the primary getDoc endpoint enforces the publish-mode password, sibling content-returning endpoints (getHeadingChildrenDOM, the getHeading*Transaction family, and getBacklinkDoc) omit that check, so an attacker who harvests internal block IDs from reader-accessible endpoints can pull protected content directly. VulnCheck reported the issue and a vendor patch (v3.7.3) is available; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Server-side request forgery in bank-vaults vault-secrets-webhook (<= 1.22.2) lets a low-privileged tenant with ConfigMap or Secret create/update rights in any watched namespace force the cluster-wide admission webhook to make attacker-controlled outbound HTTP requests and exfiltrate ServiceAccount JWTs. The webhook trusts the vault.security.banzaicloud.io/vault-addr annotation with no scheme validation or host allowlist, then synchronously mints a SA token (via cluster-wide serviceaccounts/token:create) and POSTs it to the attacker's address, which can be replayed against the real Vault. A vendor patch (v1.23.1) exists and the reporter published a working PoC, but there is no public exploit identified in the wild and the flaw is not in CISA KEV.
DNS rebinding defeats `nltk.pathsec.urlopen()`'s SSRF filter in NLTK 3.9.4 and earlier, allowing unauthenticated remote attackers to reach loopback addresses, private networks, and cloud instance metadata endpoints - even with `ENFORCE = True` - and receive full, non-blind HTTP responses. The root cause is a TOCTOU gap: validation resolves the hostname once, but `urllib` independently re-resolves it at connect time via a separate `getaddrinfo` call, connecting to whatever the attacker's TTL-0 rebinding record returns on the second lookup. A working proof-of-concept is publicly available in the GHSA advisory, and the `lru_cache` annotation on `_resolve_hostname` creates a false assurance that rebinding is already mitigated, meaning operators who adopted this boundary believe themselves protected when they are not.
Quadratic ReDoS in NLTK ReviewsCorpusReader allows an unauthenticated attacker to hang any application that processes untrusted reviews corpora, by supplying a single crafted line of approximately 100,000 bracket-less words. All NLTK versions through 3.9.4 are affected; the calls reviews(), features(), and sents() are all vulnerable entry points. Publicly available exploit code (PoC) is included in the advisory; no confirmed active exploitation in CISA KEV at time of analysis.
Path traversal in NLTK's NKJPCorpusReader component (versions ≤ 3.9.4) allows attackers who control the `fileids` argument to read arbitrary files outside the configured corpus root, fully defeating the `nltk.pathsec` sandbox even when `ENFORCE=True` is active. The root cause is that `add_root()` builds file paths via plain string concatenation - not the hardened `FileSystemPathPointer` - and downstream code calls the Python builtin `open()` directly, bypassing the `validate_path()` check that NLTK's own SECURITY.md explicitly promises will block unauthorized access. A detailed public PoC is confirmed against nltk 3.9.4; no active exploitation is listed in CISA KEV at time of analysis.
Path traversal in NLTK's FramenetCorpusReader (versions ≤3.9.4) allows a caller-supplied frame name containing ../ sequences to escape the corpus root and read arbitrary XML files accessible to the process, silently bypassing the nltk.pathsec sandbox even when ENFORCE=True is explicitly enabled. Any web service or pipeline that routes user-controlled input into FramenetCorpusReader.frame() is directly exposed, with full parsed content of frame-shaped XML files returned to the caller and a file-existence oracle for all other XML paths. A working proof-of-concept is publicly available in the GitHub security advisory; the vulnerability is not listed in CISA KEV at time of analysis.
Pterodactyl Wings before v1.13.0 crashes when its SFTP handler receives a crafted packet with fewer than 4 bytes in the payload during the SSH connection handshake, triggering a Go runtime index-out-of-bounds panic that kills the Wings daemon. The crash is exploitable by any unauthenticated network attacker who can reach the SFTP port, requiring no credentials because the vulnerable slice operation executes prior to authentication. No public exploit code exists at time of analysis, but the patch diff makes the trigger trivially reproducible: any packet with a short payload in the SSH subsystem channel request is sufficient.
OS command injection in pgAdmin 4 (all versions before 9.18) lets an authenticated user with the commonly-granted tools_import_export_data permission run arbitrary commands on the pgAdmin server host. The Import/Export Data tool renders a user-supplied query into a psql \copy (...) command line; its hand-written parenthesis-balance validator (_is_query_parens_balanced) wrongly assumes standard_conforming_strings=off, treating a backslash-quote (\') as an escaped quote, so a payload like SELECT 'a\') TO PROGRAM 'echo pwned' x' passes validation while real psql (scs=on, the default on PostgreSQL 13-18) closes the string early and executes an attacker-chosen TO PROGRAM clause via popen(). No CISA KEV listing and no standalone public exploit, but the fix commit's regression test discloses a fully working RCE payload; EPSS not provided.
SQL injection sandbox escape in pgAdmin 4's AI Assistant (versions 9.13 through 9.16) lets an attacker break out of the read-only transaction wrapper on the execute_sql_query tool and run arbitrary write or OS commands on the backend PostgreSQL server. The flaw is an incomplete fix for CVE-2026-12045: the sqlparse-based validator disagrees with PostgreSQL over backslash-before-quote string escaping, so a crafted SELECT parses as one statement to the guard but executes as four statements (including a smuggled COMMIT) on the database. Delivery is via indirect prompt injection, and detailed PoC payloads exist publicly in the vendor's regression tests; there is no public exploit identified as used in the wild and no KEV listing, with EPSS data not provided.
Cross-tenant credential theft in pgAdmin 4 (9.0 through 9.16) lets an authenticated non-owner user hijack another user's shared server connection by abusing the Workspaces adhoc-connect endpoint (/misc/workspace/adhoc_connect_server), which clones a target server row verbatim - including its owner's stored database password and tunnel password - and reassigns ownership to the caller. The victim is typically an administrator whose shared server carries saved credentials, and the attacker gains use of those database credentials and any privileges they confer. There is no public exploit identified at time of analysis and it is not on CISA KEV, but the fix (pgAdmin 4 9.17) and the underlying commit are public, and EPSS was not provided.
Command injection in pgAdmin 4's MASTER_PASSWORD_HOOK feature exposes the pgAdmin service account to arbitrary OS command execution by any authenticated user whose identity originates from an external auth source (OAuth/OIDC, Kerberos, webserver headers). Affected deployments span versions 7.2 through 9.16, but only those with the hook configured to use the `%u` substitution token alongside an external IdP where usernames can be attacker-influenced. No public exploit code or CISA KEV listing exists at time of analysis; however, the commit diff publicly discloses the exact vulnerable code path, significantly lowering the barrier to independent exploit development.
SQL injection in pgAdmin 4 through an incomplete remediation of CVE-2026-12044 allows a low-privileged authenticated user to execute arbitrary SQL in a higher-privileged victim's database session. By creating a PostgreSQL object - table, index, publication, or subscription - with an apostrophe in its name (a character PostgreSQL legally permits in quoted identifiers), the attacker plants a payload that fires the moment any other pgAdmin user opens the object's Statistics or Dependencies tab, triggering raw Jinja2 template interpolation in coll_stats.sql, dependencies.sql, and get_position.sql without the qtLiteral escaping applied by the prior fix. The cross-user injection escalates impact well beyond the attacker's own database privileges, with the injected SQL executing under the victim's session credentials. No public exploit has been identified at time of analysis, and this CVE has not been added to the CISA KEV catalog.
Sensitive-credential disclosure leading to full node compromise in Pterodactyl Wings before v1.12.3 lets a low-privileged, authenticated panel user (a server owner or a subuser holding startup.update) smuggle a {{config.*}} placeholder through a user-editable egg variable, causing Wings to resolve it against its entire daemon configuration and write secrets - including the node daemon token, token_id, and Docker registry credentials - into a file the user can read via the file manager or SFTP. Because the daemon token is both the Panel⇆Wings API bearer and the HMAC signing key for every JWT the node issues, an attacker can then forge tokens and act against every server on the node. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS is 9.9 and the affected templating pattern is common across stock and community eggs.
Confidential Active Directory attribute disclosure in Samba's Active Directory Domain Controller allows an authenticated low-privilege domain user to read protected directory attributes by abusing how LDAP Compare requests are handled. Because Samba fails to validate user-supplied attribute names (LDAP filter injection, CWE-90) and runs the resulting internal search in a trusted context, normal ACL enforcement is bypassed; in gMSA-enabled deployments this permits extraction of msKds-RootKeyData and offline derivation of Group Managed Service Account passwords, which can escalate to full domain compromise. No public exploit identified at time of analysis and the issue is not listed in CISA KEV, but a vendor patch is available.
Memory-corruption remote code execution in Google Chrome's Dawn WebGPU graphics component affects all Desktop builds prior to 151.0.7922.72, where a crafted HTML page triggers a use-after-free (CWE-416) that lets a remote attacker run arbitrary code - though confined inside the renderer sandbox, which is why Chromium rated it Low despite the CVSS 8.8. Exploitation requires only that a victim load a malicious page (UI:R), with no authentication. There is no public exploit identified at time of analysis and the CVE is not on CISA KEV.
Remote code execution in Google Chrome's PDFium component (versions prior to 151.0.7922.72) allows a remote attacker to run arbitrary code - confined to the renderer sandbox - when a victim opens a maliciously crafted PDF. The flaw is a CWE-416 use-after-free reported by Google's own Chrome team and fixed in the July 2026 Stable channel update; Chromium rated its intrinsic severity Low because execution is contained within the sandbox, though NVD's CVSS scores it 8.8. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Local privilege escalation in the Google Chrome Updater on Windows (versions prior to 151.0.7922.72) lets a low-privileged local attacker win a race condition and substitute a malicious file to elevate privileges. The flaw carries a CVSS 7.0 score, and while Chromium rates its security severity as Low, the SSVC technical impact is Total. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Arbitrary code execution in Google Chrome's V8 JavaScript engine allows a remote attacker to run code inside the renderer sandbox when a victim visits a crafted HTML page, affecting all desktop builds prior to 151.0.7922.72. The flaw is a CWE-843 type confusion in V8 and carries a CVSS 8.8 due to network reach and high CIA impact, though execution is confined to the sandbox and Chromium rates the security severity as Low. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but a vendor patch is available.
Remote code execution in Google Chrome's V8 JavaScript engine (all versions prior to 151.0.7922.72) allows a remote attacker who lures a victim to a crafted HTML page to execute arbitrary code, though confined inside the renderer sandbox rather than achieving a full sandbox escape. Google rated the Chromium security severity as Low, and there is no public exploit identified at time of analysis and no evidence of active exploitation (CISA SSVC exploitation status: none). Exploitation hinges on winning a timing race, so despite the 7.5 CVSS score it is regarded as difficult to trigger reliably.
Remote code execution within the browser's renderer sandbox affects Google Chrome desktop builds prior to 151.0.7922.72, stemming from an inappropriate implementation in the Passwords component (CWE-269). A remote attacker who lures a victim to a crafted HTML page can execute arbitrary code, but execution is confined to the sandbox - which is why Chromium rated the underlying issue Low severity despite the CVSS 8.8. No public exploit identified at time of analysis, and the fix is already shipping in the Stable channel.
Sandboxed remote code execution in Google Chrome desktop before 151.0.7922.72 lets a remote attacker run arbitrary code within the renderer sandbox when a victim opens a crafted HTML page. The flaw stems from an inappropriate implementation in Chrome's Scheduling component; Google rated it Chromium-Low severity and no public exploit has been identified, though the NVD CVSS of 8.8 reflects the high per-system impact once triggered. Exploitation requires user interaction (visiting a malicious page) and, because code executes inside the sandbox rather than escaping it, real-world impact is constrained absent a chained sandbox-escape bug.
Sandbox-constrained arbitrary code execution in Google Chrome's V8 JavaScript engine affects all desktop builds prior to 151.0.7922.72, where a crafted Chrome extension abuses an inappropriate V8 implementation to run attacker code inside the renderer sandbox. Exploitation requires convincing a user to install a malicious extension, and Google internally rated the Chromium security severity as Low. There is no public exploit identified at time of analysis and CISA SSVC records exploitation status as 'none'.
Remote code execution in Google Chrome on macOS prior to 151.0.7922.72 stems from an inappropriate implementation in the Safe Browsing component, where a remote attacker can trigger arbitrary code execution by luring a victim into opening or downloading a malicious file. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R) requires no privileges but does require user interaction, and Google has shipped a fixed Stable channel build. Despite the 8.8 CVSS, Chromium rated the underlying issue Low severity, EPSS is only 0.20% (10th percentile), and there is no public exploit identified at time of analysis.
Memory-exhaustion denial of service in OliveTin (versions 3000.0.0 through 3000.16.x) allows a remote unauthenticated attacker to crash the service by repeatedly hitting the OAuth2 login endpoint. Each /oauth/login request permanently adds an entry to an in-memory registeredStates map that was never expired, deleted, or bounded, so sustained requests grow memory until the process is killed. No public exploit is identified at time of analysis, EPSS was not provided, and this is not in CISA KEV, but the flaw is trivially triggerable when OAuth2 authentication is enabled.
Server-side request forgery allowlist bypass in the V programming language standard library (net.urllib / net.http) through version 0.5.2 lets remote unauthenticated attackers reach internal network services that a host-based allowlist was meant to block. The flaw stems from a parser differential: net.urllib.parse() and net.http.get() disagree on how a backslash in a URL's authority is handled, so validation and connection resolve to different hosts. Publicly available exploit code exists and the issue was reported by VulnCheck, though it is not listed in CISA KEV (no public evidence of active exploitation at time of analysis).
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can create Flow/Output custom resources to break out of the generated fluent.conf and achieve remote code execution inside the shared Fluentd aggregator. Because the FluentRender renderer writes CRD values (e.g. record_transformer records) into the config without escaping newlines, an attacker injects a `<match **>` block using the core `@type exec` plugin to run arbitrary commands. A working proof-of-concept is published in the GitHub advisory (GHSA-mjqf-28ph-426h); publicly available exploit code exists, but there is no CISA KEV listing indicating active exploitation.
Improper authorization in Zitadel's user self-management API lets any authenticated user obtain the plaintext email/phone verification code for their own account and mark those contact details as verified without ever proving control of them. This is an incomplete-fix follow-up to CVE-2026-27946 (GHSA-282g-fhmx-xf54): that advisory blocked setting email.is_verified:true via UpdateHumanUser, but additional code paths still returned the verification code to the self-managing user. It affects Zitadel 2.43.0-2.71.19, 3.0.0-3.4.10, and 4.0.0-4.15.0, letting attackers claim ownership of emails/phones they do not control and bypass email-based security policies. No public exploit identified at time of analysis.
Server-side request forgery in Prebid Server (Go) versions before 4.4.0 lets remote unauthenticated attackers coerce the ad server into making HTTP requests to attacker-chosen destinations. Multiple bidder adapters (e.g. acuityads, adhese, bidmachine) interpolate an unvalidated user-supplied 'host'/'account' bid-request parameter directly into outbound URLs, enabling extraction of host-environment data and access to internal network services. No public exploit identified at time of analysis, but the fix commit and GHSA advisory are public; EPSS was not provided.
Denial of service in open-iscsi's bundled open-isns library (iSNS implementation) lets an unauthenticated man-in-the-middle attacker crash the iSNS client/server by triggering a double free in the attribute-decoding routines. The flaw stems from freed pointers not being nulled in isns_attr_type_string_decode and isns_attr_type_opaque_decode, so a crafted iSNS message causes the same allocation to be freed twice. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; impact is limited to availability, with no confidentiality or integrity effect.
Denial of service in the cJSON C library (versions through 1.7.19) arises from exponential algorithmic complexity in the cJSON_Compare() function, which recursively descends into each shared object subtree twice per level with no depth guard. Applications that call cJSON_Compare() on attacker-influenced JSON that is structurally equal to a reference document can be forced to burn hours of CPU on a document of only a few hundred bytes (nesting depth around 40), with cost roughly doubling per added level. No public exploit identified at time of analysis and the issue is not on CISA KEV; impact is compute exhaustion only, with no confidentiality or integrity effect.
Denial of service in cJSON (DaveGamble's C JSON parser) through version 1.7.19 lets a remote attacker crash any application that applies an untrusted RFC 6902 JSON Patch through cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive(). By combining add and copy operations that graft duplicated subtrees, an attacker inflates document nesting far beyond the parser's 1000-level limit, and the unbounded recursion in cJSON_Delete() (plus a permissive CJSON_CIRCULAR_LIMIT of 10000 in cJSON_Duplicate()) exhausts the thread stack. Reported by VulnCheck with a public technical write-up; there is no public exploit identified at time of analysis and it is not on CISA KEV.
Local privilege escalation in open-iscsi's iscsiuio component lets any unprivileged local user connect to the iscsiuio control socket and issue commands normally restricted to root, because the daemon validated peer credentials against the wrong file descriptor. The flaw (CWE-863 Incorrect Authorization) was reported by SUSE and fixed upstream in commit 668ca1df; there is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Out-of-bounds write in GNU binutils' BFD library (bfd/elf32-dlx.c) lets a crafted ELF/DLX object file corrupt memory and achieve arbitrary code execution when parsed by any BFD-consuming tool (objdump, readelf, strip, ld, nm, objcopy). Reported by Red Hat and tracked against RHEL 6-10, Hardened Images and OpenShift 4, the flaw is only reachable when binutils is compiled with the DLX backend (typically --enable-targets=all), so exposure is gated by a non-default build option. There is no public exploit identified at time of analysis (not in CISA KEV), though the researcher demonstrated code execution via a File Stream Oriented Programming (FSOP) attack on glibc FILE structures.
Remote file disclosure in openhole-server v0.1.1 and earlier allows unauthenticated attackers to read arbitrary files from tunneled local services. The server forwards URL-decoded request paths, causing percent-encoded dot-segments (%2e%2e) and slashes to be decoded into path traversal sequences (../) before reaching the backend. Exploitation requires a tunneled local service that resolves paths without canonicalization, and the vulnerability is fixed in v0.1.2 by preserving raw percent-encoding.
Remote denial of service in gotd/td versions before 0.145.1 allows unauthenticated attackers to exhaust memory and CPU by sending a crafted MTProto unencrypted packet with a maliciously inflated dataLen field, causing excessive allocation before length validation. No authentication or session is required, and the vulnerability is reachable during the handshake phase. There is no evidence of active exploitation and no public exploit has been identified.
Improper enforcement of the `--no-delete` flag in goshs WebDAV server allows unauthorized file deletion or overwrite. The `MOVE` handler incorrectly treats the verb as write-only without checking the delete restriction, permitting remote attackers using WebDAV clients to bypass the `--no-delete` boundary via a `MOVE` request with `Overwrite: T`. A public proof-of-concept exists, and the vendor has patched this in version 2.1.4.
An authorization bypass in goshs’s bulk zip-download route allows unauthenticated attackers to read any file protected solely by a per-folder .goshs ACL, circumventing both folder-based authentication and per-file block lists. The vulnerability affects goshs v2.x up to 2.1.0 and all v1.x versions. A proof-of-concept is publicly available, demonstrating the bypass against a patched version that had addressed a related ACL gap on write/delete routes but left the read path unprotected.
An incomplete fix for CVE-2026-40884 in goshs v2.1.3 allows unauthenticated attackers to bypass SFTP authentication and gain full file read, write, and delete access when the server is started with `-b 'user:' -sftp` and without the `-fkf` flag. Publicly available exploit code exists, and the root cause is a logic flaw in the password handler registration that was not fully addressed in the prior patch.
Denial of service in rouille 0.1.6 through 3.6.2 allows remote unauthenticated attackers to crash the server
Privilege escalation in Pterodactyl Wings allows authenticated subusers to upload arbitrary files without the required file.create permission by reusing lower-privilege panel-signed JWTs (e.g., from websocket authentication or file downloads). A public proof-of-concept demonstrates how a subuser with only websocket.connect can upload files to the server, potentially compromising its container. Patches introduce JWT scoping in Panel 1.12.3 and Wings 1.12.2.
Denial of service in GitHub MCP Server versions below 1.1.0 allows any unauthenticated attacker to crash the server by sending a malformed completion/complete JSON-RPC request with missing parameters. The nil pointer dereference occurs before authentication checks, making exploitation trivial. Publicly available exploit code exists, enabling immediate termination of the process.
Information disclosure in the Xen hypervisor's DM_OP (device model operation) hypercall handling allows a device model caller to leak uninitialized hypervisor stack memory because certain operations do not verify that the required number of buffers was supplied before reading them. Affected Xen builds process DM_OP requests using structures that may remain uninitialized ('stack rubble'), disclosing low-value memory contents (CWE-665) with limited integrity and availability side effects. No public exploit has been identified at time of analysis; SSVC records exploitation status as none, EPSS is low (0.26%, 18th percentile), and it is not on CISA KEV.
We are tasked to produce a comprehensive analysis JSON for CVE-2026-62432. We must synthesize all provided data: CVE description, CVSS, tags, SSVC, references, etc. The output must be plain-text strings per field, no arrays, no markdown. First, parse the input: - CVE ID: CVE-2026-62432 - Description: "The EVTCHNOP_expand_array hypercall checks for whether FIFO event channels are enabled, but without holding the correct lock. It can race with EVTCHNOP_reset, resulting in dereferencing a NULL pointer." - CVSS: 7.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L - CWE: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) - Reported by: security@xen.org - Tags: Denial Of Service, Race Condition - SSVC: Exploitation: none, Automatable: yes, Technical Impact: partial - ENISA EUVD ID: EUVD-2026-49785 - References include xenbits advisory, NVD, oss-security. No listed KEV status, no POC mention, no explicit patch version. The patch data is missing (we need to check references? Not provided explicitly. We must infer from multiple sources. The description mentions xen and hypercall, so it's a Xen hypervisor vulnerability. We need to fill out each field. Let's systematically analyze. - product_name: From description, "EVTCHNOP_expand_array hypercall" implies Xen hypervisor. The vulnerability is in Xen's event channel mechanism. So product is "Xen Hypervisor". Could also say "Xen", but "Xen Hypervisor" is 2 words. According to rule "1-3 words ONLY", "Xen Hypervisor" fits. - summary: Must be 2-3 sentence plain-language synthesis. Not copy description. Start with impact verb and product. Example: "Race condition in Xen Hypervisor can lead to denial of service via NULL pointer dereference." But also mention what attacker can do. The CVSS suggests partial impacts in C/I/A, so maybe more than DoS? But tags say Denial Of Service, Race Condition, and description says dereferencing NULL pointer, so likely denial of service (sys
A divide-by-zero vulnerability in Xen's Viridian periodic STIMER handling allows an attacker with guest VM access to crash the hypervisor, causing denial of service. The issue arises from an unchecked user-controlled divisor that can be set to zero, triggering a #DE fault. No active exploitation is known per SSVC, though the attack is automatable and requires no guest-level privileges.
Information disclosure in Xen hypervisor's CMOS emulation allows a guest VM to exploit a race condition in the index caching mechanism, leading to an out-of-bounds read of hypervisor memory. A malicious guest can repeatedly manipulate the CMOS index port while the hypervisor processes an access, potentially leaking sensitive data from the host or other VMs. No active exploitation or public exploit code is known at this time.
Privilege escalation in Xen hypervisor due to lock acquisition unfairness in platform operations allows authenticated control-domain users to bypass XSM/Flask permission checks. An attacker with low-privileged authenticated access can exploit the race condition to execute privileged operations, potentially gaining full control of the system. The vulnerability carries a CVSS 8.8 rating but has no known active exploitation or public exploit code.
Denial of service in Xen hypervisor running PV guests without hardware-assisted paging (HAP) or shim allows a malicious guest or remote attacker to monopolize CPU via long-running shadow paging operations, impacting host availability. This issue has been deprecated rather than patched, as modern alternatives (HAP, PVH, shim) eliminate
Denial-of-service in Xen's Xenstore component allows unprivileged guest domains to crash the host by triggering a bitmap teardown in an error path of the XEN_DOMCTL_get_domain_state operation. Exploit code is publicly available, though no active exploitation is confirmed. The attack is automatable, requiring no user interaction or guest authentication.
Use-after-free vulnerability in Safari’s web content processing allows remote attackers to execute arbitrary code on affected Apple devices when a user visits a malicious website. Affected versions include Safari prior to 26.6, iOS and iPadOS prior to 26.6, macOS Tahoe prior to 26.6, visionOS prior to 26.6, and watchOS prior to 26.6. No public exploit or active exploitation has been identified, and EPSS indicates a low probability of exploitation (0.13%).
Memory corruption in Apple Safari 26.x allows remote code execution via processing maliciously crafted web content. This buffer overflow (CWE-119) affects all Apple platforms—iOS, iPadOS, macOS, visionOS, and watchOS—requiring user interaction to visit a malicious webpage. While the CVSS score is critical (8.8), EPSS (0.13%) indicates low current exploitation probability and no KEV listing or public exploit exists.
Information disclosure in Apple Safari and OS-integrated WebKit allows websites to detect if a user has visited specific URLs. Safari, iOS, iPadOS, macOS, tvOS, visionOS, and watchOS prior to version 26.6 are affected. No public exploit code or active attacks have been reported, and the probability of exploitation is very low (EPSS 0.17%).
Out-of-bounds read in Apple Safari's web content processing can crash the browser and potentially leak sensitive memory contents. This vulnerability affects all Apple platforms where Safari rendering is used and is fixed in Safari 26.6, iOS/iPadOS 26.6, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6, and watchOS 26.6. Exploitation requires user interaction to visit a malicious site; no known active exploits or public proof-of-concept exist.
Reflected cross-site scripting in XMLRPC-C Library versions 1.07 through 1.67.01 allows unauthenticated attackers to execute arbitrary JavaScript when a victim clicks a crafted link, as the error page component reflects unsanitized user input. This can lead to theft of sensitive session data or other browser-accessible information from affected services. No public exploit code or active exploitation has been reported at this time.
Use-after-free in SQLite 3.41's JSON parser allows remote code execution. A remote attacker can deliver a crafted JSON payload; if a user or application processes it with SQLite, the vulnerability triggers memory corruption, potentially enabling full system compromise. A proof-of-concept advisory is publicly available, though no active exploitation has been confirmed.
Use-after-free in SQLite 3.41's expression-evaluation path lets an attacker who can submit a crafted SQL statement crash the process, leak adjacent memory, or potentially achieve code execution. The flaw stems from sqlite3ReleaseTempReg() prematurely freeing a temporary register that exprComputeOperands() then dereferences. Rated CVSS 7.5 (AV:N/AC:H/PR:L); publicly available exploit code exists per the CISA SSVC 'poc' determination, but it is not on the CISA KEV list and EPSS is low (0.24%, 16th percentile), indicating no evidence of widespread active exploitation.
Use-after-free in SQLite 3.41 expression parsing leads to memory corruption, allowing remote attackers to crash applications and leak sensitive memory contents via crafted SQL queries. Public proof-of-concept exists but there is no evidence of active exploitation. The vulnerability is triggered by sending malicious SQL statements that cause the parser to access a freed expression object.
Remote denial of service and heap memory leak in SQLite 3.41 via the json_remove() function allows attackers with the ability to execute SQL queries to crash the database process or leak sensitive heap data. A use-after-free in jsonRemoveFunc is triggered by malformed JSON and a deep path parameter; publicly available proof-of-concept code exists, and low EPSS risk indicates limited exploitation likelihood.
Memory corruption in SQLite 3.41's ORDER BY parsing allows remote attackers to crash the database process or leak sensitive data via crafted SQL queries. A use-after-free in ExprList handling, triggered by an ORDER BY clause with many items, can also lead to arbitrary code execution under specific memory conditions. A public advisory exists, but no active exploitation (KEV) or EPSS data is available.
Use-after-free in SQLite 3.41 allows remote attackers supplying crafted SQL to trigger memory corruption during parsing, leading to denial of service, sensitive information leakage, and potential arbitrary code execution.
Heap-based buffer overflow in LibRaw 0.21 allows remote code execution when a user opens a maliciously crafted RAW image file. The flaw resides in the stretch() and fuji_rotate() functions and requires user interaction, enabling a complete compromise of confidentiality, integrity, and availability. Proof-of-concept code exists, but no active exploitation has been confirmed.
Local privilege escalation in the Linux kernel's ARM FFA firmware interface allows an unprivileged local attacker to achieve arbitrary code execution by triggering an out-of-bounds write when processing PARTITION_INFO_GET descriptors. The kernel fails to validate firmware-supplied indices, enabling a heap buffer overflow that can corrupt memory. Patches are available, no public exploit exists, and EPSS indicates low exploitation probability (0.21%).
Use-after-free in the Linux kernel's usbio (USB I/O bridge) driver allows a local, low-privileged attacker to corrupt kernel slab memory during USB device disconnect, potentially achieving privilege escalation or triggering a kernel panic. The bug lies in usbio_disconnect(), which iterates the client list in reverse using list_for_each_entry_reverse() - a macro that reads client->link.prev after the loop body, but auxiliary_device_uninit() can free the current client before that read, dereferencing freed slab memory. Patches are confirmed in Linux stable branches 6.18.39, 7.1.4, and 7.2-rc3; no public exploit or active exploitation is identified at time of analysis.
Heap buffer overflow in the Linux kernel's rtl8723bs staging WiFi driver (rtw_cfg80211_set_wpa_ie()) allows a local low-privileged user to corrupt kernel memory by one byte via a crafted nl80211 connect request, enabling potential privilege escalation to kernel context. The 256-byte supplicant_ie array in struct security_priv overflows when a WPA IE with length 255 is supplied, writing 257 bytes and clobbering the adjacent last_mic_err_time field; a flawed length check in rtw_parse_wpa_ie() using u8 narrowing silently permits the overflow. Patches are available across all active stable kernels; EPSS is 0.23% and no public exploit or CISA KEV listing exists at time of analysis.
Use-after-free in the Linux kernel Bluetooth MGMT subsystem allows a local attacker with low privileges to trigger kernel memory corruption via a race condition between add_device and remove_device operations. The flaw exists in add_device_complete(), which dereferences a hci_conn_params pointer without holding hci_dev_lock, while a concurrent MGMT_OP_REMOVE_DEVICE path frees the same object under that lock. KASAN confirms exploitation as slab-use-after-free; no public exploit or active exploitation (CISA KEV) has been identified, and patches have been released across multiple stable branches.
Use-after-free memory corruption in the Linux kernel's netpoll subsystem allows a local attacker or concurrent kernel path to access freed memory during the netpoll shutdown sequence. The flaw exists because cancel_delayed_work() - called from softirq context during __netpoll_cleanup() - does not block until the TX worker finishes, permitting queue_process() to dereference a kfree'd npinfo struct via container_of(). KASAN confirms the UAF; patches are available across multiple stable kernel branches, and no public exploit or KEV listing exists at time of analysis.
Use-after-free memory corruption in the Linux kernel's NXP i.MX8 ISI (Image Sensing Interface) media driver is triggered during module removal (rmmod of imx8_isi), confirmed by KASAN slab-use-after-free reports. The root cause is an incorrect teardown order in mxc_isi_remove(): the crossbar cleanup frees media entity pads before the V4L2 cleanup has finished removing media links that reference those same pads, resulting in a dangling pointer dereference in __media_entity_remove_link(). No public exploit has been identified at time of analysis, and with EPSS at 0.21% (11th percentile), real-world weaponization appears unlikely despite the CVSS 7.8 score.
Out-of-bounds memory read in the Linux kernel's btnxpuart Bluetooth driver exposes kernel memory to a malicious or compromised NXP Bluetooth UART controller. The vulnerability exists in nxp_recv_fw_req_v3(), which handles firmware download requests during v3 controller initialization: when the controller supplies a crafted 32-bit offset or 16-bit length value that pushes past the end of the firmware image, the driver reads arbitrary kernel memory and transmits it back to the controller over UART. The parallel v1 path (nxp_recv_fw_req_v1()) already contained the equivalent bounds check; the v3 path lacked it. No active exploitation is confirmed (not in CISA KEV) and EPSS is 0.21% (11th percentile), consistent with the narrow local/hardware attack surface.
Memory leak in the Linux kernel's SMB client encrypted receive path (receive_encrypted_standard()) allows a local low-privileged user or a cooperative malicious SMB server to exhaust kernel heap memory, with potential for heap grooming-based privilege escalation. The bug was introduced with commit b24df3e30cbf and affects multiple stable kernel series from 4.19 onward. No public exploit code exists and EPSS is 0.22%, but the kernel team's classification of CWE-787 and a C:H/I:H/A:H CVSS score reflect the Linux security team's assessment that the leaked kernel buffer is exploitable beyond simple resource exhaustion.
Double-free memory corruption in the Linux kernel's Qualcomm CPU frequency hardware driver (qcom-cpufreq-hw) allows a local low-privileged attacker on Qualcomm SoC-based systems to trigger kernel heap corruption, potentially escalating privileges to root. The flaw originates in qcom_cpufreq_hw_cpu_exit(), which incorrectly calls kfree() on memory allocated via devm_kzalloc() - memory already tracked by the kernel's device resource management (devres) system. This results in a double-free when the platform device is subsequently detached and devres performs its own cleanup. No public exploit code exists and EPSS is low (0.21%), consistent with a static-analysis discovery rather than active exploitation.
Use-After-Free in the Linux kernel HID letsketch driver allows local exploitation during device unbind, potentially enabling kernel memory corruption and privilege escalation on affected systems. The letsketch_probe() function arms a per-device kernel timer (inrange_timer) with a 100 ms timeout, but no .remove callback exists to drain the timer before devm cleanup frees letsketch_data and input_dev structures on USB unplug or rmmod, producing a UAF read/write into freed kernel memory. Patches are backported across six stable kernel branches; no public exploit code exists and EPSS is 0.21% (12th percentile), reflecting the niche device requirement and race-condition complexity.
Use-after-free in the Linux kernel HID appleir driver allows a local attacker to corrupt kernel memory during device removal, potentially achieving privilege escalation. The race condition exists between the key_up_timer callback (armed by appleir_raw_event() on each keydown/key-repeat) and hid_hw_stop(), which frees the underlying input_dev before the timer is drained. A second race window, where a USB URB completion during hid_hw_stop() can re-arm the timer via mod_timer(), means a simple teardown reorder is insufficient — the fix introduces a spinlock-gated 'removing' flag combined with timer_shutdown_sync() to permanently disable further callbacks. No public exploit has been identified at time of analysis, and EPSS is 0.22% (13th percentile).
Use-after-free in the Linux kernel HID lg-g15 driver allows a local attacker to trigger kernel memory corruption by racing device input events against USB keyboard removal. The driver allocates lg_g15_data via devm and schedules work items from HID report handlers (backlight cycle key on G15, G15 v2, G510), but lacked a remove callback to cancel pending work before devres freed the allocation. On kernel versions from approximately 5.5 through the unfixed stable branches, unplugging the keyboard while a work item is pending causes the worker to dereference freed memory via container_of, potentially enabling local privilege escalation. No public exploit has been identified and EPSS is 0.22% (13th percentile), indicating no observed widespread exploitation.
Incorrect RCU lock annotations in the Linux kernel's BPF LPM trie map implementation (`kernel/bpf/lpm_trie.c`) cause lockdep false positives on debug kernels when sleepable BPF programs access `BPF_MAP_TYPE_LPM_TRIE` maps via lookup, update, or delete operations. The mismatch arises because sleepable BPF programs hold `rcu_read_lock_trace()` while the trie code asserts `rcu_read_lock_bh_held()` or `rcu_read_lock_held()`, producing repeated 'suspicious RCU usage' kernel warnings per distinct callsite. The Linux kernel developers explicitly state no actual use-after-free occurs, since Tasks Trace RCU already serializes against trie node reclaim; however, the incorrect annotation undermines lockdep's ability to detect future regressions and is increasingly impactful as sleepable BPF LSM programs become common in production security tooling. No public exploit exists and no CISA KEV listing has been issued.
Use-after-free and memory leak in the Linux kernel's EHCI and FOTG210 USB isochronous submit paths expose systems running kernel versions from 2.6.15 through 7.1.3 to local kernel memory corruption by a low-privileged user. When an isochronous URB submission fails before the staged schedule handoff - either because the host controller becomes inaccessible or usb_hcd_link_urb_to_ep() returns an error - the ehci_iso_sched allocation is not freed and urb->hcpriv retains a dangling pointer, creating a UAF condition. No public exploit exists and the EPSS score is 0.21% (12th percentile), but vendor-released patches across multiple stable branches are available and should be applied to eliminate the risk.
Use-after-free in the Linux kernel USB gadget UDC subsystem exposes systems with DWC3-based USB controllers to a race condition between usb_del_gadget() and gadget_match_driver(), enabling a NULL pointer dereference that can crash the kernel or enable privilege escalation on unpatched systems. The flaw affects all major Linux stable branches from 5.15.x through 7.1.x prior to the patched releases, and is particularly relevant for embedded Linux, Android-based devices, and IoT hardware that use USB gadget/device mode. No public exploit has been identified at time of analysis, and EPSS remains at 0.21% (12th percentile), reflecting current low exploitation interest.
Use-after-free in the Linux kernel's idmouse USB fingerprint driver allows a low-privileged local attacker to corrupt kernel memory by racing a device disconnect against a file-descriptor release, potentially enabling local privilege escalation to root. The bug stems from `mutex_unlock()` accessing the freed driver-data structure after the lock is released, a documented non-atomic behavior; the fix introduces a `kref` reference counter to correctly manage object lifetime. Patches are available across all active stable branches; no active exploitation or public exploit has been reported.
Use-after-free in the Linux kernel's USB ldusb driver allows a local unprivileged user to corrupt kernel memory by racing disconnect() against release() on a connected USB device. The root cause is that mutex_unlock() is documented as non-atomic and may access the mutex object after it logically releases the lock, creating a window where the driver data structure can be freed while still in use. No public exploit has been identified at time of analysis, and EPSS is low (0.22%), but the C:H/I:H/A:H CVSS impact vector reflects the potential for full kernel privilege escalation if successfully triggered.
Use-after-free in the Linux kernel's USB iowarrior driver exposes systems with Code Mercantile IO-Warrior USB devices to kernel memory corruption, potentially enabling local privilege escalation to root. The defect exists because submitted write URBs are not cancelled during close(), leaving them in-flight at disconnect time; the completion handler then fires against already-freed device structures. No public exploit code has been identified at time of analysis, and EPSS at 0.22% (13th percentile) reflects minimal observed exploitation pressure, though the C:H/I:H/A:H CVSS impact reflects genuine kernel-level consequence.
Use-after-free in the Linux kernel USB iowarrior driver allows a local unprivileged user to corrupt kernel memory when a USB device disconnect races with a file release operation. The root cause is that mutex_unlock() is documented as non-atomic and may access the mutex structure after releasing the lock, meaning the driver data object can be freed while mutex_unlock() is still executing. An attacker who can trigger the race - by opening the iowarrior device and simultaneously provoking a USB disconnect - may achieve kernel memory corruption leading to privilege escalation. No public exploit code exists and EPSS is low (0.21%), but the impact class is standard kernel UAF.
The Linux kernel's legousbtower USB driver contains a use-after-free race condition between the release() and disconnect() code paths, present since Linux 2.6.25. An authenticated local user with a LEGO USB Tower device attached can trigger the race at disconnect time to corrupt freed kernel memory, potentially gaining elevated privileges or crashing the system. Patches have been issued across all active stable branches (5.10, 5.15, 6.1, 6.6, 6.12, 6.18, 7.1); no public exploit code or CISA KEV listing exists at time of analysis.