A use-after-free (UAF) vulnerability exists in the xen-netback driver of the Linux kernel when reading network statistics data. This occurs due to improper synchronization of RCU state during queue teardown after errors connecting to the frontend, potentially allowing access to freed or reused memory. The issue is fixed by calling synchronize_net() before freeing the queue data.
OHIF Viewers is a zero-footprint DICOM viewer with shared extension packages. From 3.5.0-beta.0 until 3.12.15, 3.13.7, and 3.14.0-beta.19, the dicom-pdf extension reads the attacker-controlled MIMETypeOfEncapsulatedDocument value in extensions/dicom-pdf/src/getSopClassHandlerModule.js and uses it as the Blob media type for the attacker-controlled EncapsulatedDocument bytes. When a victim opens Encapsulated PDF SOP Class 1.2.840.10008.5.1.4.1.1.104.1, extensions/dicom-pdf/src/viewports/OHIFCornerstonePdfViewport.tsx embeds the Blob URL in an object element. A Blob labeled as HTML is handled as HTML despite the application/pdf object hint, and the Blob inherits the OHIF origin, allowing embedded script to access session storage, authentication tokens, and same-origin PACS requests. The malicious DICOM object may be opened locally, uploaded to a shared PACS, or supplied by a DICOMweb source. This issue is fixed in source versions 3.12.15, 3.13.7, and 3.14.0-beta.19.
Lektor versions up to 3.3.14 and beta versions 3.4.0b1 through 3.4.0b15 have an absolute path traversal vulnerability in the admin API on Windows. This flaw allows attackers to escape the project directory by using drive-letter paths that are not properly normalized by the cleanup_path function. Exploitation can occur via malicious web pages with cross-site requests or DNS rebinding against the unauthenticated local server, enabling recursive deletion of directories or writing of attacker-controlled files.
Wazuh versions from 4.0.0 up to but not including 4.14.9 contain a SQL injection vulnerability in the WazuhDBBackend._substitute_params function. This flaw allows authenticated users with agent:read permissions on one agent to inject UNION SELECT statements via the q and search parameters. Exploitation can lead to extraction of internal keys of all agents through a blind boolean oracle technique. The vulnerability is fixed in version 4.14.9.
Wazuh dashboard plugins versions from 4.9.0 up to but not including 4.14.9 contain an authorization bypass vulnerability. This flaw allows authenticated dashboard users to override the Manager API Authorization header via the /api/request proxy endpoint by supplying nested body.headers.Authorization values. Exploitation enables attackers to impersonate other Manager API identities or send unauthenticated requests upstream. The vulnerability has a high severity with a CVSS 4.0 score of 8.8. A fix is available in version 4.14.9.
Wazuh versions from 3.9.0 up to but not including 4.14.9 have a vulnerability in the fluent-forward module where TLS hostname verification is missing. This flaw allows network attackers who can redirect connections to impersonate the Fluentd collector by presenting any certificate chaining to the configured CA file. Such attackers can intercept forwarded security telemetry and the shared key hash, enabling offline cracking attempts.
Wazuh versions from 4.3.0 up to but not including 4.14.9 have a server-side request forgery (SSRF) vulnerability in the GitHub module. This flaw arises because the module trusts unvalidated 'Link rel="next"' pagination URLs, allowing attackers who control the next-page URL to make the Wazuh manager send requests with the GitHub API token to attacker-controlled hosts. This can lead to exposure of organization repositories and settings. The vulnerability is rated high severity with a CVSS score of 8.2. A fix is available in version 4.14.9.
Wazuh versions from 3.7.0 up to but not including 4.14.9 contain a server-side request forgery (SSRF) vulnerability in the Azure wodle get_graph_events() function. This function follows the @odata.nextLink URL without validating the host or HTTPS scheme. An attacker who can influence the nextLink value may redirect requests to attacker-controlled endpoints, potentially capturing the Microsoft Graph bearer token and accessing internal services. The vulnerability has a medium severity with a CVSS score of 6.3. A fix is available in version 4.14.9.
Wazuh Manager versions from 3.0.0 up to but not including 4.14.9 have a memory leak vulnerability in the generic JSON decoder. This flaw allows remote attackers to exhaust memory of the wazuh-analysisd process by sending events with repeated static fields, such as duplicate 'id' fields. Exploitation requires enrolling an agent via passwordless enrollment. The resulting out-of-memory (OOM) condition can cause the process to be killed, disabling alerting functionality.
A stack-based buffer overflow vulnerability exists in Wazuh agent versions from 1.0.0 up to but not including 4.14.9. The flaw is in the logcollector snort-full log reader, which miscalculates remaining buffer space in the read_snortfull() function. An attacker who writes crafted multi-line content to a monitored snort-full log can overflow a 65,280-byte stack buffer, potentially crashing the agent or overwriting an SEH handler on 32-bit Windows agents running as SYSTEM.
CVE-2026-112334 is an out-of-bounds write vulnerability in wazuh-execd affecting Wazuh versions from 1.0.0 up to but not including 4.14.9. It allows privileged attackers with manager-configuration access to corrupt root process memory by pushing more than 64 commands via ossec.conf active-response blocks, causing array overflow and potential crashes across the Active Response fleet.
A regression in the enforcement of FIPS-approved hash algorithms was identified in Python's hashlib module. This issue affects only Python version 3.14.10 when used with OpenSSL operating in FIPS mode. The problem was corrected in Python 3.14.11.
A memory safety issue exists in OCaml versions before 4.14.5 involving ephemerons whose keys are closures with the Infix_tag. During garbage collection, the ephemeron's data can be freed while still referenced, leading to a use-after-free condition. This flaw was fixed in OCaml 4.14.5.
A vulnerability in the undici HTTP client for Node.js versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3 allows a shared cache to serve an authenticated response to an unauthenticated caller. This occurs when a cached response is revalidated with a conditional request that is redirected to a different origin. The redirect handler removes origin-bound credential headers but not cache validators, causing undici to incorrectly treat a 304 Not Modified response from the redirected origin as a successful revalidation. This can expose cached authenticated content to unauthorized users. The issue is fixed in versions 7.30.2 and 8.12.4 and later.
The Redirection for Contact Form 7 WordPress plugin up to version 3.2.14 contains an authorization bypass vulnerability. This flaw allows unauthenticated attackers to write arbitrary post meta values to newly created lead posts and copy server-side files with allowed MIME types into the plugin's uploads directory. Exploitation requires a published Contact Form 7 form with the Save Entry (Save Lead) action enabled.
The Posts Table with Search & Sort plugin for WordPress versions up to and including 1.4.14 contains a stored cross-site scripting (XSS) vulnerability via the 'date_format' parameter. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises from insufficient input sanitization and output escaping, allowing the payload to bypass WordPress's wp_kses_post filter by reconstructing malicious HTML tags only at render time.