Coverage: Last 24 hours

Today’s Highlights

Major exploit developments, critical SaaS and code hosting vulnerabilities, and multiple ongoing attacks highlight increasing attacker opportunities across both traditional and AI-powered environments. Several newly disclosed flaws allow full compromise of Linux, Microsoft 365, Adobe ColdFusion, and code collaboration platforms, with multiple intelligence and ransomware actors actively exploiting weaknesses. Themes include critical escalation in Linux, rapid supply chain exploitation, AI-related session exposures, workflow hijack risks, and adversarial use of phishing and mobile malware rental.

Table of Contents

1. 15-Year-Old GhostLock Flaw Enables Root and Container Escape on Most Linux Distros
2. Writer AI Flaw Could Let Agent Previews Leak Session Tokens Across Tenants
3. What Changes When Your Software Supply Chain Includes AI Writing Your Code?
4. Public GitHub Issue Could Trick GitHub Agentic Workflows Into Leaking Private Repo Data
5. RedWing MaaS Packages Android Bank Fraud as a Telegram Rental Service
6. DEBULL Tooling Abuses Microsoft Device-Code Flow to Target M365 Accounts
7. Court Filing Reveals Windows Device ID Helped FBI Trace Alleged Scattered Spider Hacker
8. CISA Adds 4 Actively Exploited Adobe, Joomla, and Langflow Flaws to KEV
9. Suspected China-Aligned Hackers Exploit Roundcube Flaws Against Universities
10. Critical Gitea Flaw Under Active Exploitation, Researchers Warn

Top Stories

15-Year-Old GhostLock Flaw Enables Root and Container Escape on Most Linux Distros

Source: The Hacker News | Risk: Critical | Impacted: Linux server fleets, Kubernetes and container platforms, Multi-tenant SaaS infrastructure, CI/CD runners

Summary: Researchers at Nebula Security have disclosed GhostLock (CVE-2026-43499), a 15-year-old Linux kernel flaw that lets any logged-in user take full root control of a machine that has not been patched. The vulnerable code has shipped by default in essentially every mainstream distribution since 2011. The flaw needs no special permission, no unusual settings, and no network.

Why it matters: Attackers can directly achieve root-level access and escape containers on the vast majority of Linux deployments, bypassing virtually all user privilege controls and sandbox boundaries.

Practitioner Perspective

Organizations with Linux servers or containerized environments face a uniquely severe threat: GhostLock (CVE-2026-43499) enables unprivileged users to become root without needing special configuration or network access. Any multi-tenant or shared-host system, such as CI/CD platforms, university clusters, or SaaS infrastructure, is at heightened risk if unpatched. This flaw invalidates assumptions about user separation and container isolation until remediated. Every Linux system or distribution in active use should be considered vulnerable unless already patched or mitigated. Immediate validation of patch levels and exploit detection in high-risk Linux workloads must be the top priority.

Recommended Actions

• Patch all Linux distributions for CVE-2026-43499 (GhostLock) using vendor-supplied kernel updates or backported fixes
• Review and restrict shell access on Linux systems, especially in multi-user environments, until patch status is confirmed

Writer AI Flaw Could Let Agent Previews Leak Session Tokens Across Tenants

Source: The Hacker News | Risk: Critical | Impacted: Writer AI enterprise customers, SaaS security teams, Content automation platform admins

Summary: Cybersecurity researchers have disclosed details of a now-patched critical session isolation vulnerability in Writer, an enterprise generative artificial intelligence (AI) platform, that could result in cross-tenant compromise. The one-click vulnerability has been codenamed WriteOut by the Sand Security Research team. “An outsider could go from having no access to taking over any Writer AI.”

Why it matters: A session isolation vulnerability in Writer AI exposed organizations to the risk of full cross-tenant compromise, possibly enabling outsiders to hijack any privileged enterprise account via a single click.

Practitioner Perspective

Tenant boundary escape in a major enterprise AI platform like Writer represents a fundamental breach of trust and risk containment. Any organization relying on SaaS AI products for sensitive content generation or workflow automation should urgently validate session handling and review third-party platform security practices. Even with patches in place, assume exposure if tenant-jumping vulnerabilities existed in recent platform versions. Monitor for anomalous administrative or system activity during the disclosed exposure period. Control over session and preview handling is a high-value risk area for all multi-tenant SaaS solutions.

Recommended Actions

