Externally-Generated Error Message Containing Sensitive Information vulnerability in plug_crypto in elixir-plug plug_crypto allows an unauthenticated remote attacker to expose the secret key base through application logs via a wrong-typed argument. Every public function in Plug.Crypto validates argument types in a function-head guard. A failed guard makes the Erlang VM raise FunctionClauseError with the actual argument values in the top stack frame, so the secret key base, a derived key, or the value an API key is compared against lands in that frame. The library's rescue blocks and Plug.Crypto.prune_args_from_stacktrace/1 only reach exceptions raised inside a function body, so they never see a guard failure. Plug.Cowboy and Bandit write the frame to the error log and attach it as crash_reason Logger metadata, which error trackers forward.
Two entry points take request data. Plug.Crypto.verify/4 exposes the secret key base when the token is neither a binary nor nil, which Phoenix.Token.verify/4 reaches because it forwards the token unguarded. Plug.Crypto.secure_compare/2 exposes the other operand when one side is not a binary, as happens when a missing request header yields nil. Reading the leaked value needs separate access to the logs or the error tracker, so the request alone does not disclose the secret to the attacker.
This issue affects plug: from 1.6.3 before 1.7.0; plug_crypto: from 1.0.0 before 2.2.1.
An attacker able to supply a crafted XML document to an application using QXmlStreamReader can cause disproportionate CPU consumption during parsing, making the application unresponsive (denial of service). Exploitation requires only that the application parse attacker-influenced XML; no authentication, privileges, or user interaction beyond ingesting the input are needed. There is no loss of confidentiality or integrity — no data disclosure, data modification, or code execution — and the impact is contained to the affected process.
CVE-2026-89320 is a high-severity vulnerability in Eclipse Foundation's Eclipse KeyPont - GOSE where the HmacShaCryptor.Hash function fails to hash its input and always returns the MAC of an empty message under the key. This flaw causes the authentication tag in AES-CBC-HMAC JSON Web Encryption (JWE) to be constant per key and independent of the message, effectively removing ciphertext integrity.
CVE-2026-25784 is a critical vulnerability in Hallo Welt! GmbH BlueSpice container images (versions 5.2.3 up to but not including 5.2.7). It arises from an insecure default initialization of the $mwsgTokenAuthenticatorServiceCIDR setting, which disables IP restrictions on internal service authentication if the related environment variable is unset. This allows any user with read access, including anonymous users on public wikis, to obtain an application token via the REST API and escalate privileges to sysop level.
CVE-2026-89319 is a medium severity vulnerability in Eclipse KeyPont - GOSE where the Decrypt function improperly validates a 64-bit plaintext length read from a protected header field. This can cause panics due to truncated or oversized values, leading to unbounded memory allocation or slice-bounds errors.
CVE-2026-25716 is a missing authorization vulnerability in Hallo Welt! GmbH BlueSpice affecting the BlueSpiceUserManager extension. Authenticated users without special privileges can block or unblock arbitrary user accounts, including administrators, via REST endpoints that do not verify permissions. This can lead to denial of service by locking out administrators or unauthorized removal of blocks imposed by administrators. The issue affects BlueSpice versions from 5.0.0 before 5.1.11 and from 5.2.0 before 5.2.7.
CVE-2026-89318 is a vulnerability in Eclipse KeyPont - GOSE where the Decrypt function passes an incorrectly sized initialization vector (IV) to the Go standard library's AEAD Open method without validating its length. This causes the Go library to panic, crashing the decrypting goroutine. The issue affects versions from 0 up to 1.0.0-rc4, including some release candidates. The vulnerability has a medium severity with a CVSS score of 6.9.
CVE-2026-89317 is a medium severity vulnerability in Eclipse Foundation's Eclipse KeyPont - GOSE component. The vulnerability arises because the library parses the JWS 'crit' header but does not enforce the requirement to reject tokens with unrecognized critical extensions, as mandated by RFC 7515 §4.1.11. Since GOSE implements no header extensions, any token with a non-empty 'crit' header should have been rejected but was not.
CVE-2026-89316 is a medium severity vulnerability in Eclipse KeyPont - GOSE where the function LoadPublicKey performs an unchecked type assertion on an EC key's curve. If a JSON Web Key (JWK) declares a key type "EC" but specifies a non-EC algorithm, this triggers a panic due to the unchecked assertion.
CVE-2026-89315 is a vulnerability in Eclipse KeyPont - GOSE where the JwtClaims.MarshalJSON function uses Go's reflect.StructOf to dynamically create struct fields for JWT claims. This function panics if a claim name is not a valid Go identifier or duplicates another field name, conditions which can be triggered by ordinary JWT claim names. The vulnerability affects multiple versions of the product up to 1.0.0-rc4. It has a CVSS 4.0 score of 6.9, indicating medium severity.
CVE-2026-89314 is a medium severity vulnerability in Eclipse Foundation's Eclipse KeyPont - GOSE. It involves an inefficient algorithmic complexity issue in the jwkFields.CheckConsistency function, which uses a pairwise nested loop to detect duplicate key_ops entries. This causes the validation cost to grow quadratically with the number of entries. Since this check runs on every JWK and JWKS unmarshal, a specially crafted JWKS document could cause significant CPU consumption, potentially occupying a CPU core for many seconds.
CVE-2026-89313 is a medium severity vulnerability in Eclipse KeyPont - GOSE where the function JwksTrustStore.Get incorrectly returns the last key in the JWKS document when a requested key ID (kid) is not found, instead of signaling a 'not found' error. This occurs due to the use of a named return value and a naked return statement that returns the last parsed key with a nil error. This behavior can cause callers to receive incorrect key data, potentially leading to trust or validation issues.
CVE-2026-89312 is a vulnerability in Eclipse Foundation's Eclipse KeyPont - GOSE where the AesGcmCryptor.Open function passes a caller-supplied nonce directly to cipher.AEAD.Open without validating its length. The Go standard library panics if the GCM nonce length is incorrect, causing the decrypting goroutine to crash when processing a JWE with a wrong-sized IV. This affects multiple versions of the product prior to 1.0.0-rc4.
Capcom suffered a data breach impacting approximately 11.7 million email addresses from its CAPCOM ID service. The breach also involved unauthorized changes to login passwords for 196 accounts. Additional personal information such as dates of birth, gender, country/region, and nicknames were compromised for 43 users. Capcom has reset affected passwords and notified impacted users. The company reported the incident to authorities and continues to investigate while maintaining service availability.
Quest Diagnostics reported unauthorized access to its Quanum Lab Services Manager platform, potentially compromising certain patient records. The breach was discovered recently and is under investigation, with the company working alongside federal law enforcement and cybersecurity experts. The exact number of affected patients and the scope of the data accessed remain unknown. Quest Diagnostics has experienced similar breaches in the past, affecting tens of thousands to millions of patient records. The company confirmed this breach is unrelated to recent PHP vulnerabilities affecting many websites. The incident highlights ongoing cybersecurity challenges in healthcare data protection.
CGM CLININET is vulnerable to Reflected Cross-Site Scripting (XSS) due to improper neutralization of user-supplied data. A remote unauthenticated attacker can craft a malicious URL containing JavaScript or HTML code, which is executed in the victim's browser when the URL is visited, allowing the attacker to steal session cookies and perform actions on behalf of the victim within the application.
The vulnerability was confirmed to affect versions up to 2026.MS3 but later versions may also be vulnerable.
CGM CLININET contains a local privilege escalation vulnerability (CVE-2025-30054) due to incorrect permission assignments on scripts and configuration files used by a root-privileged service processing HL7 messages. An attacker with uhcapache user privileges can modify these files to execute arbitrary code as root. Versions up to 2026.MS3 are confirmed vulnerable. A patch is available. The vulnerability has a critical CVSS 4.0 score of 9.3.
CVE-2025-30053 is a vulnerability in the CGM CLININET application where the cgm-updater process listens on an open network port without any authentication. This missing authentication for a critical function allows unauthenticated network access. The vulnerability affects versions up to 2026.MS3. The CVSS 4.0 base score is 6.9, indicating a medium severity level.
CVE-2025-30052 is an authentication bypass vulnerability in the rsyncd service of CGM CLININET. The service grants access based solely on the client's source IP address, allowing an attacker who can spoof an allowed IP to bypass authentication and edit files on the system. This affects versions up to 2026.MS3. The vulnerability has a high severity with a CVSS score of 8.8. A patch is available, and the product is a cloud service with vendor-managed remediation.
CVE-2025-30051 is a vulnerability in the CGM CLININET application where critical credentials, including the production database login and RabbitMQ broker credentials, are stored in the SysIO.pl configuration file with insecure file permissions. This misconfiguration allows any local user to read the file, potentially exposing sensitive credentials. The issue was fixed in version 2026.MS3.