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.
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.
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.
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.
baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 contain a stored cross-site scripting (XSS) vulnerability. This occurs because global shortcode expansion processes the entire rendered page, including HTML-escaped blog comments from unauthenticated users, allowing malicious scripts to execute in the context of site visitors or administrators. The vulnerability has been patched in versions 5.3.2 and 5.4.2.
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.
The npm package 'skillward' versions 0.1.1 and 0.1.2 contain malicious code that can fully compromise any computer on which it is installed or running. This compromise may lead to unauthorized access and control by an outside entity. Immediate removal of the package is recommended, but due to the potential full system compromise, simply removing the package may not eliminate all malicious components. All secrets and keys stored on the affected computer should be rotated from a different, secure machine.
A use-after-free vulnerability (CVE-2026-109619) exists in PHP's fatal error handling, where stale request state is retained. This flaw affects PHP as packaged in Red Hat Enterprise Linux 7 Extended Lifecycle Support. Red Hat has issued a security update to address this issue. The vulnerability is rated as having an important security impact by Red Hat Product Security.
A mailbox quota-accounting vulnerability in Zimbra Collaboration Suite (ZCS) allows an authenticated user to consume another user’s mailbox quota by repeatedly sharing and revoking a document. Creation of the recipient’s shared-file record charges the document size to mailbox-wide usage. Revocation deletes the record and reverses its folder counters without reversing the mailbox-wide charge. Repeated normal share notifications therefore accumulate quota usage after the visible records are gone. On accounts with a finite quota, this can prevent incoming mail and other size-increasing operations without recipient interaction. The issue affects ZCS 10.1.16 and 10.1.20.
An SMTP command injection vulnerability in the data-source testing functionality of Zimbra Collaboration Suite (ZCS) allows an ordinary authenticated user with account options enabled to inject CR/LF into the emailAddress inserted into an SMTP envelope command by a JSON SOAP request. After a successful preliminary POP3 or IMAP login, Zimbra sends the injected commands to the selected SMTP service. If that service accepts the pipelined transaction, the attacker can submit mail with attacker-selected recipients, headers and body content without victim interaction. The vulnerable command-construction path is present in ZCS 10.1.16 and 10.1.20.
baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 contain a deserialization vulnerability in the widget-area entity. This flaw allows an administrator or an attacker with widget-write capability to store malicious serialized objects via the admin JSON API. These objects are deserialized without class restrictions, enabling remote code execution as the web-server user upon unauthenticated page access after payload storage. The vulnerability has been patched in versions 5.3.2 and 5.4.2.
baserCMS is a website development framework. In versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2, an authenticated user with only theme-file view permission can traverse outside the theme directory through the optional BcThemeFile plugin's Admin web screen. ThemeFilesController::parseArgs() constructs a path containing literal ../ segments, and the view and edit actions pass it to ThemeFilesService::get() without containment validation. Authorization checks the unresolved request path, after which ThemeFile::_getContents() reads the resolved file and exposes its contents in the form textarea. A client must preserve the dot segments rather than normalize them away. Readable files are limited to .php, .css, .js, and .ctp; this can disclose application source and config/install.php database credentials in MySQL or PostgreSQL deployments, while SQLite configurations have an empty database password. Reading config/app_local.php may expose the Security.salt fallback, which is effective only when not overridden by environment configuration. The flaw does not disclose .env, .pem, or SQLite .db files, does not itself permit file writes or code execution, and does not affect the separate API getFullpath() route. The plugin is disabled by default and unauthenticated requests are not sufficient. This issue has been patched in versions 5.3.2 and 5.4.2.
A PHP vulnerability was recently disclosed with coordinated patches released by PHP.net and many vendors. No reliable public exploit code is currently available, though some firms claim to have working exploits. Cloudflare and Amazon report many exploit attempts, but it is unclear if these are effective. Applying the official patches is the recommended defense. Workarounds and web application firewall rules may provide limited temporary protection. Embedded devices and appliances running vulnerable PHP versions are a concern due to patching difficulties and should be isolated. The situation highlights the importance of timely patching and preparedness for future similar vulnerabilities.
baserCMS versions 5.2.3 before 5.3.2 and 5.4.0 before 5.4.2 contain a path traversal vulnerability in the optional BcThemeFile plugin's Admin API. The vulnerability arises because encoded path traversal sequences are decoded after validation, allowing an authenticated administrator to write PHP files outside the intended theme directory, such as into the webroot, and execute them. Exploitation requires an administrator session, the non-default plugin enabled, and a same-origin Origin header. The issue has been patched in versions 5.3.2 and 5.4.2.