• Assess Writer AI tenant activity logs for cross-tenant access patterns during the reported vulnerability window
• Verify that all Writer AI deployments are updated to patched versions addressing the WriteOut vulnerability

What Changes When Your Software Supply Chain Includes AI Writing Your Code?

Source: The Hacker News | Risk: Medium | Impacted: Development teams using AI code tools, SaaS engineering organizations, AppSec reviewers

Summary: Software supply chain security was hard enough. Then AI joined the build pipeline. For five years, “software supply chain security” meant one question: what’s in your code? Which open-source packages, which versions, which transitive dependencies three layers deep that nobody chose on purpose? SolarWinds, Log4Shell, and XZ Utils all taught the same lesson: the risk lives less in the code.

Why it matters: Increasing reliance on AI-generated code in the enterprise supply chain adds opaque dependencies and decision risks, amplifying the likelihood of hidden vulnerabilities slipping into production.

Practitioner Perspective

Enterprises embracing AI-driven code or allowing AI assist in software builds must adapt their threat models. Traditional dependency scanning and supply chain management approaches may miss what AI-generated or suggested code introduces. Risks shift from known component versions to the integrity and reviewability of what AI actually commits or injects. Software teams must invest in quality gates, code review standards, and continuous monitoring to counteract loss of transparency. Understand that with AI in the loop, supply chain attack paths are no longer only about components, they are about decisions and intent encoded by the AI.

Recommended Actions

• Implement mandatory manual and automated code review for all AI-generated code submitted to production repositories
• Log and audit which AI models or agents are used in the build and CI/CD pipeline and correlate with commit metadata

Public GitHub Issue Could Trick GitHub Agentic Workflows Into Leaking Private Repo Data

Source: The Hacker News | Risk: High | Impacted: GitHub Enterprise and org admins, DevSecOps teams, CI/CD workflow owners

Summary: A public issue can trick GitHub Agentic Workflows into leaking the contents of an organization’s private repositories, researchers at Noma Security have shown. The attacker needs only to open a normal-looking issue on a public repository, with no stolen credentials and no access to the organization. If that organization has given the agent read access across its repositories, private ones.

Why it matters: Attackers can use public GitHub issues to manipulate Agentic Workflows, causing unintended leaks of sensitive data from private repositories with broad workflow permissions.

Practitioner Perspective

Any organization using Agentic Workflows with read access across multiple private GitHub repositories is susceptible to this abuse. Attackers need only file a carefully crafted public issue to potentially trigger credentials or secret spillage. Relying on automated workflows with broad access without strict input validation or context containment is now a tangible supply chain risk. Security and DevOps teams should audit workflow permissions and context boundaries. Shifting to workflow architectures with least privilege and strict approval gating is now mandatory.

Recommended Actions

• Review all GitHub Agentic Workflows for excessive repository permissions and adjust scopes
• Audit workflow triggers to restrict responses to public issues or enforce additional verification steps

Emerging Signals

RedWing MaaS Packages Android Bank Fraud as a Telegram Rental Service

Source: The Hacker News | Risk: High | Impacted: Banking app users, Financial institutions, Corporate BYOD programs

Summary: A new Android malware operation called RedWing is being rented out on Telegram as a ready-made bank-fraud service. It lets even low-skill criminals take over a victim’s phone, steal their banking logins, and capture the one-time codes that protect their accounts. Zimperium’s zLabs, which found the operation, says it looks like a new variant of Oblivion, a $300-a-month rent-a-malware tool.

Why it matters: Even low-skilled attackers can now execute mobile banking compromises via rentable malware, increasing the attack surface for credential and MFA theft targeting end users.

Practitioner Perspective

RedWing, marketed on Telegram, transforms Android banking fraud into an easily rentable crimeware service that removes most technical barriers. Enterprises and financial institutions must anticipate broader, more frequent credential theft and account takeover attempts originating from mobile devices. Enhanced controls to detect anomalous device activity and unauthorized banking sessions are necessary. If your user base or workforce includes mobile banking users, assume ongoing risk escalation. Focus on endpoint visibility and user awareness to counter rapidly commoditizing threats.

Recommended Actions

• Monitor for signs of RedWing or Oblivion malware in Android EDR and MDM systems
• Increase transaction and login anomaly detection on banking portals and apps

DEBULL Tooling Abuses Microsoft Device-Code Flow to Target M365 Accounts

