The Linux Kernel 7.1 EOL has officially arrived. Discover the final updates and learn why you must upgrade to the latest stable LTS releases immediately.

Related Posts:

• CERN to Move 2,200 Accelerator Control Machines to Debian 13
• Debian 11 Reaches End of Long Term Support
• Linux Nears USB4 Support for Apple Silicon

The post Linux Kernel 7.1 Reaches End of Life appeared first on Daily CyberSecurity.

A critical MikroTik RouterOS vulnerability is actively exploited in the wild. Learn how to detect rogue ops accounts and apply the latest firmware updates.

Related Posts:

• CVE-2026-86218 (CVSS 10): N-central Pre-Auth RCE Exploited in the Wild
• MikroTrick PoC: RouterOS Admin Rights Exploited In Wild
• AI Agent Coordination: The Unprecedented OpenAI Breakout

The post MikroTik RouterOS Vulnerability Exploited in the Wild: Patch and Defense Blueprint appeared first on Daily CyberSecurity.

Plex urges an urgent security update to Media Server 1.43.3 and Desktop 1.115.0. NAS and Docker users may need to patch manually.

Related Posts:

• MikroTik RouterOS Vulnerability Exploited in the Wild: Patch and Defense Blueprint
• StyleSmuggler: Magento Zero-Day RCE Exploited in the Wild
• CVE-2026-75754 (CVSS 10): ASUS Control Center Root RCE

The post Plex Issues Urgent Security Update for Media Server and Desktop appeared first on Daily CyberSecurity.

A critical WHMCS security update fixes CVE-2026-67399 and CVE-2026-67398. Apply the patch now to prevent remote code execution and data leaks.

Related Posts:

• MikroTik RouterOS Vulnerability Exploited in the Wild: Patch and Defense Blueprint
• StyleSmuggler: Magento Zero-Day RCE Exploited in the Wild
• CVE-2026-75754 (CVSS 10): ASUS Control Center Root RCE

The post Critical WHMCS Security Update Patches RCE Flaws appeared first on Daily CyberSecurity.

Google's Chrome security update patches 15 flaws, including two critical buffer overflows in WebGL and Dawn. Update to 151.0.7922.169 now.

Related Posts:

• CVE-2026-13737: Commvault Command Execution Flaws Expose Networks
• CVE-2026-18051 (CVSS 10): Unauthenticated Arbitrary File Write Hits 900k W3 Total Cache Sites
• CVE-2026-21580: Stored XSS Hits Atlassian Confluence

The post Chrome Update Fixes 15 Flaws, Two Critical in WebGL, Dawn appeared first on Daily CyberSecurity.

Samsung’s August 2026 Galaxy update fixes 56 Android and One UI security flaws, including critical vulnerabilities and clipboard access risks.

The post Samsung’s August Update Patches 56 Security Vulnerabilities Across Galaxy Devices appeared first on TechRepublic.

Chrome's stable channel update patches 41 flaws, including 6 critical use-after-free and memory bugs. Update to 151.0.7922.108 now.

Related Posts:

• Metabase SQL Injection Zero-Day (CVSS 10) Exploited
• Multiple ClamAV Flaws Let Remote Attackers Cause DoS
• CryptoJS Randomness Vulnerability Drains Crypto Wallets

The post Chrome Security Update Patches 41 Vulnerabilities, Including 6 Critical Flaws appeared first on Daily CyberSecurity.

Google released a Chrome update addressing 382 security bugs, including sandbox-escape risks. Users and IT teams should update quickly.

The post New Chrome Update Fixes 382 Security Bugs Across Desktop, Mobile appeared first on TechRepublic.

Google has released its June 2026 Android security update, addressing 124 vulnerabilities, including one actively exploited zero-day. The zero-day — CVE-2025-48595 — is an integer overflow vulnerability in the Android Framework that allows local attackers to escalate privileges on affected devices without requiring user interaction. CVE-2025-48595 is classified as a high-severity integer overflow (CWE-190) in the Android Framework — the set of APIs and system services that applications interact with directly. An integer overflow occurs when an arithmetic operation produces a value that exceeds the maximum size of the data type used to store it, causing the value to wrap around or produce unexpected behaviour that attackers can exploit to gain elevated access.

