A denial of service vulnerability exists in the VRML V2.0 parser component of Open CASCADE Technology (OCCT) version V8_0_0_rc5. The flaw arises from improper handling of malformed VRML files, which can cause a corrupt or unvalidated pointer dereference during shape construction in the VrmlData_IndexedFaceSet::TShape function within libTKDEVRML.so.
An out-of-bounds read vulnerability exists in the VrmlData_IndexedLineSet::TShape component of the VRML parser in Open CASCADE Technology (OCCT) version V8_0_0_rc5. This flaw allows denial of service when processing a crafted VRML file due to improper validation of coordIndex values used as array indices.
Open CASCADE Technology (OCCT) V8_0_0_rc5 contains multiple vulnerabilities in its IGES and STEP file parsers that can be triggered by crafted IGES or STEP files. These issues include an out-of-bounds read in Geom2d_BSplineCurve::EvalD0 during IGES B-spline curve evaluation, an out-of-bounds read in MakeBSplineCurveCommon during STEP B-spline curve construction, and infinite recursion in StepShape_OrientedEdge::EdgeStart when processing a self-referential OrientedEdge entity. Successful exploitation may result in denial of service or unintended memory disclosure.
Vect ransomware emerged in January 2026 as a new threat actor operating a Ransomware-as-a-Service program with strategic partnerships that significantly expand its reach. The group has partnered with TeamPCP, known for supply chain attacks compromising security tools like Trivy, KICS, and LiteLLM, and BreachForums, distributing affiliate keys to forum members. With 25 published victims primarily targeting the United States and Technology sector, Vect maintains an open affiliate program requiring only a $250 invite code. The operation offers multi-platform ransomware payloads for Windows, Linux, and ESXi with sophisticated lateral movement capabilities and tiered commission structures reaching 89% for top affiliates. Analysis reveals connections to the defunct Devman ransomware through shared code strings and ransom note similarities, suggesting possible rebranding or code reuse.
A supply chain attack named Mini Shai-Hulud targeted four SAP NPM packages related to the SAP Cloud Application Programming (CAP) ecosystem. Malicious preinstall scripts in these packages fetched and executed a Bun binary, bypassing security monitoring. The injected malware steals local credentials and various cloud and developer tokens, exfiltrating them via public GitHub repositories. The compromised packages were available for 2-4 hours before being unpublished and replaced with clean versions. The attack is linked to the TeamPCP threat actor and exploited a compromised NPM token exposed via CircleCI. Organizations using SAP CAP, SAP Business Technology Platform workflows, or MTA-based deployment pipelines should verify if they installed the affected package versions during the exposure window.
A Brazilian anti-DDoS technology firm was found to have enabled a botnet that launched prolonged and massive distributed denial-of-service (DDoS) attacks against other Brazilian network operators. The firm's CEO attributes the malicious activity to a security breach, suggesting it was likely orchestrated by a competitor aiming to damage the company's reputation. There is no evidence of known exploits in the wild beyond this incident, and no patch or remediation information is available. The incident highlights risks related to insider threats or compromised infrastructure within security service providers.
CVE-2026-4424 is part of a set of vulnerabilities affecting Red Hat Update Infrastructure 5.2 Technology Preview container images. These Technology Preview features are not fully supported, may not be functionally complete, and are not recommended for production deployment. The advisory does not specify a direct fix for these vulnerabilities. One related vulnerability, CVE-2026-25679, involves improper validation in the Go standard library's net/url.Parse function, which can cause denial-of-service conditions but not code execution or data leakage. Red Hat classifies this issue as having high severity due to potential denial-of-service impacts on network-facing services that rely on Go runtime components.
ZionSiphon is operational technology-focused malware targeting water treatment and desalination facilities in Israel. The sample demonstrates ICS-awareness through industrial protocol interaction capabilities including Modbus, with incomplete support for DNP3 and S7comm. It incorporates geographic and environmental validation controls designed to restrict execution to Israeli water infrastructure systems. The malware attempts persistence through registry autorun entries, privilege escalation, and removable media propagation. Functionality includes network discovery of industrial devices, process manipulation targeting chlorine dosing and flow control, and configuration file modification. A critical validation flaw prevents successful execution, suggesting the analyzed sample represents incomplete development or testing. Embedded pro-Iran and anti-Israel messaging indicates politically motivated intent, though no specific threat actor attribution exists.
The ShinyHunters cybercrime group claimed to have stolen 9 million records containing personal information from Medtronic, a major medical technology company. Medtronic confirmed a hack of its systems but stated there was no identified impact on its products, patient safety, manufacturing, distribution, or financial systems. The company is investigating whether any personal information was accessed. The data breach reportedly involved corporate and personal data, with ShinyHunters threatening to leak the information unless a ransom was paid. Medtronic's diabetes-focused subsidiary MiniMed reported its systems were unaffected. The company has not publicly confirmed the data theft but appears to have removed itself from the leak site, possibly indicating ransom payment. No specific technical vulnerability details or exploits have been disclosed.
Borg SPM 2007 (Sales Ended in 2008) developed by BorG Technology Corporation has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read, modify, and delete database contents.
CVE-2026-35244 is a medium severity vulnerability in Oracle Hyperion Infrastructure Technology version 11.2.24.0.000, specifically in the Lifecycle Management component. It allows a high privileged attacker with network access via HTTP to compromise the system, requiring human interaction from a third party. Exploitation can lead to unauthorized creation, deletion, or modification of critical or accessible data, as well as unauthorized read access to some data. The CVSS 3.1 base score is 5.2, reflecting limited confidentiality impact but high integrity impact.
An insecure direct object reference vulnerability in the Users API component of Crafty Controller allows a remote, authenticated attacker to perform user modification actions via improper API permissions validation.
This release of the Red Hat build of OpenTelemetry provides security improvements.
Breaking changes:
* None
Deprecations:
* None
Technology Preview features:
* None
Enhancements:
* None
Bug fixes:
* XPath library vulnerability is fixed: Previously, the 'github.com/antchfx/xpath' library was vulnerable to a denial of service (DoS) attack. This issue occurred because specially crafted boolean XPath expressions that evaluated to true caused an infinite loop in the 'logicalQuery.Select' function, leading to 100% CPU utilization. With this update, the XPath library properly handles these expressions and prevents infinite loops. As a result, the system is no longer vulnerable to this DoS condition. For more information, see https://access.redhat.com/security/cve/cve-2026-32287.
* gRPC-Go authorization bypass vulnerability is fixed: Previously, gRPC-Go was vulnerable to an authorization bypass attack. This issue occurred because the HTTP/2 ':path' pseudo-header was not properly validated. Remote attackers could send raw HTTP/2 frames with a malformed ':path' that omitted the mandatory leading slash to bypass defined security policies. With this update, gRPC-Go properly validates the ':path' pseudo-header and rejects malformed requests. As a result, attackers can no longer bypass security policies to gain unauthorized access to services or disclose information. For more information, see https://access.redhat.com/security/cve/cve-2026-33186.
* Go JOSE denial of service vulnerability is fixed: Previously, the Go JOSE library for handling JSON Web Encryption (JWE) objects was vulnerable to a denial of service (DoS) attack. This issue occurred because the application failed when decrypting a specially crafted JWE object that specified a key wrapping algorithm but contained an empty encrypted key field. With this update, Go JOSE properly validates the encrypted key field before decryption. As a result, the application no longer crashes when processing malformed JWE objects, and the service remains available to legitimate users. For more information, see https://access.redhat.com/security/cve/cve-2026-34986.
Known issues:
* The filesystem scraper does not produce the `system.filesystem.inodes.usage` and `system.filesystem.usage` metrics in the Host Metrics Receiver after upgrading from Collector version 0.142.0 to 0.143.0 or later. No known workaround exists. For more information, see https://issues.redhat.com/browse/TRACING-5963.
This release of the Red Hat OpenShift distributed tracing platform (Tempo) provides security improvements and bug fixes.
Breaking changes:
* None.
Deprecations:
* None.
Technology Preview features:
* None.
Enhancements:
* None.
Bug fixes:
* gRPC-Go authorization bypass vulnerability fix: Previously, gRPC-Go was vulnerable to an authorization bypass attack. This issue occurred because the HTTP/2 :path pseudo-header was not properly validated. Remote attackers could send raw HTTP/2 frames with a malformed :path that omitted the mandatory leading slash to bypass defined security policies. With this update, gRPC-Go properly validates the :path pseudo-header and rejects malformed requests. As a result, attackers can no longer bypass security policies to gain unauthorized access to services or disclose information. For more information, see https://access.redhat.com/security/cve/cve-2026-33186.
* XPath component fix: Previously, the github.com/antchfx/xpath component did not properly handle certain Boolean XPath expressions. A remote attacker could submit a crafted expression that caused an infinite loop, resulting in 100% CPU utilization and a denial-of-service condition. With this update, the XPath component correctly processes Boolean expressions that evaluate to true. The system no longer enters an infinite loop when handling these expressions. For more information, see https://access.redhat.com/security/cve/cve-2026-4645.
* Go JOSE denial-of-service vulnerability fix: Previously, the Go JOSE library for handling JSON Web Encryption (JWE) objects was vulnerable to a denial-of-service (DoS) attack. This issue occurred because the application failed when decrypting a specially crafted JWE object that specified a key wrapping algorithm but contained an empty encrypted key field. With this update, Go JOSE properly validates the encrypted key field before decryption. As a result, the application no longer crashes when processing malformed JWE objects, and the service remains available to legitimate users. For more information, see https://access.redhat.com/security/cve/cve-2026-34986.
* Lodash _.template function fix: Previously, the lodash _.template function validated the variable option but did not validate options.imports key names. Both options passed values to the same code execution path. An attacker with the ability to control options.imports key names or pollute Object.prototype could exploit this gap to execute arbitrary code. With this update, lodash validates options.imports key names by using the same rules applied to the variable option. The _.template function rejects invalid key names and prevents code injection through this path. For more information, see https://access.redhat.com/security/cve/cve-2026-4800.
* Go crypto/x509 and crypto/tls packages fix: Previously, the Go standard library crypto/x509 and crypto/tls packages did not limit the number of intermediate certificates processed during certificate chain building. An attacker could provide an excessive number of intermediate certificates, causing the system to perform an uncontrolled amount of work and resulting in a denial-of-service condition. With this update, the packages limit the number of intermediate certificates accepted during certificate chain validation. The system rejects certificate chains that exceed this limit. For more information, see https://access.redhat.com/security/cve/cve-2026-32280.
* Go Root.Chmod function fix: Previously, the Root.Chmod function in the Go standard library internal/syscall/unix package had a race condition between checking and modifying a target file. An attacker could replace the target with a symbolic link after the check but before the operation completed, causing the permission change to apply to the linked file instead. This allowed an attacker to bypass directory restrictions and change permissions on unintended files. With this update, the Root.Chmod function prevents this race condition. The function no longer follows symbolic links that replace the target during execution. For more information, see https://access.redhat.com/security/cve/cve-2026-32282.
* Go crypto/x509 package fix: Previously, the Go crypto/x509 package applied excluded DNS constraints to wildcard Subject Alternative Names (SANs) in a case-sensitive manner. An attacker could bypass certificate validation by using a different case in the wildcard SAN than the excluded DNS constraint specified. This allowed the system to accept a malicious certificate that should have been rejected. With this update, the package applies DNS constraints case-insensitively when validating wildcard SANs. Certificate chain verification correctly rejects certificates that match excluded DNS constraints regardless of case. For more information, see https://access.redhat.com/security/cve/cve-2026-33810.
* Go crypto/tls component fix: Previously, the Go crypto/tls component did not re-validate certificates against updated certif
A senior member of the cybercrime group 'Scattered Spider,' Tyler Robert Buchanan, pleaded guilty to wire fraud conspiracy and aggravated identity theft. He admitted involvement in text-message phishing attacks during summer 2022 that compromised at least a dozen major technology companies. These attacks resulted in the theft of tens of millions of dollars in cryptocurrency from investors. The threat involves social engineering via phishing rather than a software vulnerability. There is no indication of a patch or technical remediation since this is a criminal activity case. The severity is assessed as low given the nature of the threat and lack of ongoing exploit details.
On April 11, 2026, researchers analyzed a CHM file (api_reference.chm) tagged as Kimsuky that initiated a three-stage attack chain. The C2 server at check[.]nid-log[.]com had directory listing enabled, allowing recovery of complete source code for all payload stages: a 6,338-byte VBScript performing system reconnaissance and establishing persistence via scheduled task, a 449-byte VBScript bridge to PowerShell, and a 6,234-byte PowerShell keylogger with clipboard monitoring and timed exfiltration. The infrastructure included 79+ domains across 5 C2 IPs spanning Korean VPS providers. The server responded with "Million OK !!!!" signature, matching previously documented Kimsuky infrastructure while showing upgraded Apache/PHP stack. The operation targeted Korean Naver users through credential phishing and tax authority impersonation, with infrastructure linked to previously documented Kimsuky campaigns via shared DAOU Technology subnets.
Mercor, an AI recruiting firm, suffered a supply chain attack involving the LiteLLM component, resulting in the theft of approximately 4TB of data as claimed by the Lapsus$ threat group. The incident highlights risks associated with third-party AI software dependencies in recruitment technology. Although no known exploits are currently active in the wild, the breach could expose sensitive candidate and corporate information, impacting confidentiality and trust. The attack underscores the importance of securing supply chains, especially for AI-driven platforms handling personal data. Organizations relying on similar AI recruiting tools should be vigilant and assess their exposure to LiteLLM or related components. Mitigation requires thorough supply chain audits, enhanced monitoring of third-party software, and rapid incident response capabilities. Countries with significant AI technology adoption and recruitment sector reliance, such as the United States, United Kingdom, Germany, Canada, Australia, and South Korea, are most at risk. Given the medium severity rating, the threat poses a moderate risk primarily to confidentiality with limited immediate availability or integrity impact. No authentication or user interaction is required for exploitation, but the attack vector is indirect via supply chain compromise.
A critical vulnerability was discovered in OpenAI Codex that could allow attackers to compromise GitHub tokens. This flaw potentially enables unauthorized access to sensitive GitHub credentials, which could lead to repository manipulation, data theft, or further lateral movement within affected environments. Although no known exploits have been observed in the wild, the severity is critical due to the sensitive nature of GitHub tokens and the potential impact on confidentiality and integrity. The vulnerability does not specify affected versions or patches, indicating a need for immediate investigation and mitigation by organizations using OpenAI Codex integrated with GitHub workflows. Defenders should prioritize reviewing token management practices and monitor for unusual access patterns. Countries with significant technology sectors and heavy use of GitHub and AI coding tools are at higher risk. Immediate mitigation steps include restricting token scopes, rotating tokens, and applying any forthcoming patches or updates from OpenAI or GitHub. This threat highlights the importance of securing AI-assisted development environments and credential management.
A supply chain poisoning attack on LiteLLM, a popular AI model gateway, was detected by NSFOCUS Technology CERT. The TeamPCP group compromised the Trivy security scanning tool used in LiteLLM's release process, allowing them to publish malicious versions 1.82.7 and 1.82.8 on PyPI. These versions contained credential-stealing programs that collected sensitive data and, if a Kubernetes cluster was detected, deployed privileged Pods and implanted persistent backdoors. The attack impacted numerous dependent packages and potentially affected millions of users. The incident highlights the growing risks in AI infrastructure and the need for robust supply chain security measures.
A vulnerability was detected in Shenzhen Ruiming Technology Streamax Crocus 1.3.44. The affected element is an unknown function of the file /DevicePrint.do?Action=ReadTask of the component Parameter Handler. The manipulation of the argument State results in sql injection. The attack can be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.