Source: The Hacker News | Risk: High | Impacted: Microsoft 365 tenants, Remote and hybrid workforces, Organizations federating identities via Azure AD

Summary: A Microsoft 365 device code phishing campaign has been observed leveraging collaboration-themed lures to take control of victim accounts between the last week of June 2026 and into early July, per findings from ZeroBEC. “The campaign did not depend on a fake Microsoft password page. It used a malicious collaboration-style lure to push users into the legitimate Microsoft device login.”

Why it matters: Attackers are abusing legitimate Microsoft device login flows to bypass password phishing controls and compromise Microsoft 365 accounts, making traditional phishing defenses less reliable.

Practitioner Perspective

Campaigns like DEBULL exploit user trust in official Microsoft prompts rather than relying on password harvesting. Any enterprise operating M365 must treat device code and OAuth login flows as high-risk vectors, not just phishing-resistant alternatives. Incident responders should re-examine assumptions about MFA effectiveness in these scenarios. Security teams should actively track ongoing campaigns and improve detection of unexpected device-code prompts and sign-ins. Prioritize user awareness around device-based login attempts initiated outside normal workflows.

Recommended Actions

• Enhance detection for suspicious Microsoft device login flow initiations in O365 and AzureAD sign-in logs
• Review and restrict device-code grant permissions and associated OAuth app approvals

Court Filing Reveals Windows Device ID Helped FBI Trace Alleged Scattered Spider Hacker

Source: The Hacker News | Risk: High | Impacted: Law enforcement officials, Windows users, Retailers and jewelry sector

Summary: U.S. prosecutors linked an alleged Scattered Spider hacker to a break-in at a luxury jewelry retailer using a persistent Windows device ID, according to a newly unsealed federal complaint. Microsoft records tied that ID first to the account the attackers used to keep access during the May 2025 intrusion, then to online accounts prosecutors say belong to 19-year-old Peter Stokes.

Why it matters: Persistent device identifiers in Windows systems enabled ongoing attribution and tracking, playing a key role in connecting different incidents to the same attacker, which heightens privacy and operational security considerations for defenders and law enforcement.

Practitioner Perspective

Investigators leveraged Windows device IDs to connect the dots across disparate incidents, making forensics and attribution more achievable. Organizations need robust device inventory, persistent identifier tracking, and careful privacy management to balance operational needs with law enforcement requests. Modern attacks often target or exploit endpoint identifiers, so defenders must monitor for abnormal device registrations and linkage to privilege escalation or lateral movement.

Recommended Actions

• Implement device inventory and monitoring for anomalous device identifiers in Active Directory environments
• Review endpoint registration policy and ensure sensitive device IDs are properly secured and auditable

Exploits & CVEs

CISA Adds 4 Actively Exploited Adobe, Joomla, and Langflow Flaws to KEV

Source: The Hacker News | Risk: Critical | Impacted: Adobe ColdFusion deployments, Joomla CMS environments, Langflow AI application users, Public web servers

Summary: The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Tuesday added four security flaws to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation. The vulnerabilities are listed below – CVE-2026-48282 (CVSS score: 10.0) – A path traversal vulnerability in Adobe ColdFusion that could lead to arbitrary code execution in the context of the.

Why it matters: Actively exploited flaws in Adobe ColdFusion, Joomla, and Langflow open the door to immediate code execution or compromise of internet-facing production environments, increasing the risk of lateral movement and data theft.

Practitioner Perspective

Production web and application servers running Adobe ColdFusion, Joomla, or Langflow are prime targets, given proven exploitation in the wild and inclusion in the CISA KEV. Organizations relying on these platforms should operate under the assumption of ongoing attacker attention. Public-facing infrastructure and internal applications not yet patched face a significantly increased likelihood of compromise. Inventory and exposure reviews are urgent, especially for business-critical systems. Waiting for regular patch cycles is not defensible given current threat activity.

Recommended Actions

• Immediately deploy fixes for CVE-2026-48282 on all Adobe ColdFusion servers
• Patch vulnerable Joomla and Langflow instances per latest vendor advisories cited by CISA

Suspected China-Aligned Hackers Exploit Roundcube Flaws Against Universities

Source: The Hacker News | Risk: High | Impacted: Universities using Roundcube, Physics and engineering departments, Academic mail admins