CVE-2025-48595: The Zero-Day Under Fire

The vulnerability enables a local attacker with basic application permissions to escalate privileges and execute code at a higher permission level, potentially gaining full control of device functions. Crucially, exploitation requires no user interaction beyond running a malicious application on the device. This marks the fourth Android zero-day patched since December 2025. Google noted that CVE-2025-48595 "may be under limited, targeted exploitation" — language the company uses when targeted attacks have been confirmed, but widespread in-the-wild exploitation has not yet been observed. This pattern is frequently associated with commercial spyware vendors or nation-state threat actors targeting high-profile individuals such as journalists, activists, or government officials.

Scope of the June 2026 Update

The June 2026 Android security update is substantial, fixing 124 vulnerabilities across two patch levels. Patch level 2026-06-01 addresses core Android OS components, including the Framework and System, with 18 vulnerabilities rated critical. **Patch level 2026-06-05** includes all fixes from 2026-06-01 plus additional patches for kernel subcomponents and third-party chipset drivers from manufacturers such as Qualcomm and MediaTek. Affected Android versions include Android 14, 15, 16, and Android 16 QPR2. Pixel devices receive updates immediately through Google's update delivery system, while devices from Samsung, OnePlus, Xiaomi, and other manufacturers will receive updates on a rolling timeline that may extend weeks or months after Google's release.

CVSS and Technical Details

• CVE: CVE-2025-48595
• CWE: CWE-190 (Integer Overflow or Wraparound)
• Severity: High
• KEV Status: Not confirmed, added to CISA KEV catalogue as of June 3, 2026
• Affected Versions: Android 14, Android 15, Android 16, Android 16 QPR2

Why It Matters

The pattern of four Android zero-days in under six months reflects an active market for Android exploits among sophisticated threat actors. While Google's characterisation of "limited, targeted exploitation" suggests this is not yet a mass exploitation scenario, targeted use by spyware operators or nation-state actors presents significant risk for high-value individuals and organisations. Mobile devices increasingly serve as primary work devices, accessing corporate email, VPN, and sensitive business applications. A privilege escalation vulnerability on a corporate-enrolled Android device could allow an attacker to capture credentials, intercept MFA codes, access enterprise apps, and exfiltrate sensitive data — all from a device users typically trust implicitly. The trajectory of Android zero-days in 2026 suggests that mobile endpoints are receiving increased attention from sophisticated threat actors," said a threat intelligence analyst. "Organisations with mobile device management (MDM) programmes should treat Android OS updates with the same urgency as Windows Patch Tuesday releases."

Mitigation Steps

• Apply the June 2026 Android security update immediately on all managed Android devices via your MDM or enterprise mobility management (EMM) platform.
• For Pixel devices, install the update via Settings > System > Software update.
• Contact device manufacturers for updated timelines if using non-Pixel Android devices.
• Implement mobile application management (MAM) policies that block installation of applications from unverified sources.
• Enable Google Play Protect scanning on all managed Android devices.
• Restrict sensitive corporate applications to devices meeting a minimum patch level of 2026-06-05 through MDM policy enforcement.
• Monitor for unusual privilege escalation events in your mobile device management console.

Google's June 2026 Android update demonstrates that mobile patch management is now an essential component of enterprise security hygiene, not an optional maintenance activity.

GitLab has rolled out a major security update to address a series of vulnerabilities impacting both its Community Edition (CE) and Enterprise Edition (EE) platforms. The GitLab security update resolves multiple flaws, including high-severity issues that could be exploited to disrupt services or gain unintended access to system functionality. This update is particularly critical for organizations operating in self-managed GitLab environments, where administrators are responsible for applying patches and maintaining system security.  Delaying the deployment of this GitLab security update could leave systems exposed to known threats, including the actively addressed CVE-2026-5173 vulnerability. The patch release not only strengthens access controls but also mitigates risks tied to denial-of-service attacks, data exposure, and improper authorization checks. As a result, GitLab is strongly urging all affected users to upgrade to the latest versions immediately to ensure their environments remain protected against potential exploitation. 

