Artificial intelligence has moved from experimentation to everyday business operations with remarkable speed. Employees are using it to summarize documents, draft communications, analyze spreadsheets, write code, build automations, and create AI-powered workflows across nearly every business function. Microsoft’s 2026 Work Trend Index found that employees often adopt AI faster than their organizat

The rapid integration of artificial intelligence into daily business operations has led to a significant increase in "shadow AI," posing a growing challenge for enterprise security. Shadow AI refers to unsanctioned AI applications, workflows, and AI-enabled software features that operate outside official channels, creating substantial visibility gaps for security teams. This phenomenon often results in organizations having far more AI operating within their environments than leadership realizes.
Employees are adopting AI tools at a faster pace than organizations can adapt their governance and management practices. While approved enterprise AI platforms typically undergo structured security, privacy, legal, and governance reviews, shadow AI often bypasses these processes. This can occur innocently, such as an employee enabling an AI feature within existing software, signing up for a free AI account to meet a deadline, or using a tool recommended by a coworker. These seemingly minor decisions can quickly become ingrained in daily workflows.
Technical restrictions alone are often insufficient to curb shadow AI, as employees can utilize personal devices or accounts, or activate AI features already built into business applications through software updates. The primary concern with shadow AI is not merely unauthorized software, but rather unauthorized data movement. Many employees, in their pursuit of efficiency, upload sensitive information—such as presentations, confidential proposals, or customer data—into AI tools without understanding how that data is stored, retained, or used.
The risks extend to less obvious scenarios, such as an employee enabling an AI feature within an existing SaaS platform without considering its access to customer records, financial information, proprietary source code, intellectual property, or regulated personal data. The emergence of no-code AI agents further complicates matters, allowing business users to create workflows that connect AI models directly to critical systems like email, document repositories, CRM platforms, HR applications, and cloud storage. These automations often inherit the permissions of the creating employee, granting AI access to systems that were never part of an enterprise AI strategy.
Recent research indicates that a significant portion of enterprise generative AI usage, specifically 47%, occurs through personal accounts rather than organization-managed ones. Furthermore, over half of employees admit to inputting sensitive business information into AI tools. These activities frequently remain undetected until a security assessment, compliance review, or incident brings them to light.
Effective AI governance relies on a clear understanding of current AI usage. Organizations must gain an accurate picture of what AI tools are already running across the business before making decisions about approvals or additional oversight. While high-risk AI projects supporting legal or regulatory decisions typically receive careful review, routine business tasks—such as resume screening, report generation, workflow automation, customer support, and content creation—often receive less oversight despite potentially accessing large amounts of sensitive information.
Traditional governance models struggle to keep pace with the rapid evolution of AI. New AI models emerge frequently, software vendors continuously add generative features to existing products, and employees integrate AI into their work without formal purchase requests. This dynamic environment necessitates an ongoing understanding of AI usage, changes, and newly introduced risks, rather than relying on infrequent reviews. Training employees on data privacy, intellectual property, model behavior, and information exposure is also crucial to empower them to make informed decisions about AI use.
Shadow AI is an inherent consequence of making powerful technology widely accessible. While these capabilities enhance productivity and automation, they also complicate monitoring through conventional governance processes. As AI becomes more deeply embedded in everyday software, employees will continue to experiment with new tools and features. The critical objective for organizations is to ensure these activities do not remain invisible, making the discovery and understanding of AI usage a core security function.
A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.
A security flaw has been discovered in Tenda CP3 27.5.57.101. This vulnerability affects the function SystemAsh of the file Apis/system.c of the component Kylin. The manipulation of the argument AlarmVoiceURL results in os command injection. It is possible to launch the attack remotely.

OpenAI has announced a $1 billion commitment to provide subsidized access to its Daybreak AI cybersecurity tools for under-resourced critical infrastructure defenders. The initiative, named Daybreak for Frontline Defenders, will offer AI models, training, and technical support over the next six months, prioritizing water and wastewater utilities, electric grid operators, and local government entities. This move aims to equip organizations with limited budgets and staff against increasingly sophisticated cyber threats.

Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5. Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4. "Sansec is publishing early
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.

Attackers are exploiting two new PaperCut flaws to steal credentials and gain privileged access in education-sector attacks across the U.S. and Europe. Attackers are exploiting two recelty disclosed PaperCut flaws, CVE-2026-81578 and CVE-2026-82078, in attacks targeting schools and other education organizations in the U.S. and Europe, as reported by TheHackerNews. Arctic Wolf researchers observed