Summary: A suspected China-aligned threat activity cluster has been observed exploiting Roundcube webmail software belonging to physics and engineering departments of U.S. and Canadian universities as part of a new campaign. The activity involves the exploitation of now-patched, critical security flaws in the open-source email solution, such as CVE-2024-42009 (CVSS score: 9.3), to siphon credentials.

Why it matters: Adversaries are exploiting current Roundcube vulnerabilities to gain persistent access to academic institutions, allowing long-term credential theft and intelligence collection from strategic research environments.

Practitioner Perspective

Universities and research organizations running Roundcube should treat all recent account and mail traffic as potentially compromised. China-aligned actors’ interest demonstrates the platform’s use as a foothold for both espionage and ongoing access. Exploitation of CVE-2024-42009 and related flaws is a vector for surveillance and lateral movement, often bypassing weak patch hygiene in .edu environments. Security teams must move quickly to identify, quarantine, and resecure any affected mail infrastructure. Prioritize incident response and credential resets where feasible over patch-only approaches in previously exposed deployments.

Recommended Actions

• Patch Roundcube installations for CVE-2024-42009 and audit recent authentication and connection logs
• Search for signs of exfiltration or credential harvesting in both system and mail logs since initial flaw disclosure

Critical Gitea Flaw Under Active Exploitation, Researchers Warn

Source: SecurityWeek | Risk: Critical | Impacted: Organizations self-hosting Gitea, DevOps and CI/CD pipeline owners, Software publishers

Summary: Attackers are exploiting the critical Gitea vulnerability CVE-2026-20896 to bypass authentication with a single HTTP header and access vulnerable repositories and secrets. The post Critical Gitea Flaw Under Active Exploitation, Researchers Warn appeared first on SecurityWeek.

Why it matters: The Gitea authentication bypass (CVE-2026-20896) lets attackers access private code and secrets in vulnerable environments, enabling immediate compromise of software supply chain and intellectual property.

Practitioner Perspective

Gitea instances exposed to the internet or used for sensitive code projects are directly at risk, as active exploitation is confirmed. This is a textbook opportunistic target for attackers seeking privileged access to source code, credentials, and CI/CD secrets. Organizations using self-hosted Gitea must patch or take affected instances offline immediately. Consider all contents of previously vulnerable Gitea repositories as potentially exposed or tampered with. Review commit history and access logs as part of a full-scope compromise assessment.

Recommended Actions

• Patch all Gitea deployments for CVE-2026-20896 and verify successful update via version check
• Review repository access logs for unauthorized or anomalous authentication headers

Defensive Actions

• Deploy emergency mitigations for CVE-2026-43499 (GhostLock) across all Linux systems in production workloads and container environments
• Prioritize patching and compensating controls for Gitea (CVE-2026-20896), Adobe ColdFusion (CVE-2026-48282), and Roundcube (CVE-2024-42009)
• Audit Dialogflow CX and Writer AI tenant isolation configurations, reviewing agent and session token handling
• Assess the exposure of GitHub Agentic Workflows and revoke unnecessary broad repository permissions
• Investigate recent device-code phishing targeting M365 and review controls around OAuth/device login flows
• Monitor for signs of RedWing or Oblivion Android malware in managed environments and educate users on mobile security threats
• Search for exploitation evidence in application and authentication logs related to newly added CISA KEV vulnerabilities
• Rotate credentials and secrets that may have been exposed in unpatched Gitea or Roundcube instances
• Implement manual and automated code reviews for all AI-generated code in production repositories
• Strengthen segmentation and egress controls in environments holding sensitive public or legal data to prepare for extortion-driven breaches

What We’re Watching

• Ongoing exploitation of GhostLock (CVE-2026-43499) in both traditional Linux servers and container environments
• Continued active attacks on code hosting and collaborative development platforms, such as Gitea and GitHub, exposing software supply chains
• Rollout and vendor readiness regarding fixes for Adobe, Joomla, Langflow, and critical AI SaaS vulnerabilities
• Uptick in credential theft campaigns leveraging mobile malware and device-code based phishing
• Public sector incident response protocols and segmentation following newly reported large extortion payouts
• Improvements or disclosure gaps in multi-tenant SaaS session isolation and privilege models
• Detection and forensics efforts in academic and research organizations targeted by state-aligned espionage campaigns

Categories: Cybersecurity Blog, Cybersecurity News

Tags: cve, cybersecurity, Incident Response, Linux, Malware, SaaS Security, Supply Chain, Vulnerabilities