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.
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the volume artifact handler for GET /artifacts/get?source=volume did not confine a caller-supplied file path to the selected volume. A caller who can reach the route and identify an existing mounted volume can use path traversal to read files outside that volume when the artifact-serving process can read them. The frontend pod serves the request when artifact proxying is disabled, while the selected namespace's artifact-service pod serves it when proxying is enabled. A deployment with authentication disabled requires no application credentials; in multi-user deployments, the caller ordinarily must be authorized for the supplied namespace. This 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.
Microsoft has been named a Leader in the 2026 IDC MarketScape for Worldwide Modern Endpoint Security for Enterprises. The recognition highlights Microsoft Defender's autonomous attack disruption and predictive shielding capabilities that contain ransomware and identity attacks within minutes. The platform integrates AI-driven detection and response across endpoints, identities, email, and cloud, enabling near real-time containment of threats. The solution includes agentic AI through Security Copilot, improving alert accuracy and reducing analyst workload. Microsoft Defender's unified portal correlates signals from multiple sources into single incidents, facilitating rapid and effective response. The platform also supports securing local AI agents used by employees, providing visibility and control over their activity. This integrated approach addresses the increasing speed and complexity of ransomware and AI-driven attacks observed between 2025 and 2026.
North Korean threat actors are increasingly integrating AI technologies into their cyber operations to enhance speed, efficiency, and complexity. These actors use AI to accelerate social engineering, targeting, malware development, and operational scaling, but their activities remain human-directed rather than fully autonomous. Key groups such as Jade Sleet, Coral Sleet, and Jasper Sleet have operationalized AI across their workflows, while others are at various stages of adoption. Their operations primarily target cryptocurrency, financial organizations, IT companies, government entities, and education sectors to generate revenue, collect intelligence, and pursue political objectives. Microsoft provides mitigation guidance and Defender detections to help defend against these evolving threats.
CVE-2025-13050 is a medium severity vulnerability in Centreon that involves broken function level authorization. It allows an authenticated user with low privileges to execute poller post-restart commands, potentially impacting integrity and availability. The flaw affects Centreon versions 24.04, 24.10, and 25.10. Fixes are available in versions centreon-web-24.04.25, centreon-web-24.10.21, and centreon-web-25.10.9.
Frappe before 15.121.0 and 16.x before 16.34.0 contains a path traversal vulnerability because certain file-upload handling does not validate the destination path before writing to disk. Authenticated attackers can upload crafted files to locations outside the intended storage directory to achieve remote code execution on the server.
CVE-2026-119144 is a server-side template injection vulnerability in the Frappe Framework affecting versions before 15.111.0 and 16.x before 16.21.0. It arises because user-controlled message fields are rendered as templates without proper neutralization, allowing an authenticated attacker with common operational privileges to inject and execute arbitrary template expressions on the server.
CVE-2026-119143 is a denial of service vulnerability in bytecodealliance's wasmtime affecting versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. The flaw allows guest code to cause a host panic by performing out-of-bounds zero-length stream operations, leading to a crash in WASIp3 embedders.
Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability where dropping the Future returned by TypedFunc::call_async can panic the host. When the guest task has not started, cleanup code searches only one location for work items and unwraps the resulting error, crashing embedders that cancel pending calls.
Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability that allows malicious Wasm modules to panic the host because the may_leave flag is not cleared during realloc. Attackers can call into the host from realloc while lowering stream or future results, such as cancelling the active read or re-waiting a waitable-set, crashing the host.
CVE-2026-119140 is a denial of service vulnerability in bytecodealliance's wasmtime affecting versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. It allows malicious components to cause the host to panic by exploiting thread.yield calls in start functions, leading to a crash due to undisposed fiber drops.
CVE-2026-119139 is a reachable assertion vulnerability in bytecodealliance's wasmtime affecting versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. The flaw occurs in component::Func::call, where a leftover assertion rejects guest exports using the async ABI option. An attacker supplying a component with an async-lifted export can cause the host process to crash when that export is invoked.
Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability that allows pending calls to trigger an assertion failure after a trap poisons the Store. Attackers supplying misbehaving guest code can cause a trap and let earlier calls proceed, crashing embedders that continue using the inconsistent Store.
Wasmtime 42.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a stack overflow vulnerability that allows guests to crash the host through recursive type drops. Guests can define a long chain of recursive types so that removing the top-level type triggers unbounded recursive drops, exhausting the host stack.