Uni-CLI gives people and agents one command interface for websites, browsers, desktop applications, local tools, and MCP. Prior to version 0.225.2, Uni-CLI exposed the legacy JSON-RPC-over-HTTP MCP transport on loopback without validating browser Origin headers before routing requests. A malicious web page could send a CORS simple POST request, such as text/plain, to the local /mcp endpoint and deliver a JSON-RPC body to the dispatcher. If the user had started the local MCP HTTP transport, that page could drive tools/call requests against the user's local Uni-CLI server. The Streamable HTTP transport already enforced this browser-to-localhost boundary. The legacy stateless HTTP path did not, so the two HTTP transports had drifted. This issue is about the browser-to-localhost boundary; it does not change Uni-CLI's local-code-execution trust model. This issue has been patched in version 0.225.2.
This content describes a technology used by Kaspersky to detect and block email spam domains generated by domain generation algorithms (DGAs). Spammers use DGAs to create many similar domain names automatically, making it difficult to block spam by individual domain names. Kaspersky's solution clusters similar domains and creates rules to block entire batches of these generated domains, improving spam filtering efficiency. The technology is part of Kaspersky's corporate email security solutions and helps reduce spam, phishing, and malware emails.
Isar is an integration system for automated root filesystem generation. In versions 0.11 and newer, /etc/apt/trusted.gpg.d is created manually during bootstrap setup to be able to deploy local keys. By that, the directory is owned by the calling user (the one that executes Isar) instead of root. If the calling user's id is identical to one of an unprivileged user inside the image, this user is able to alter existing keys and deploy new ones, silently breaking the apt repo integrity protection. The issue is has no impact on those images that use an immutable rootfs, or if apt is never invoked. Changing only the keys does not trigger an exploit, it's just one step in a chain. An attacker would also have to manipulate a remote repo or intercept non-secure communication with it. This issue has been patched via commit 29e84ed.
CVE-2026-55486 is a critical cross-site scripting (XSS) vulnerability in the intranda goobi-viewer-core web application. Versions from 25.08 up to but not including 26.05 are affected. The flaw arises because the IIIF Auth 2.0 endpoints auth/login and auth/token accept an origin query parameter without proper validation. This parameter is then embedded unsafely into the Content-Security-Policy header and an HTML response body, enabling reflected XSS attacks. The vulnerability has been patched in version 26.05.
CVE-2026-55465 is a medium severity vulnerability in intranda goobi-viewer-core versions from 22.04 up to but not including 26.05. It involves an unauthenticated REST endpoint that improperly concatenates user input into a Solr query without proper escaping or validation, allowing injection of Solr local-param syntax. This can bypass access-condition filters to access restricted georeferenced records. The issue is fixed in version 26.05.
CVE-2026-55463 is a vulnerability in intranda goobi-viewer-core versions from 4.11.0 up to but not including 26.05. Several Jakarta WebSocket endpoints do not verify that the HttpSession belongs to a logged-in user and do not validate the Origin header. This allows unauthenticated attackers to connect to these endpoints and disrupt the crowdsourcing page-lock mechanism. The issue is fixed in version 26.05.
The Goobi viewer is a web application that allows digitised material to be displayed in a web browser. From version 25.01 to before version 26.05, AuthenticationEndpoint.verifyOpenIdToken builds its verifier as JWT.require(algorithm).withIssuer(issuer).build() and does not enforce the aud claim during cryptographic validation. The aud check is performed manually afterwards via a single string-equality call, which only handles single-string aud values. In a multi-RP IdP setup, a token whose single-string aud matches the viewer's client ID but was issued for a different relying party passes the check and authenticates the attacker as the token's sub. This issue has been patched in version 26.05.
CVE-2026-55457 is an improper authentication vulnerability in intranda goobi-viewer-core versions prior to 26.05. The issue arises because the application returns an empty string as a default token when no web API token is configured, and the authorization filter accepts requests with an empty token parameter. This allows unauthorized access to endpoints protected by authorization bindings. The vulnerability has been patched in version 26.05.
CVE-2026-55444 is an improper input validation vulnerability in the legacy RSS servlet of intranda goobi-viewer-core prior to version 26.05. The servlet accepts q and filterQuery parameters that are concatenated into Solr queries without proper validation, allowing an unauthenticated attacker to manipulate queries and bypass access restrictions in the generated RSS feed. This issue has been patched in version 26.05.
CVE-2026-55442 is an improper input validation vulnerability in intranda goobi-viewer-core affecting versions from 23.03 up to but not including 26.05. The flaw involves the SolrTools.cleanUpQuery() function, which attempts to sanitize user-supplied query strings by stripping Solr local-parameter syntax. However, the sanitization can be bypassed by wrapping the local parameter in double curly braces, allowing a valid Solr local parameter to be forwarded. This vulnerability has been patched in version 26.05.
Conda Organization Infrastructure is a centralized location for infrastructure codes. Prior to commit 9c0f238, a GitHub Actions Pwn Request vulnerability appears to remain present in conda/conda. The affected workflow is .github/workflows/update.yml. It is triggered by issue_comment events containing @conda-bot render or @conda-bot recreate. For the render path, the workflow obtains the pull request head repository and branch from the PR API, checks out that PR-controlled repository/ref using secrets.SYNC_TOKEN, and then runs conda/actions/template-files@7f6830b1428a9bd47f0b068892c77eae95207037. The external template-files action reads its default configuration and templates from the checked-out working directory. In the confirmed finding, that action uses an unsandboxed Jinja2 environment to render attacker-controlled template content. This creates a Pwn Request chain in which an untrusted PR/comment path can reach template rendering in a privileged token context. This issue has been patched via commit 9c0f238.
A path traversal vulnerability (CWE-22) exists in intranda goobi-viewer-core versions 24.03 up to but not including 26.05. The vulnerability occurs because the application improperly handles filenames extracted from a Content-Disposition header, allowing directory traversal sequences or absolute paths to be used. This can lead to arbitrary file writes by the Tomcat process user, potentially resulting in remote code execution. The issue is fixed in version 26.05.
CVE-2026-46651 is a critical vulnerability in intranda goobi-viewer-core versions 24.03 up to but not including 26.05. The DownloadTaskEndpoint WebSocket endpoint (/tasks/download/monitor.socket) accepts download requests from unauthenticated users, allowing unauthorized access to critical functions. This issue has been patched in version 26.05.
CVE-2026-46347 affects the intranda goobi-viewer-core web application prior to version 26.05. The vulnerability involves the generation of password reset links with insufficient randomness, allowing an attacker to potentially brute-force the replacement password if they can approximate the server-side generation time. Exploitation requires the victim to have initiated the password reset and the attacker to infer server time from metadata. This issue has been fixed in version 26.05.
The Goobi viewer is a web application that allows digitised material to be displayed in a web browser. Prior to version 26.05, the password reset token is predictably based on the time of the reset request. An attacker who knows the target's email address can request a reset and then brute-force the token. Exploiting this finding alone forces an unauthorized password reset on any account. This issue has been patched in version 26.05.
obsidian-tc versions from 1.0.1 up to but not including 1.31.4 have an incomplete cleanup vulnerability where certain entity lifecycle operations can overwrite or corrupt vault notes due to inconsistent handling of note ownership and filesystem failures. This can result in unauthorized overwriting of note bodies and inconsistencies between the SQLite memory graph and notes on disk. The issue is fixed in version 1.31.4.
obsidian-tc versions from 1.13.0 up to but not including 1.31.4 contain an improper authorization vulnerability. This flaw allows a client to bypass human approval for certain destructive vault operations when using Streamable HTTP deployment with auth.jwtSecret configured and a client supporting elicitation.form. The server incorrectly trusts a previously minted requestState as proof of approval, enabling execution of dispatch-gated destructive actions without explicit human consent. The issue is fixed in version 1.31.4.
GFI Archiver before 15.14 contains a stored cross-site scripting vulnerability in the MailInsights scheduled report configuration that allows authenticated attackers to inject arbitrary web script or HTML via the report name parameter to /Archiver/MailInsights.aspx. The injected payload is stored by ReportScheduling.btnSaveReport_Click() without output encoding and is executed in the browser of the user who created the scheduled report when they subsequently view the MailInsights page.
AI agents with autonomous capabilities can be manipulated through malicious inputs such as emails, websites, and plugins to perform unauthorized actions including executing commands, stealing data, or deleting files using their legitimate permissions. Gen Digital's research demonstrated these risks without exploiting software vulnerabilities, highlighting the need for trust and control mechanisms around AI agents. To address these risks, Gen Digital developed the Agent Trust Hub, which includes skill verification, secure connectivity via an AI-native VPN, runtime safety controls that intercept dangerous actions, and tools to improve data transparency. The platform also promotes open standards for runtime safety and independent testing guidelines to build trust in AI agent security.