CVE-2026-118590 is a medium severity vulnerability in the nipy nibabel library versions 5.4.0, 5.4.1, and 5.4.2. It involves uncontrolled memory allocation in the array_from_file function within nibabel/volumeutils.py, which can be triggered remotely. A fix has been proposed but is not yet accepted.
OpenBMB XAgent version 1.0.0 contains a directory traversal vulnerability in the main-upload_file-the-preserved-live-upload-file-witness-directly-reaches function located in ToolServer/ToolServerNode/main.py at line 46. This flaw could allow an attacker to access files outside the intended directory structure.
CVE-2026-107051 is a vulnerability in klassm AndFHEM version 2.4.1 that involves insecure permissions. This flaw allows unauthorized attackers to manipulate other users' FHEM home-automation control configurations.
CVE-2026-107045 is a vulnerability in Citrine v3.1.0 (versionCode 62) where insecure permissions in the CitrineContentProvider component allow unauthorized attackers to read another user's Nostr event database.
CVE-2026-107034 is a vulnerability in LeafPad / Leaf Note version 1.21 (versionCode 21) where insecure permissions allow unauthorized attackers to read another user's note data.
Share to Clipboard version 1.14.1 (versionCode 32) has insecure permissions that allow unauthorized attackers to overwrite another user's clipboard content.
CVE-2026-118586 is a server-side request forgery (SSRF) vulnerability in the dfm feedfinder2 project affecting versions 0.0.1 through 0.0.4. The flaw exists in the find_feeds function of feedfinder2.py, allowing remote attackers to manipulate requests and potentially cause the server to make unintended requests. The vulnerability has a medium severity rating with a CVSS score of 6.9. No patch or vendor response has been reported yet.
A weakness has been identified in D-Link DIR-505 1.10B02. The impacted element is the function main of the file /secmark1524.cgi of the component Web Management CGI. This manipulation of the argument accu/pass/code/hash/cmds causes backdoor. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks.
Tornado HTTP servers prior to version 6.6 are vulnerable to event loop blocking and excessive memory use when processing HTTP/1.1 chunked transfer encoded bodies composed of many small chunks. An attacker can send a request body with millions of 1-byte chunks, causing the server's event loop to block for extended periods (up to a minute for bodies near 100 MB), impacting all connections served by the process. This vulnerability also affects Tornado's SimpleAsyncHTTPClient when reading responses from malicious servers. The issue is fixed in Tornado 6.6, which introduces periodic yielding to the event loop and more efficient chunk handling.
Crass, a CSS tokenizer, incorrectly handles bad URL tokens when a closing parenthesis follows an escaped backslash, causing it to consume more input than browsers do. This flaw can cause CSS sanitizers that rely on Crass to mistakenly allow malicious CSS declarations, style rules, or at-rules such as @import to pass through. The vulnerability affects CSS sanitizers like Sanitize, Loofah, and rails-html-sanitizer, enabling attackers to smuggle CSS that can be used for UI redress, loading attacker-controlled resources, or CSS-based data exfiltration. The issue does not enable script execution in modern browsers. The vulnerability is fixed in Crass version 1.0.8.
Open Object provides an API and admin interface to manage objects and object types. From 2.4.3 until 2.5.1, 3.6.2, 4.0.2, and 4.1.1, a token scoped to read one ObjectType can read the full versioned record of an object of any other ObjectType via the history-detail endpoint `GET /api/v2/objects/{uuid}/{index}`. The `history_detail` action in `src/objects/api/v2/views.py` calls `self.get_queryset()` and `get_object_or_404` directly instead of `self.get_object()`, so `check_object_permissions` and the per-object check in `ObjectTypeBasedPermission.has_object_permission` are not invoked. The queryset's `filter_for_token` applies only to the list and search actions, while `ObjectTypeBasedPermission.has_permission` allows non-create actions, leaving neither check to constrain history-detail records to the token's permitted ObjectType. The normal retrieve endpoint returns 403 for the same unauthorized object, and the sibling history action enforces the grant. Any valid non-superuser API token with a read grant on at least one ObjectType can therefore disclose another ObjectType's complete versioned object `data`, which can include citizen or case records and sensitive identifiers in government deployments. This issue is fixed in versions 2.5.1, 3.6.2, 4.0.2, and 4.1.1.
MailWatch for MailScanner is a web-based front-end to MailScanner. Prior to 1.2.27, any authenticated MailWatch user, including the U/user, D/domain-admin, and H/host roles, can release to inbox or permanently delete the quarantined mail of any other user or domain by supplying an arbitrary message `id` to `mailscanner/quarantine_action.php`. The action path calls `quarantine_list_items()` in `mailscanner/functions.php`, which selects from `maillog` by the supplied identifier without the per-role `global_filter` applied by listing and read views. The action requires a valid session and CSRF token, but the caller can submit a token from the caller's own session; ownership of the requested message is never checked. Message identifiers are enumerable, allowing a low-privilege user to invoke `quarantine_release()` or `quarantine_delete()` for other users' or domains' quarantined messages, force-delivering mail held by the quarantine or permanently deleting it. This issue is fixed in version 1.2.27.
The DB Tools rely on the TLS implementation in Golang’s standard library, which generally uses the system CA store. However, the crypto/x509 package also has its own internal denylist of known-bad CA certificates. Golang 1.27.3 adds the eMudhra certificates to this list.
DB Tools version 100.19.0 was compiled with Golang 1.26.8, which does not include this check.
The issue is resolved by updating to Golang 1.27.3 in DB Tools 100.20.0
CVE-2026-61564 is a critical code injection vulnerability in WWBN AVideo-Encoder versions prior to 8.1.0. The unauthenticated installer endpoint 'install/checkConfiguration.php' improperly interpolates request parameters into PHP string literals without escaping, allowing attackers to inject and execute arbitrary PHP code as the web-server user. Exploitation requires the absence of the 'videos/configuration.php' file, which is typical on fresh deployments or after file removal. The vulnerability also enables arbitrary file read/write and a secondary SQL injection via unsanitized INSERT statements. This issue is fixed in version 8.1.0.
CVE-2026-57448 is a server-side request forgery (SSRF) vulnerability in the mrblomblo blombooru application prior to version 1.40.0. The vulnerability exists in the administrator-only GET /proxy-image endpoint, which fetches URLs server-side without proper validation. This allows an authenticated administrator to access internal network services and cloud instance metadata, potentially exposing sensitive credentials. The issue is fixed in version 1.40.0.
Mattermost versions 11.9.x <= 11.9.1, 11.8.x <= 11.8.5, 11.7.x <= 11.7.10 fail to validate the target post ID in the Agents plugin's mention reminder component, which allows an authenticated user who can post in a channel visible to a system administrator to cause the administrator's browser to send an unintended API request, resulting in replacement of an installed plugin and code execution on the server, via a crafted post containing a forged mention reminder that the administrator clicks. Mattermost Advisory ID: MMSA-2026-00742
AnkiMCP is an Anki addon that implements an MCP server, enabling AI assistants to interact with the Anki flashcard application. Prior to version 0.21.0, `anki_mcp_server/mcp_server.py` globally disables FastMCP DNS-rebinding protection through `TransportSecuritySettings` with `enable_dns_rebinding_protection=False`, including for the default local Streamable HTTP listener. The defaults in `anki_mcp_server/config.py` enable `http_enabled` on `127.0.0.1:3141`, with an empty `http_path` selecting the root endpoint. No bearer token, API key, session secret, strict `Host` allowlist or strict `Origin` allowlist is enforced before `initialize`, `tools/list` and `tools/call` reach MCP dispatch. A victim who visits a malicious web page while Anki and the listener are running can have browser requests rebound to loopback, allowing the attacker to `initialize` MCP, enumerate tools, read the local collection, and perform enabled non-destructive note/deck creation or updates. The attacker needs neither LAN position nor a local process. Available operations depend on enabled tool filters; destructive tools are hidden unless `enabled_destructive_tools` is opted into, limiting deletion-level impact but not the exposed read/write operations. The reported harness confirms real MCP tool dispatch with substituted Anki bridge responses rather than demonstrating destructive changes to a real collection. Disabling protection for tunnels/proxies also disables it for the normal loopback configuration. This issue is fixed in version 0.21.0.
A server-side request forgery (SSRF) vulnerability exists in n8n versions before 1.123.83, 2.41.4, and 2.42.1 in the Slack Trigger webhook. This flaw allows unauthenticated attackers to bypass signature verification when no signing secret is set, enabling them to exfiltrate Slack workspace access tokens by causing the node to send these tokens to an attacker-controlled host.
MONAI versions prior to 1.6.1 have a vulnerability in the check_hash() function where integrity verification is insufficient. Specifically, if the hash value is None, the function silently returns True, and MD5 is used as the default hash type. This flaw allows attackers who can perform man-in-the-middle or registry compromise attacks to substitute bundles, datasets, or model archives downloaded without hashes. Such substitution can lead to malicious file delivery and potential code execution.
MONAI versions from 1.2.0 up to but not including 1.6.1 contain a remote code execution vulnerability in the ConfigWorkflow.__init__ method. This vulnerability arises because the method passes a bundle's configs/logging.conf file to logging.config.fileConfig, which uses eval() on handler class and args fields. An attacker can exploit this by publishing a malicious bundle with a crafted logging.conf that executes arbitrary Python code when the victim loads or runs the bundle.