@eeacms/volto-chatbot version prior to 2.0.4 contains an unauthenticated proxy vulnerability that allows attackers to invoke arbitrary Danswer API operations with server-side credentials. The middleware route '**/_v1_da/**' accepts any HTTP method and path without authentication or path restrictions, forwarding requests with attached API keys or session cookies. This enables a Confused Deputy attack where attackers can perform privileged actions on the upstream Danswer API as the configured service account.
Crass versions prior to 1.0.7 have a vulnerability where parsing input containing non-ASCII characters leads to superlinear CPU consumption due to inefficient tracking of multi-byte character positions. This can be exploited by an attacker to cause excessive CPU usage and potential denial of service. The issue is fixed in version 1.0.7.
Crass versions prior to 1.0.7 contain a vulnerability where processing a stylesheet with a large number of adjacent CSS comments causes excessive recursion, leading to a SystemStackError. This occurs when the default behavior of discarding comments is used (i.e., :preserve_comments option is false). The issue is fixed in version 1.0.7, which eliminates recursion when discarding comments. As a workaround, enabling the :preserve_comments option prevents the recursion and the error.
Crass versions prior to 1.0.7 contain a vulnerability where deeply nested CSS blocks and functions can cause unbounded recursion, leading to a SystemStackError or excessive memory consumption. This issue arises because Crass lacks a depth guard when parsing CSS simple blocks and functions. The vulnerability is fixed in version 1.0.7 by introducing a configurable depth limit with a conservative default.
Kubeflow Pipelines versions prior to 2.17.0 contain an authorization bypass vulnerability in the frontend artifact routes. Authenticated users could access artifact contents from other tenants' namespaces without proper authorization checks, potentially exposing datasets, models, or pipeline outputs. This affects multi-user deployments relying on Kubeflow Pipelines for tenant isolation. The vulnerability does not allow disclosure of Kubernetes Secrets, modification of storage, or server-side code execution. The issue is fixed in version 2.17.0.
A vulnerability in Cedar JSON policy templates using the 'is in' scope condition allows malformed slot identifiers to cause linking errors or semantic mismatches. This can lead to policy panics or unintended authorization decisions, such as allowing access that should be forbidden. The issue affects only malformed JSON policies with incorrect slot identifiers in principal and resource constraints. Versions prior to 4.11.1 and 3.4.3 are affected. Patches are available in these fixed versions.
The @sylphx/pdf-reader-mcp package, when run as an HTTP server with MCP_TRANSPORT=http, fails to enforce API key authentication despite logging that it does. This allows unauthenticated access to the /mcp endpoint, enabling any client able to reach the server to invoke PDF processing tools and read any accessible PDF files on the host. The default binding to all interfaces (0.0.0.0) increases exposure risk. This vulnerability affects versions >=2.2.0 and <3.0.1 and is fixed in version 3.0.1.
PraisonAI versions prior to 4.6.78 contain a vulnerability in the JobWorkflowExecutor._exec_inline_python() function that allows remote code execution. The vulnerability arises because the sandbox intended to safely execute inline Python expressions is broken: the 'os' module is allowed to be imported, and dangerous functions like os.system() can be called. This enables an attacker to execute arbitrary OS commands with the privileges of the user running the workflow, particularly in multi-tenant or CI environments where untrusted YAML workflows may be executed.
Parse Server versions prior to 9.10.0-alpha.2 and 8.6.84 are vulnerable to a stored cross-site scripting (XSS) issue via malformed Content-Type headers in file uploads. The vulnerability arises because malformed Content-Type values that do not conform to the type/subtype format can bypass the file extension blocklist and be stored unchanged. When served from storage adapters that preserve the Content-Type header (e.g., Amazon S3, Google Cloud Storage, Azure Blob Storage), browsers may MIME-sniff the file content and execute embedded scripts, leading to stored XSS. The default GridFS adapter is not affected due to recomputing Content-Type and using X-Content-Type-Options: nosniff. Patches are available that validate Content-Type headers for well-formedness and reject malformed values.
Daptin versions up to 0.12.15 contain a vulnerability in their global LanguageMiddleware that parses the Accept-Language HTTP header without proper size or character filtering. The underlying Go language parser has quadratic-time complexity on malformed language tags using underscore separators, allowing an unauthenticated attacker to cause significant CPU resource exhaustion with a single crafted request. This can lead to denial of service by consuming excessive server CPU for extended periods.
PocketMine-MP versions prior to 5.44.2 have a vulnerability during the resource pack stage of client login. A malicious client can send multiple ResourcePackClientResponsePacket packets with a completed status, causing the server to repeatedly execute pre-spawn progression. This leads to the creation of multiple Player objects for a single session, increasing memory usage and outbound network traffic due to duplicated large pre-spawn packets. The issue was patched in version 5.44.2.
A vulnerability in SilverStripe CMS version 5 allows bypassing multi-factor authentication (MFA) during the password reset process. An attacker with access to a user's email can reset the password and gain a logged-in session without completing MFA. This issue is fixed in version 6.0.0 and does not affect CMS 6.
A vulnerability in Kubeflow Pipelines prior to version 2.18.0 allows unauthorized access to logs via the API server's log retrieval endpoint. The API server does not authorize callers against the selected run, enabling an attacker with network access and knowledge of run and node IDs to read live or archived logs. This includes the ability to read logs from unrelated pods by manipulating node IDs. The exposed logs may contain sensitive workload data or credentials. The issue is fixed in version 2.18.0.
This article is a personal narrative by a security leader diagnosed with stage-three prostate cancer, drawing parallels between personal health risk management and cybersecurity risk leadership. It emphasizes the human aspect of risk, resilience, and leadership, highlighting the importance of psychological safety, transparency, and support within security teams. The piece advocates for a more human-centered approach to risk management, encouraging open dialogue and acknowledging vulnerabilities without stigma.
CVE-2025-12523 is a vulnerability in Centreon affecting the Users Configuration Endpoint, where broken object level authorization allows an authenticated user to disclose information they should not access. The flaw impacts Centreon versions 24.10, 24.04, and versions from 25.10.0 up to but not including 25.11.0. The vulnerability has a CVSS score of 6.5 (medium severity) and is fixed in centreon-web versions 25.10.6, 24.10.21, and 24.04.25.
CVE-2026-62374 affects the @sd-jwt/core JavaScript library used for Selective Disclosure JWT (SD-JWT) implementations. Versions 0.19.0 and earlier of @sd-jwt/core and @sd-jwt/decode silently drop tampered or malformed Disclosures without error, returning a reduced claim set while still reporting verification success. This behavior violates RFC 9901 requirements to reject unreferenced or invalid Disclosures. An attacker can exploit this to alter authorization decisions if key binding is not enforced, potentially bypassing claim-based restrictions. The issue is fixed in version 0.20.0 of @sd-jwt/core. No patch is identified for the standalone @sd-jwt/decode package.
Two serious vulnerabilities were found in the Rust zip crate, a widely used library for handling ZIP files. The first (RUSTSEC-2026-0367) allows privilege escalation by preserving dangerous file permission bits (setuid, setgid, sticky bit) when extracting archives, potentially enabling attackers to plant setuid-root files. The second (CVE-2026-115905) is a critical remote code execution flaw caused by inconsistent handling of file names between the central directory and local headers in ZIP archives, allowing arbitrary file overwrite and execution. Both vulnerabilities are fixed in version 9.0.5 of the zip crate. The advisory emphasizes that patching alone is insufficient and advocates architectural security using deny-by-default sandboxes to contain untrusted code and limit the impact of such vulnerabilities.
CVE-2026-118758 is a path traversal vulnerability in Kubeflow Pipelines prior to version 2.18.0. The volume artifact handler for the GET /artifacts/get?source=volume endpoint did not properly restrict file paths to the selected volume, allowing an attacker who can access this route and identify a mounted volume to read files outside that volume. The vulnerability affects deployments with disabled authentication or where the attacker is authorized for the namespace. The issue is fixed in version 2.18.0.
The provided document does not contain substantive threat intelligence or detailed information about the 'From Hijacked Pbx To Stolen Trunk Inj3ctor3s Campaign'. It appears to be a placeholder or verification page without actual content for analysis. Several CVE identifiers are mentioned but without descriptions or context. No active exploitation or specific malicious activities are detailed.
KeePassXC versions from 2.3.0 up to but not including 2.8.0 contain an out-of-bounds write vulnerability in the browser integration component. The issue arises because a fixed 1 MiB output buffer is used for encrypting authorized responses, but the encryption function writes more data than this buffer can hold under certain conditions. This flaw can be triggered by a browser-protocol client with valid database association and access to the per-user IPC endpoint when an unlocked database generates a large authorized response. The vulnerability is fixed in version 2.8.0.