Apple has released an emergency iOS update to patch a critical zero-click vulnerability actively exploited in the wild, primarily targeting US users. The exploit bypasses iOS security to grant attackers root access via malicious iMessage media files, enabling silent data extraction and surveillance. Immediate patching and enabling Lockdown Mode are strongly recommended to mitigate this high-risk threat.
Red Hat build of Keycloak is an integrated sign-on solution,
available as a Red Hat JBoss Middleware for OpenShift containerized
image. The Red Hat build of Keycloak for OpenShift image provides
an authentication server that you can use to log in centrally, log
out, and register. You can also manage user accounts for web
applications, mobile applications, and RESTful web services.
Red Hat build of Keycloak Operator for OpenShift simplifies
deployment and management of Keycloak 26.4.13 clusters.
This erratum releases new images for Red Hat build of Keycloak
26.4.13 for use within the OpenShift Container Platform cloud
computing Platform-as-a-Service (PaaS) for on-premise or private
cloud deployments, aligning with the standalone product release.
Security fixes:
* Information disclosure via CORS header injection due to unvalidated JWT azp claim (CVE-2026-37977)
* Server-Side Request Forgery via OIDC token endpoint manipulation (CVE-2026-4874)
* eclipse-vertx/vert.x:Denial of Service via TLS handshake with wildcard server name (CVE-2026-6860)
* Improper Access Control on Keycloak Server when the account Account API feature is disabled (CVE-2026-7500)
* Policy bypass during WebAuthn credential registration via client-side JavaScript manipulation (CVE-2026-8830)
* Security flaw in org.keycloak/keycloak-services (CVE-2026-8922)
* Information disclosure through arbitrary filesystem path probing (CVE-2026-9083)
* Cross-site scripting (XSS) via case-insensitive URI validation bypass (CVE-2026-9086)
* Cross-Session Email Verification Proof Not Bound to Upstream Identity in First-Broker-Login (CVE-2026-9087)
* Information disclosure due to user profile permission bypass (CVE-2026-9088)
* Group-Admin Escalation to Realm-Admin (CVE-2026-9099)
* Privilege escalation due to oversized subject_token JWT (CVE-2026-9704)
* Attacker can re-enable and take over disabled clients via Registration Access Token (CVE-2026-9705)
* Organization Data Leak After Feature Disabled in Keycloak (CVE-2026-9791)
* Security restriction bypass allows unauthorized ROPC token acquisition (CVE-2026-9792)
* Information disclosure via SAML ECP endpoint (CVE-2026-9794)
* Privilege escalation via improper scope mapping enforcement (CVE-2026-9795)
* Unauthorized access to resources via UMA permission ticket bypass (CVE-2026-9799)
* Authorization bypass via incorrect URI comparison (CVE-2026-9800)
* Denial of Service via malformed LDAP password policy response (CVE-2026-9801)
* Unauthorized account access via replayed refresh tokens after cluster restart (CVE-2026-9802)
* Denial of Service via malformed Authorization header (CVE-2026-9803)
Traccar Client is a GPS tracking mobile app for sending location updates to private servers using the open-source Traccar platform. In versions 9.7.19 and below, a single crafted deep link can silently hijack all GPS tracking parameters and redirect telemetry to an attacker-controlled server. The app registers a custom org.traccar.client://config deep-link scheme that silently writes attacker-supplied parameters (server URL, device ID, accuracy, distance, and interval) into the app's persistent configuration with no confirmation, notification, or visual indication. A single crafted link delivered via SMS, email, a webpage, or any installed app can therefore reconfigure the app the moment the victim taps it, with no special permissions required. As a result, an attacker can covertly redirect all of the victim's GPS telemetry to their own server at maximum precision and frequency, and the change persists across restarts. This gives the attacker continuous, real-time tracking of the victim's location. This issue has been fixed in version 9.7.20.
Israeli cybersecurity company Check Point has released security updates to patch a critical flaw affecting Remote Access VPN and Mobile Access deployments, which was exploited in zero-day attacks. [...]
Red Hat build of Keycloak is an integrated sign-on solution, available as a Red Hat JBoss Middleware for OpenShift containerized image. The Red Hat build of Keycloak for OpenShift image provides an authentication server that you can use to log in centrally, log out, and register. You can also manage user accounts for web applications, mobile applications, and RESTful web services.
Red Hat build of Keycloak Operator for OpenShift simplifies deployment and management of Keycloak 26.4.12 clusters.
This erratum releases new images for Red Hat build of Keycloak 26.4.12 for use within the OpenShift Container Platform cloud computing Platform-as-a-Service (PaaS) for on-premise or private cloud deployments, aligning with the standalone product release.
Security fixes:
* Denial of Service via specially crafted SAML input (CVE-2026-7307)
* Information Disclosure via evaluate-scopes Admin API (CVE-2026-37978)
* Unauthorized account takeover via WebAuthn token replay (CVE-2026-37982)
* Information disclosure via OIDC token introspection endpoint audience bypass (CVE-2026-37979)
* Access token disclosure and implicit flow bypass via forged client data (CVE-2026-7571)
* Session fixation in OIDC login flow that can lead to account takeover (CVE-2026-7507)
* Open redirect when using wildcard valid redirect URIs in Keycloak (CVE-2026-7504)
* Information disclosure via broken access control in user lookup endpoint (CVE-2026-37981)
* Unauthorized resource access and data modification via Insecure Direct Object Reference (CVE-2026-4630)
We strongly recommend the following industry cybersecurity best practices.
* Locate control and safety system networks and remote devices behind firewalls and isolate them from the business network.
* Install physical controls so no unauthorized personnel can access your industrial control and safety systems, components, peripheral equipment, and networks.
* Place all controllers in locked cabinets and never leave them in the “Program” mode.
* Never connect programming software to any network other than the network intended for that device.
* Scan all methods of mobile data exchange with the isolated network such as CDs, USB drives, etc. before use in the terminals or any node connected to these networks.
* Never allow mobile devices that have connected to any other network besides the intended network to connect to the safety or control networks without proper sanitation.
* Minimize network exposure for all control system devices and systems and ensure that they are not accessible from the Internet.
* When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.
For more information refer to the Schneider Electric [Recommended Cybersecurity Best Practices](https://www.se.com/us/en/download/document/7EN52-0390/) document.
Samsung Print Service Plugin for Android is potentially vulnerable to information disclosure when using an outdated version of the application via mobile devices. HP is releasing updates to mitigate these potential vulnerabilities.
Cisco Talos uncovered an intrusion active since January 2026 where attackers deployed CloudZ remote access tool and an undocumented plugin called Pheno to steal credentials and one-time passwords. The attack exploits Microsoft Phone Link application by intercepting synchronized mobile data including SMS and OTPs without requiring phone-level infection. CloudZ evades detection through dynamic memory execution and anti-analysis checks. The infection chain begins with a fake ScreenConnect update executable, leading to a Rust-compiled dropper that deploys a .NET loader, ultimately establishing the modular CloudZ RAT. The Pheno plugin monitors Phone Link processes and intercepts SQLite database files containing synchronized phone data. CloudZ employs ConfuserEx obfuscation, multiple configuration layers, and facilitates various commands including browser data exfiltration, shell execution, and plugin management while maintaining persistence through scheduled tasks.
A sophisticated ClickFix campaign targets both Windows and macOS users through fake CAPTCHA pages that trick victims into executing malicious commands. The macOS variant deploys an AppleScript-based infostealer that harvests sensitive data including keychain databases, credentials, and session cookies from 12 browsers, over 200 browser extensions, and 16 cryptocurrency wallets. The malware employs a persistent, non-closable dialog box mimicking legitimate system prompts to force victims into providing their system password. Stolen session cookies enable attackers to bypass multi-factor authentication by hijacking active sessions. The campaign uses client-side JavaScript to filter victims by user-agent, directing desktop users to OS-specific payloads while ignoring mobile devices. Latest macOS updates include native terminal security warnings designed to alert users against pasting potentially malicious commands.
CVE-2025-59440 is a high-severity vulnerability affecting the USIM component in various Samsung Mobile, Wearable Processors, and Modems based on Exynos chipsets. The issue arises from improper handling of SIM card proactive commands, which can lead to a Denial of Service (DoS) condition. There is no confirmed patch or official remediation available at this time. The vulnerability does not impact confidentiality or integrity but can disrupt device availability. No known exploits are reported in the wild. Users and administrators should monitor vendor advisories for updates and apply patches once available.
CVE-2026-20990 is a high-severity vulnerability affecting Samsung Mobile devices' Secure Folder feature prior to the SMR March 2026 Release 1. It involves improper export of Android application components, allowing a local attacker with limited privileges to launch arbitrary activities within the Secure Folder environment. This flaw can lead to significant confidentiality and integrity breaches by enabling unauthorized access to sensitive data and operations protected by Secure Folder. Exploitation requires local access but no user interaction or elevated privileges beyond limited local rights. No known exploits are currently reported in the wild. The vulnerability stems from CWE-926, which concerns improper export of components that should be restricted. Organizations using Samsung Mobile devices with Secure Folder should prioritize patching once updates are available and implement strict local access controls to mitigate risk. Countries with high Samsung device usage and strategic reliance on mobile security are most at risk. Given the high CVSS score (8.4) and potential impact, this vulnerability demands urgent attention from defenders.
Red Hat build of Keycloak is an integrated sign-on solution, available as a Red Hat JBoss Middleware for OpenShift containerized image. The Red Hat build of Keycloak for OpenShift image provides an authentication server that you can use to log in centrally, log out, and register. You can also manage user accounts for web applications, mobile applications, and RESTful web services.
Red Hat build of Keycloak Operator for OpenShift simplifies deployment and management of Keycloak 26.4.10 clusters.
This erratum releases new images for Red Hat build of Keycloak 26.4.10 for use within the OpenShift Container Platform cloud computing Platform-as-a-Service (PaaS) for on-premise or private cloud deployments, aligning with the standalone product release.
Security fixes:
* Keycloak SAML broker: Authentication bypass due to disabled SAML client completing IdP-initiated login (CVE-2026-3047)
* Improper Enforcement of Disabled Identity Provider in IdentityBrokerService (Authentication Bypass) (CVE-2026-3009)
* Unauthorized authentication via disabled SAML Identity Provider (CVE-2026-2603)
* Unauthorized access via improper validation of encrypted SAML assertions (CVE-2026-2092)
* Missing Check on Disabled Client for Docker Registry Protocol (CVE-2026-2733)
* Denial of Service due to excessive SAMLRequest decompression (CVE-2026-2575)
* Keycloak SAML brokering: Response delay due to unchecked NotOnOrAfter in SubjectConfirmationData (CVE-2026-1190)
* Keycloak Authorization Header Parsing Leading to Potential Security Control Bypass (CVE-2026-0707)
CVE-2026-0032 is a high-severity local privilege escalation vulnerability in the Android kernel, specifically within multiple functions of mem_protect.c. The flaw is caused by a logic error leading to an out-of-bounds write, allowing an attacker with limited privileges to escalate their rights without requiring additional execution privileges or user interaction. Exploitation can compromise confidentiality, integrity, and availability of affected devices. No known exploits are currently in the wild, but the vulnerability affects the core Android kernel, making it critical for device security. Organizations relying on Android devices should prioritize patching once updates are available and implement strict access controls to mitigate risk. This vulnerability primarily impacts countries with high Android device usage and significant mobile infrastructure. Due to the kernel-level impact and ease of exploitation, the severity is rated high with a CVSS score of 7.8.
CVE-2026-0029 is a high-severity local privilege escalation vulnerability in the Android kernel's pkvm component. The flaw arises from a logic error in the __pkvm_init_vm function, causing possible memory corruption. Exploitation requires no additional execution privileges or user interaction, making it easier for a local attacker to escalate privileges. This vulnerability impacts the confidentiality, integrity, and availability of affected Android devices. Although no known exploits are currently reported in the wild, the high CVSS score (8.4) indicates significant risk. Organizations relying on Android devices should prioritize patching once updates are available. The vulnerability primarily affects devices running the Android kernel with the pkvm component, which is widely used globally. Countries with large Android user bases and strategic interest in mobile security are most at risk. Immediate mitigation involves restricting local access and monitoring for suspicious activity until patches are deployed.
CVE-2026-0025 is a high-severity information disclosure vulnerability in Google Android affecting versions 14 through 16-qpr2. It arises from a permissions bypass in the hasImage method of Notification.java, allowing local attackers to access information across user boundaries without requiring any user interaction or additional execution privileges. This flaw can lead to local privilege escalation, compromising confidentiality, integrity, and availability of affected devices. Although no known exploits are currently in the wild, the vulnerability's ease of exploitation and broad impact make it a significant risk. Organizations using affected Android versions should prioritize patching once available and implement strict access controls to mitigate potential abuse. Countries with large Android user bases and high mobile device usage, such as the United States, India, Brazil, Germany, Japan, and South Korea, are particularly at risk. Defenders must monitor for updates from Google and apply security best practices to reduce exposure.
Cisco Talos uncovered 'DKnife', a sophisticated gateway-monitoring and adversary-in-the-middle (AitM) framework comprising seven Linux-based implants. Used since 2019, DKnife performs deep-packet inspection, traffic manipulation, and malware delivery via routers and edge devices. It targets various devices, including PCs, mobile devices, and IoT, delivering ShadowPad and DarkNimbus backdoors. The framework primarily targets Chinese-speaking users, with evidence suggesting China-nexus threat actors as operators. DKnife's capabilities include DNS hijacking, Android application update hijacking, Windows binary hijacking, anti-virus traffic disruption, and user activity monitoring. A link to the WizardNet campaign was also discovered, indicating a shared development or operational lineage.
CVE-2026-20982 is a medium severity path traversal vulnerability in Samsung Mobile devices' ShortcutService component prior to the SMR February 2026 Release 1. It allows a privileged local attacker to create files with system-level privileges by exploiting improper input validation. The vulnerability requires local access with high privileges but does not require user interaction or authentication beyond that. Although no known exploits are currently reported in the wild, successful exploitation could lead to unauthorized file creation, potentially compromising system integrity. The CVSS 4.0 score is 6.8, reflecting moderate impact and exploitability. European organizations using Samsung Mobile devices, especially those with sensitive data or critical infrastructure, should prioritize patching once updates are available. Countries with high Samsung device penetration and strategic technology sectors are more likely to be affected. Mitigation involves applying the February 2026 security update promptly, restricting local privileged access, and monitoring for suspicious file creation activities.
CVE-2026-20981 is a medium severity vulnerability in Samsung Mobile devices caused by improper input validation in the FacAtFunction component prior to the SMR February 2026 Release 1. This flaw allows a privileged physical attacker to execute arbitrary commands with system-level privileges. Exploitation requires physical access and privileged status, with no user interaction needed. The vulnerability impacts confidentiality, integrity, and availability due to the potential for full system compromise. No known exploits are currently in the wild, and no patches have been linked yet. European organizations using Samsung Mobile devices could be at risk, especially in countries with high Samsung market penetration and critical infrastructure relying on these devices. Mitigation involves restricting physical access, monitoring for unusual system commands, and promptly applying Samsung's security updates once released. Countries like Germany, the UK, France, Italy, and Spain are most likely affected due to their large Samsung user bases and strategic importance. The vulnerability's medium severity reflects the balance between high impact and the requirement for physical privileged access.
CVE-2026-20980 is a high-severity vulnerability affecting Samsung Mobile devices due to improper input validation in the PACM component prior to the SMR Feb-2026 Release 1. This flaw allows a physical attacker to execute arbitrary commands on the device without requiring authentication or user interaction. The vulnerability has a CVSS 4.0 score of 7.0, reflecting its significant impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the ease of exploitation and the critical nature of mobile devices make this a serious threat. European organizations using Samsung Mobile devices, especially those with sensitive data or critical communications, could face risks of device compromise and data breaches. Mitigation requires timely application of Samsung’s security updates once available, physical device security controls, and monitoring for unusual device behavior. Countries with high Samsung mobile market penetration and strategic importance in technology sectors, such as Germany, the UK, France, and Italy, are most likely to be affected. Defenders should prioritize patch management and physical security to reduce exposure to this vulnerability.