Critical GitLab Security Update Targets High-Severity Flaws 

GitLab security update covers a high-severity vulnerability tracked as CVE-2026-5173, which impacts websocket connections. This flaw could allow an authenticated attacker to bypass access controls and invoke unintended server-side methods. With a CVSS score of 8.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N), the issue represents a serious risk to affected environments.  The vulnerability was discovered internally by GitLab team member Simon Tomlinson. It affects GitLab CE/EE versions from 16.9.6 prior to 18.8.9, version 18.9 before 18.9.5, and version 18.10 before 18.10.3. The latest security patch resolves this issue along with several others. 

Patch Releases and Affected Versions 

The GitLab security update includes patched versions 18.10.3, 18.9.5, and 18.8.9. According to the official release statement:  “Today, we are releasing versions 18.10.3, 18.9.5, 18.8.9 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately.”  GitLab confirmed that users of GitLab.com and GitLab Dedicated services are already protected and do not need to take action. 

Twelve Vulnerabilities Addressed 

This GitLab security update resolves a total of twelve vulnerabilities, ranging from high to low severity. Alongside CVE-2026-5173, several denial-of-service (DoS) vulnerabilities were identified: 

• CVE-2026-1092: A DoS issue in the Terraform state lock API caused by improper JSON validation (CVSS 7.5).  
• CVE-2025-12664: A DoS vulnerability in the GraphQL API that could be triggered through repeated queries (CVSS 7.5).  
• CVE-2026-1403: A CSV import flaw allowing authenticated users to disrupt Sidekiq workers (CVSS 6.5).  
• CVE-2026-1101: A GraphQL SBOM API issue affecting GitLab EE, also enabling DoS attacks (CVSS 6.5).  

In addition to these, multiple medium-severity flaws were patched: 

• CVE-2026-1516: A code injection issue in Code Quality reports that could expose user IP addresses (CVSS 5.7).  
• CVE-2026-4332: A cross-site scripting vulnerability in analytics dashboards (CVSS 5.4).  
• CVE-2026-2619: Incorrect authorization in the vulnerability flags AI detection API (CVSS 4.3).  
• CVE-2025-9484: Information disclosure via GraphQL queries (CVSS 4.3).  
• CVE-2026-1752: Improper access control in the Environments API (CVSS 4.3).  
• CVE-2026-2104: Information disclosure through CSV export (CVSS 4.3).  

A low-severity issue, CVE-2026-4916, was also addressed, involving missing authorization checks in custom role permissions (CVSS 2.7). Many of these vulnerabilities were reported through GitLab’s HackerOne bug bounty program, highlighting contributions from researchers such as a92847865, foxribeye, sim4n6, maksyche, go7f0, and others. 

Bug Fixes and Stability Improvements 

Beyond security fixes, the update also includes a wide range of bug fixes across all three versions. These improvements address issues such as failed Git operations for deploy keys on Geo sites, performance optimizations in migration helpers, and compatibility fixes for Amazon Linux 2023.  Other fixes include resolving flaky test cases, improving dependency proxy access, and addressing regressions in project archiving and deletion workflows. These updates aim to enhance overall platform stability alongside the security patch. 

Upgrade Guidance and Deployment Notes 

GitLab emphasized that no new migrations are included in these releases, meaning multi-node deployments should not require downtime. However, by default, Omnibus packages will stop services, run migrations, and restart during upgrades unless configured otherwise via the /etc/gitlab/skip-auto-reconfigure file.  The company also noted that certain package builds, such as SLES 12.5 for versions 18.10.3 and 18.9.5, are not included in this release. Additionally, GitLab confirmed that version numbers 18.10.2, 18.9.4, and 18.8.8 were skipped, with no patches issued under those versions.