CYBER_THREATCAST
$ briefing --date=

CYBER THREATCAST

CYBER THREAT INTELLIGENCE BRIEFING

Wednesday, May 20, 2026|AFTERNOON EDITION|13:42 TR (10:42 UTC)|363 Signals|15 Sectors
ROUNDTABLE ACTIVE12 agents · 19 messages · 37mView →PODCASTExploitation Overtakes Credentials: The DBIR Inflection Point · 34mListen →
YellowKey (CVE-2026-45585), a critical Windows BitLocker zero-day, completely bypasses drive encryption with physical USB access, breaking a core Windows security promise and prompting Microsoft to issue emergency mitigations.
Vulnerability exploitation has surpassed stolen credentials as the #1 breach entry point (31% of breaches in 2025), with AI accelerating exploit timelines from months to hours, forcing organizations to rethink patch prioritization fundamentally.
TeamPCP orchestrated a coordinated supply-chain assault over 7 days: leaked Shai-Hulud malware source (May 13), compromised 631 npm packages (May 18-19), breached GitHub employee via poisoned VS Code extension (May 19), and is now selling ~4,000 internal GitHub repos.
CISA credential leak exposed plaintext AWS GovCloud admin keys, SSH keys, and internal credentials on GitHub for ~6 months, prompting congressional demands for classified briefings and raising questions about contractor oversight at America's top cyber agency.
Mythos and GPT-5.5-Cyber AI models are discovering thousands of zero-day vulnerabilities, but state/local governments lack personnel and funding to patch them, creating a critical asymmetry where AI-powered threat discovery outpaces organizational remediation capacity.

Analysis

The disclosure of CVE-2026-45585 (YellowKey) — a Windows BitLocker bypass requiring only physical USB access, a reboot into WinRE, and a held CTRL key — represents the most immediate operational threat for enterprise security teams this week. Discovered and publicly dropped by 'Nightmare Eclipse' in protest of MSRC's handling of prior disclosures, YellowKey is part of a deliberate, multi-vulnerability leak campaign that has already produced at least four zero-days, two of which (CVE-2026-33825 and an unnamed LPE) are now patched. Microsoft has issued emergency mitigations: remove the autofstx.exe BootExecute entry, re-establish BitLocker trust for WinRE, and transition all encrypted endpoints from TPM-only to TPM+PIN mode. Organizations that have not implemented pre-boot authentication on their device fleet are exposed until a full patch is available. The persistence of Nightmare Eclipse's campaign and the ongoing publication of working PoCs demands this mitigation be treated as a patch-equivalent remediation SLA.

The YellowKey situation does not exist in isolation — it is symptomatic of a structural deterioration in enterprise patching posture confirmed by the Verizon 2026 DBIR. Vulnerability exploitation now accounts for 31% of all confirmed breaches, surpassing credential abuse (13%) as the leading initial access vector for the first time. The DBIR analyzed over 31,000 incidents and more than 22,000 confirmed breaches — nearly double last year's 12,195 — and found that median time-to-full-patch increased to 43 days in 2025, while organizations remediated only 26% of CISA KEV-listed vulnerabilities, down from 38% in 2024. AI-accelerated exploitation is compressing the window between public disclosure and weaponization from months to hours, effectively rendering 43-day patch cycles incompatible with current threat velocity. Ransomware involvement in breaches climbed to 48%, though median ransom payments fell below $140,000 with only 31% of victims paying.

The TeamPCP supply chain campaign — a 7-day escalating attack arc spanning 'Shai-Hulud' and 'Mini Shai-Hulud' waves — illustrates how a single compromised developer account can cascade into enterprise-scale exposure. In the Mini Shai-Hulud wave confirmed this week, attackers seized one developer account and published over 630 malicious package versions across 317 packages in approximately 20 minutes, including Alibaba's Antv library. The campaign's objective is credential theft at scale, specifically targeting password managers to enable lateral propagation. Most critically, TeamPCP has now confirmed a GitHub employee compromise via a poisoned VS Code extension, and the group is reportedly listing approximately 4,000 internal GitHub repositories for sale at $50,000 or more. This escalation from package poisoning to platform-level compromise represents a qualitative shift in supply chain risk that affects every organization consuming open source dependencies through GitHub.

Compounding the supply chain exposure, a CISA contractor's public GitHub repository was found to contain plaintext AWS GovCloud administrative credentials, passwords in CSV format, backup data, and commands explicitly disabling GitHub's secrets detection feature. GitGuardian researcher Guillaume Valadon described it as 'the worst leak I've witnessed in my career,' noting the credentials may have provided privileged access to multiple internal CISA cloud environments before the repository was removed. The incident has triggered a congressional response, with Sen. Maggie Hassan requesting an urgent classified briefing. Separately, ChromaDB's unpatched CVE-2026-45829 (ChromaToast) exposes roughly 73% of internet-accessible deployments — every version since 1.0.0 through the current 1.5.8 — to unauthenticated pre-auth RCE. With 13 million monthly pip downloads and no vendor patch response since HiddenLayer's February 2026 and a researcher's November 2025 disclosures, this vulnerability is a direct and unmitigated risk for any AI application stack using ChromaDB.

The collective intelligence picture this week is unambiguous: attackers are exploiting faster than defenders are patching, supply chain integrity at both the package and platform level is actively compromised, and even the nation's primary cybersecurity agency is not immune to basic credential hygiene failures. Priority actions for security leadership: (1) implement YellowKey BitLocker mitigations within 24 hours for all Windows endpoints; (2) audit npm/pip/GitHub Actions dependencies for packages in the TeamPCP-affected set, treat any update published to affected packages in the last 7 days as suspect; (3) rotate all AWS credentials associated with CISA contractor tooling and audit GovCloud access logs for anomalous activity; (4) network-isolate all ChromaDB instances to trusted clients only until a patch is released; and (5) compress patch SLAs for all CISA KEV entries to sub-10 days given demonstrated AI-accelerated exploitation timelines.

The cybersecurity threat landscape in the past 24 hours reflects an inflection point: AI-powered vulnerability discovery and exploit automation have broken the traditional defender advantage of patch-lag time. Vulnerability exploitation now dominates breach entry vectors (31%), supply chain attacks are accelerating (TeamPCP's 7-day coordinated campaign, Mini Shai-Hulud's 600+ packages, GitHub's 3,800 internal repos), and critical infrastructure (ScadaBR, BitLocker) faces unpatched pre-auth RCE. Geopolitical tensions (Middle East conflict) are driving 3x surge in regional cyber threats and physical supply chain strain. Government agencies (CISA credential leak) are demonstrating that institutional cybersecurity hygiene lags private sector by years. Regulatory responses (AI executive orders, NIST SP 800-172 R3, Anthropic policy shifts) are reactive and often counterproductive (CMMC costs driving DIB market exit). The most alarming trend is asymmetry: criminal syndicates have weaponized AI faster than defenders; state/local governments face insurmountable vulnerability backlogs; and supply chain attacks are outpacing detection and response mechanisms. Defenders are operating in a reactive posture, always 6-12 months behind threat innovation cycles.

Editorial: Recommended Actions

01
PRIORITY
Immediately audit and rotate all credentials stored in public/semi-public repositories (GitHub, GitLab, etc.). Implement automated secret scanning (GitGuardian, TruffleHog) in all CI/CD pipelines and mandate 30-day credential rotation cycles for high-privileged accounts (cloud, SSH, API tokens). CISA's credential leak demonstrates that 6-month exposure windows are unacceptable; treat any GitHub/GitLab credentials as compromised retroactively.
02
PRIORITY
Establish vulnerability remediation SLAs aligned to AI-discovery velocity: critical pre-auth RCE (CVSS 9+) within 7 days, high-severity exploitable within 30 days. Current patch cycles (60-90 days) are obsolete. Implement automated patch testing in production-like environments to reduce validation bottlenecks. Prioritize scoping fixes for YellowKey (BitLocker bypass), ScadaBR (SCADA RCE), and ChromaToast (ChromaDB RCE) based on asset inventory.
03
PRIORITY
Audit OAuth and device-code authentication flows for abuse. Disable legacy device-code flows where possible; require step-up MFA (FIDO2 hardware keys) for sensitive OAuth scopes. Implement conditional access policies rejecting sign-ins from unfamiliar geographies or devices. Phishing-as-a-service kits (Tycoon2FA) are commoditizing OAuth hijacking; assume all users are targets for social engineering.
04
PRIORITY
Deploy AI-augmented supply chain monitoring: scan npm, PyPI, Docker Hub, and private registries for behavioral anomalies (package author account compromise, malware patterns, unusual build artifacts). Implement Software Bill of Materials (SBOM) generation and comparison across releases. Require code review and signed commits for all dependencies. TeamPCP's 631-package npm wave (May 18-19) and GitHub breach (3,800 repos) demonstrate that supply chain velocity exceeds traditional review gates.
05
PRIORITY
Establish crisis response playbooks for state/local government vulnerability backlogs. AI tools (Mythos, GPT-5.5-Cyber) will discover thousands of zero-days in legacy systems; remediation capacity is permanently insufficient. Prioritize: (1) internet-facing systems first, (2) segmentation for air-gapped OT, (3) vulnerability disclosure partnerships with federal agencies (CISA, NSA). Request federal funding for critical infrastructure patching; current CMMC compliance costs are unsustainable and incentivizing market exit.
ROUNDTABLE
Expert Panel Discussion
12 AI experts analyzed this briefing across 3 turns of structured debate
12Agents19Messages37mDuration

Field Signals

Real-time intelligence from X/Twitter
$ scanning feeds_

Sector Intelligence

⚔️ Attacks & Vulnerabilities

111 signals27 critical27 highAvg: 7.9
The current vulnerability landscape is defined by an unprecedented convergence of accelerating exploitation rates, AI-assisted attack tooling, and a deepening organizational capacity crisis. Verizon's 2026 Data Breach Investigations Report delivers a landmark finding: vulnerability exploitation has surpassed compromised credentials as the primary initial access vector for the first time in the report's 19-year history, now accounting for 31% of confirmed breaches—up from 20% the prior year. This shift is directly attributable to AI-enabled vulnerability discovery and weaponization, with threat actors compressing exploitation timelines from months to hours. The remediation posture across the enterprise has simultaneously deteriorated: organizations patched only 26% of CISA Known Exploited Vulnerabilities in 2025, down from 38% the prior year, with median patch resolution time worsening to 43 days. Microsoft's own vulnerability disclosure data reinforces this structural concern, with critical vulnerabilities doubling year-over-year from 78 to 157, and cloud platform exposures spiking dramatically....read full analysis

Several high-severity disclosures and active exploitations define the immediate threat surface. The researcher 'Nightmare Eclipse' has maintained a sustained zero-day barrage against Microsoft Windows, releasing six exploits in six weeks—including YellowKey (CVE-2026-45585), a BitLocker bypass requiring only physical USB access and WinRE boot, and GreenPlasma, a local privilege escalation enabling credential harvesting and lateral movement across Windows 10, 11, and Server. The Exchange Server OWA zero-day CVE-2026-42897, actively exploited with no permanent patch, allows unauthenticated session token theft via crafted email in OWA. CISA's KEV catalog has absorbed entries from both campaigns. Independently, a Huawei enterprise router zero-day caused a nationwide telecommunications outage in Luxembourg, demonstrating that unpatched critical infrastructure vulnerabilities carry real-world kinetic consequences. Proof-of-concept code has been publicly released for both a 20-year-old PostgreSQL RCE flaw in the pgcrypto extension (CVE-2026-2005, CVSS 8.8) and the Linux kernel DirtyDecrypt privilege escalation (CVE-2026-31635), materially lowering the bar for exploitation at scale. NGINX Rift (CVE-2026-42945) drew real-world exploitation within 72 hours of disclosure, confirmed by VulnCheck honeypots.

Beyond individual CVEs, several systemic trends demand strategic attention. Frontier AI models—most notably Anthropic's Mythos—have demonstrated threat-actor-level capability to chain low-severity primitives into exploitable attack paths, prompting Cloudflare to withhold the model from public release while Anthropic revised its Project Glasswing disclosure policies under congressional pressure. The Pwn2Own Berlin 2026 competition's $1.298 million in payouts across 47 unique zero-days, including successful exploitation of LLM platforms OpenAI Codex and Anthropic Claude Code, signals that AI systems are now a first-class attack surface. Critical infrastructure faces compound exposure: ScadaBR 1.2.0 carries four CISA-disclosed CVEs including unauthenticated sensor injection (CVSS 9.1) and OS command injection enabling root access, while ChromaDB's pre-authentication RCE (CVE-2026-45829) threatens AI infrastructure deployments with approximately 73% of internet-exposed instances running vulnerable versions. The Fox Tempest malware-signing-as-a-service disruption by Microsoft—which had supplied fraudulent code-signing certificates to Rhysida, Akira, INC, and Qilin ransomware groups—illustrates how upstream enablement infrastructure amplifies the reach of individual CVEs across the criminal ecosystem.

🕵️ Threat Intelligence

81 signals11 critical20 highAvg: 7.3
The dominant theme across threat intelligence reporting this period is the continued operational maturation and expanding scope of TeamPCP (tracked as UNC6780), a financially motivated threat group that has executed a sustained, multi-vector supply chain campaign targeting developer infrastructure, open-source ecosystems, and enterprise software assets. TeamPCP's activity timeline across a seven-day window included open-sourcing the Shai-Hulud worm, launching the Mini Shai-Hulud npm campaign compromising 317+ packages, breaching Grafana Labs via the TanStack supply chain attack, compromising Microsoft's durabletask Python SDK on PyPI, compromising a GitHub employee device via a poisoned VS Code extension, and claiming exfiltration of approximately 4,000 GitHub internal repositories listed for sale at $50,000+. Attribution research from Google Threat Intelligence, Wiz, and independent analysts increasingly links TeamPCP to North Korean threat actor UNC1069, with shared C2 infrastructure (sfrclak[.]com, 142.11.206[.]73) identified across the axios attack and broader DPRK activity evolution reports. The operational convergence of supply chain intrusion, credential harvesting, and extortion within a single threat actor cluster represents a significant maturation of DPRK cyber tradecraft beyond traditional espionage mandates....read full analysis

Beyond TeamPCP, the reporting period surfaces several intersecting threat actor profiles demanding analyst attention. The Banana RAT banking trojan, attributed to SHADOW-WATER-063, targets 16 Brazilian financial institutions using polymorphic payloads, fileless PowerShell execution, and real-time Pix QR code interception—a financially sophisticated capability indicating deep understanding of Brazilian payment infrastructure. Iranian-linked actors breached automatic tank gauge systems at US gas stations, modifying fuel sensor readings on internet-exposed Veeder-Root consoles with no authentication protection, demonstrating continued interest in critical infrastructure manipulation below the threshold of kinetic disruption. The Verizon 2026 DBIR's aggregate findings—31% of breaches originating from vulnerability exploitation, mobile social engineering success rates 40% higher than email phishing, shadow AI use surging from 15% to 45% of measured organizations, and third-party breach involvement up 60%—provide the statistical scaffolding that contextualizes individual campaign reports within a deteriorating industry-wide posture. FrostyNeighbor (Ghostwriter/UNC1151) has intensified operations against Ukrainian government and military entities since March 2026, deploying evolved PicassoLoader variants with server-side victim validation prior to final payload delivery, indicating investment in operational security to evade researcher tracking.

💥 Breaches & Leaks

62 signals13 critical18 highAvg: 7.4
This reporting period is defined by a cluster of high-impact breaches that collectively expose systemic weaknesses in third-party vendor risk management, developer toolchain security, and basic credential hygiene at the most sensitive levels of organizational hierarchy. The CISA credential exposure incident—in which a contractor's public GitHub repository named 'Private-CISA' exposed 844 MB of sensitive data including AWS GovCloud administrative credentials, plaintext passwords, SSH keys, Kubernetes manifests, and CI/CD pipeline documentation for approximately six months—represents an acute reputational and operational security failure for the agency responsible for advising federal cybersecurity best practices. GitGuardian researcher Guillaume Valadon confirmed that some credentials remained valid, characterized the exposure as one of the worst credential leaks he had encountered professionally, and reported that Congressional Democrats have demanded urgent classified briefings. The incident directly implicates supply chain risk: 43 federal agencies sharing infrastructure dependencies with CISA face potential lateral exposure from the six-month window during which the repository was publicly accessible....read full analysis

The GitHub internal repository breach, attributed to TeamPCP via a poisoned VS Code extension installed on an employee device, resulted in exfiltration of approximately 3,800 internal repositories containing development notes, automation logic, infrastructure references, and CI/CD tooling. GitHub confirmed the compromise, rotated critical secrets, and stated no evidence of customer data exposure—but the breach underscores a structural blind spot in enterprise security where developer workstation compromise via trusted tooling extensions can yield broad internal access. NYC Health + Hospitals disclosed unauthorized access affecting 1.8 million individuals spanning an 11-week period, with attackers exfiltrating particularly sensitive categories of data including biometric identifiers, Social Security numbers, and medical records via a compromised third-party vendor—the second major healthcare breach this period alongside the AdvancedHEALTH ransomware claim affecting 2.3 million patient data records. ShinyHunters maintained its pace of high-volume data theft operations, with confirmed breaches at 7-Eleven (600,000+ Salesforce records), the Canvas learning management platform (275 million student records from 8,809 institutions), and Cushman & Wakefield (500,000 Salesforce records). The Grafana Labs source code exfiltration via the TanStack npm supply chain attack, Deutsche Telekom dataset exposure, and ongoing PSNI compensation proceedings totaling nearly £40 million collectively illustrate the compounding financial and operational consequences of large-scale data theft campaigns that increasingly target software supply chain assets rather than end-user data directly.

🔗 Supply Chain

59 signals13 critical19 highAvg: 8.1
The software supply chain threat landscape has reached a critical inflection point, with the TeamPCP-attributed Mini Shai-Hulud campaign representing the most technically sophisticated and operationally coordinated open-source ecosystem attack observed to date. Between May 19–20, 2026, the worm compromised over 633 malicious versions across 323 unique npm packages—including AntV visualization libraries with millions of weekly downloads, echarts-for-react, timeago.js, jest-canvas-mock, and Microsoft's durabletask Python SDK—via a combination of compromised maintainer account credentials, phantom dependency injection, embedded preinstall hooks executing obfuscated Bun code, and critically, forged Sigstore provenance attestations that caused infected packages to display legitimate 'verified' badges. This last capability represents a fundamental attack against the software supply chain's emerging trust infrastructure: if provenance attestations can be forged using stolen CI/CD credentials, the verification layer that defenders rely upon to distinguish legitimate from malicious packages becomes unreliable. NPM's response—a platform-wide token reset and encouragement to migrate to Trusted Publishing via OIDC—addresses the immediate credential exposure but does not resolve the underlying vulnerability to maintainer account compromise....read full analysis

The GitHub breach via poisoned VS Code extension demonstrates that supply chain attack vectors have expanded beyond package registries into the IDE layer itself. The Nx Console extension compromise (2.2 million installations, 11 minutes from publication to credential exfiltration) and the poisoned .vscode/tasks.json auto-executing on folder open illustrate that developer tooling is now a high-value, low-detection-surface attack vector against which most enterprise security programs have minimal visibility. The cascade potential—compromised npm packages providing credentials to access GitHub, GitHub Actions tokens enabling further package publication, stolen cloud credentials enabling lateral movement across CI/CD infrastructure—creates a self-reinforcing attack loop that, as one analyst observed, could trace directly from npm package compromise to GitHub internal repository exfiltration via organizational dependency chains. TanStack's consideration of invitation-only pull requests represents the sharpest organizational response to date, acknowledging that the open-source contribution model itself creates a structural attack surface that automated controls alone cannot close. The confirmed victims of the broader Mini Shai-Hulud campaign—OpenAI, Grafana Labs, Mistral AI, GitHub—indicate that the most security-mature organizations in the industry remain vulnerable to supply chain attacks that exploit trusted relationships in developer ecosystems.

🦠 Malware

49 signals5 critical20 highAvg: 7.3
The macOS threat ecosystem has experienced a significant qualitative shift with the emergence of the SHub Reaper variant, a dual-function infostealer-backdoor that innovates on social engineering tradecraft by layering impersonations of Apple, Google, and Microsoft across distinct stages of a single attack chain. Delivered via fake WeChat and Miro installers on typosquatted domains, Reaper exploits the applescript:// URL scheme to bypass terminal-based ClickFix defenses, harvests browser credentials, cryptocurrency wallets, Keychain contents, iCloud keys, Telegram sessions, and business documents, then establishes persistent C2 communication via a fake Google Software Update LaunchAgent beaconing every 60 seconds. The malware includes VM/VPN fingerprinting and CIS region geolocation checks to evade researcher environments, and introduces an AMOS-style file grabber module targeting Desktop and Documents directories. This represents a meaningful evolution from opportunistic credential theft toward persistent lightweight backdoor capability—transforming an infostealer infection into a durable foothold suitable for follow-on operations....read full analysis

The Fox Tempest malware-signing-as-a-service ecosystem, disrupted by Microsoft in coordination with the FBI and Europol, had provided a critical enabling layer for multiple ransomware and malware distribution campaigns since May 2025. By supplying fraudulent code-signing certificates priced at $5,000–$9,500 per certificate via Telegram, Fox Tempest allowed threat actors including Rhysida, Akira, INC Ransom, and Qilin to bypass endpoint security controls and Windows trust verification, distributing malware families including Oyster, Lumma Stealer, Vidar, and Aurora masquerading as legitimate software like AnyDesk, Teams, and Webex. The operation created over 1,000 fraudulent certificates across hundreds of Azure tenants, illustrating how upstream criminal infrastructure-as-a-service lowers the technical barrier for malware distribution at scale. The concurrent MSHTA abuse surge documented by Bitdefender—leveraging this legacy Windows scripting binary as a living-off-the-land vector for LummaStealer, Amatera, CountLoader, and PurpleFox—further demonstrates attacker preference for trusted system components to minimize detection surface. The Mini Shai-Hulud worm's self-replicating architecture, credential harvesting across 90+ developer tool configurations, and dead-man's switch wiping functionality represents the most operationally sophisticated malware design observed this period.

🛡️ Defense & Detection

48 signals3 critical9 highAvg: 6.8
The defensive landscape in this reporting period is characterized by a tension between accelerating threat sophistication and the gradual maturation of detection, response, and organizational resilience capabilities. Microsoft's disruption of the Fox Tempest malware-signing-as-a-service operation—executed through coordinated action with the FBI and Europol's EC3—represents a meaningful upstream intervention, removing a critical enablement layer that allowed ransomware groups including Rhysida, Akira, INC, and Vanilla Tempest to fraudulently digitally-sign malicious payloads and bypass endpoint controls. The operation seized infrastructure, revoked over 1,000 fraudulent certificates, and took hundreds of Azure-hosted virtual machines offline. While Microsoft acknowledged that adversaries will adapt, the disruption materially raises operational costs for criminal actors dependent on signed malware to defeat security controls. Concurrently, Wiz's general availability release of Runtime Threat Detection for Google Cloud Run extends real-time behavioral visibility into containerized serverless workloads—closing a previously significant blind spot in cloud-native defense coverage alongside existing AWS Fargate and Azure Container Apps support....read full analysis

On the strategic and organizational dimensions, the Verizon 2026 DBIR crystallizes a persistent structural problem: security teams face 50% more critical vulnerabilities to patch relative to the prior year, yet remediation rates are falling and dwell times are extending. Detection engineering discipline is increasingly differentiated—research indicates organizations treating detection as a continuous operational function achieve 40–65% ATT&CK coverage versus 5–15% for those treating it as one-time SIEM configuration. The formation of the Communications Cybersecurity Information Sharing and Analysis Centre (C2 ISAC) by eight major US telecom operators directly addresses lessons learned from the Salt Typhoon campaign, establishing a coordination layer for threat intelligence exchange across critical communications infrastructure. The World Economic Forum and Orange Cyberdefense's Cosmos platform launch provides a complementary ecosystem-level capability: a universal taxonomy and interactive knowledge graph mapping global cybercrime networks to enable international law enforcement and private sector coordination. These institutional developments reflect growing recognition that fragmented, organization-level defenses are insufficient against structurally sophisticated adversaries operating as industrialized service providers.

🤖 AI Security

42 signals1 critical7 highAvg: 6.0
The AI security threat landscape in 2026 is experiencing a qualitative inflection point driven by the demonstrated capabilities of frontier models—most notably Anthropic's Mythos—to autonomously discover, chain, and exploit software vulnerabilities at a sophistication level previously associated with elite human researchers. Cloudflare's internal testing revealed Mythos can reason across multiple low-severity primitives to construct working exploits with proof-of-concept code on 50+ internal repositories, while Anthropic's policy revision to expand Project Glasswing's disclosure permissions reflects mounting pressure to balance competitive restriction with collective defensive benefit. The Hack The Box 2026 Cybersecurity Skills Report, drawing on 702,000 practitioners across 251 countries, identifies Prompt Injection (29%), ML Model Exploitation (24%), and Agentic AI Hijacking (12%) as the top-solved challenge categories—directly reflecting market prioritization of AI-specific attack surface defense. The convergence of AI-accelerated vulnerability discovery (estimated at ~50,000 CVEs annually with only 446 confirmed exploited in 2025) with organizationally constrained patching capacity creates a structural asymmetry that threat actors are actively exploiting....read full analysis

The agentic AI deployment wave is introducing a distinct class of enterprise risk that differs fundamentally from conventional application security. SentinelOne's Prompt Security for Agentic AI framework categorizes the threat surface across construction-time risks (overpermissive IAM, hardcoded secrets, unverified plugins), runtime risks (prompt injection triggering unauthorized real-world actions), and execution risks from autonomous action chaining. Gartner projects 40% of enterprise applications will incorporate task-specific AI agents by end of 2026, while Orchid Security's Identity Gap report reveals 67% of non-human accounts are created and unmanaged within applications—a fragile identity foundation that autonomous agents inherit. The ChromaDB pre-authentication RCE (CVE-2026-45829) and Marimo Python notebook framework WebSocket authentication bypass exemplify how AI infrastructure components are being actively exploited by threat actors deploying NKAbuse malware, reinforcing that AI systems are now operational targets rather than theoretical risk surfaces. Zscaler's Project AI-Guardian, Databricks' Unity AI Gateway Guardrails, and Semgrep's 27-rule AI security ruleset release collectively indicate that the security vendor ecosystem is mobilizing purpose-built tooling for AI-specific threat vectors—though deployment maturity significantly lags the pace of AI adoption across enterprise environments.

🎭 Deepfake & AI Threats

41 signals0 critical9 highAvg: 5.8
The deepfake and synthetic media threat landscape has crossed from theoretical concern to active enforcement and legislative response, with the FTC's activation of Take It Down Act enforcement on May 19, 2026, establishing $53,088 per-violation penalties for platforms failing to remove non-consensual intimate images and AI-generated deepfakes within 48 hours. This enforcement regime—covering Amazon, Meta, TikTok, Discord, and equivalent platforms—marks a structural shift in platform liability from voluntary content moderation to mandatory compliance with measurable deadlines, hash-matching technology requirements, and DOJ criminal prosecution authority. The UK's Ofcom concurrently moved to require tech companies to strengthen detection and removal of non-consensual intimate images through expanded hash-matching and revised codes of practice effective autumn 2026, following an incident involving Grok generating nudified deepfake images that UK PM Keir Starmer characterized as a 'national emergency.' New Zealand's Deepfake Digital Harm and Exploitation Bill passed its first parliamentary reading with unanimous support, expanding the Crimes Act definition of intimate visual recording to include AI-synthesized imagery. These regulatory developments reflect a global legislative convergence driven by the demonstrated harm scale of synthetic media platforms and the inadequacy of voluntary content moderation....read full analysis

On the technical capability frontier, voice cloning from three-second audio samples, high-quality deepfake video production within one hour, and commodity deepfake-as-a-service platforms have collectively made synthetic media accessible to non-experts at scale. McAfee research documents that one in four people have been targeted by AI voice clone scams, with a 77% loss rate among recipients who engaged—average losses ranging from $500 to $15,000, with Americans aged 60+ disproportionately targeted due to greater financial resources. The emergence of Haotian AI as a real-time deepfake platform enabling impersonation during Teams, WhatsApp, and Zoom calls represents the convergence of synthetic media with enterprise communication platforms, expanding attack surface from pre-recorded content to live interactive fraud. Google's SynthID watermarking expansion to Chrome and Search via Lens, AI Mode, and Circle to Search—alongside industry adoption partnerships with OpenAI, Nvidia, Kakao, and ElevenLabs—and OpenAI's dual-layer C2PA metadata plus SynthID watermarking approach for image verification represent the primary technical countermeasures being deployed at scale. However, the availability of open-source tools like Voicebox (26,500+ GitHub stars, local execution, no consent verification, 23-language support from three-second samples) illustrates the fundamental asymmetry: detection and watermarking standards require industry adoption while attack capability distribution faces no such coordination barrier.

📱 Mobile Security

37 signals3 critical8 highAvg: 6.3
Mobile security threats are intensifying across multiple dimensions simultaneously, with the Digital.ai 2026 report documenting that 87% of monitored enterprise mobile applications faced attacks—up from 55% in 2022—with financial services and automotive apps reaching 91% attack rates. The surge reflects both the maturation of mobile attack tooling and the lowering of exploit development barriers through agentic AI, which now enables adversaries to develop mobile exploits in hours rather than weeks. iOS attack rates have risen dramatically to 86% (from approximately 50% in 2023), partly driven by the Coruna and DarkSword exploit kits targeting devices running pre-iOS 26.3 firmware—CISA has added corresponding iOS vulnerabilities to its Known Exploited Vulnerabilities catalog, and millions of iPhones remain on unpatched firmware versions. The continued exploitation of pre-iOS 26.3 devices via the Coruna kit, which bundles 23 exploits across five attack chains targeting iOS versions 13 through 17.2.1, highlights that the long tail of unpatched mobile devices represents a structurally persistent attack surface that patch mandates alone cannot close....read full analysis

At the identity and authentication layer, two critical mobile security developments demand immediate attention. A critical vulnerability in Microsoft Authenticator (CVE-2026-41615, CVSS 9.6) allows attackers to steal authentication tokens and bypass MFA via a malicious unclaimed deep link protocol, potentially enabling password reset and persistent device registration—with Microsoft recommending immediate updates to iOS 6.8.47 and Android 6.2605.2973. Microsoft's concurrent decision to phase out SMS-based authentication for personal accounts reflects industry consensus that SIM-swapping, carrier breaches, and SS7 exploitation have rendered SMS OTP verification inadequate as a security control, accelerating migration to passkeys and hardware-backed authenticators. Google's rollout of opt-in Intrusion Logging within Android's Advanced Protection Mode—preserving encrypted forensic artifacts of device compromise in user Google accounts—provides a detection capability specifically designed for government spyware and police forensic tool activity, addressing the operational gap that sophisticated implants like Pegasus exploit by minimizing on-device forensic footprints. The Trapdoor Android ad fraud operation generating 659 million daily fraudulent bid requests across 455 malicious apps further illustrates the breadth of the mobile threat ecosystem beyond targeted attacks.

Crypto & DeFi Security

35 signals1 critical15 highAvg: 7.4
The DeFi security ecosystem is experiencing an escalating breach cadence that has already exceeded $1 billion in losses for 2026, with cross-chain bridge infrastructure and administrative key management emerging as the dominant attack surfaces. The reporting period alone documented over $32 million in confirmed losses across three separate protocol exploits in five days: THORChain ($10.8 million via transaction validation bypass across Bitcoin, Ethereum, BNB, and Base chains), the Verus Ethereum Bridge ($11.58 million via missing source-amount validation in cross-chain message verification), and Echo Protocol ($76.7 million in unauthorized eBTC minting via compromised admin private key, with approximately $816,000 in actual liquid losses after burn and recovery operations). The Echo Protocol incident is particularly instructive: the exploit did not require any smart contract vulnerability—it exploited weak operational security around administrator credential management, specifically single-signature access with no timelock, no minting cap, and no issuance rate limits. This pattern, combined with the THORChain and Verus bridge logic flaws, indicates that attackers are systematically targeting infrastructure-layer trust assumptions and operational security practices rather than exclusively hunting smart contract bugs....read full analysis

The Lazarus Group's confirmed attribution to the KelpDAO ($292 million) and Drift Protocol exploits in the broader 2026 DeFi hack landscape establishes nation-state actors as major participants in the DeFi theft ecosystem, consistent with DPRK's documented use of cryptocurrency theft for sanctions evasion and foreign currency generation. Cross-chain bridges remain structurally the most dangerous DeFi components due to their role as honeypot liquidity pools and the inherent complexity of cross-chain message verification logic—a complexity that consistently produces exploitable edge cases in bridge validation functions. The widespread use of Tornado Cash for post-exploit laundering across THORChain, Verus, and Echo Protocol exploits demonstrates persistent operational security challenges for blockchain forensics and law enforcement attribution. Bankr's suspension of all transactions following a 14-wallet breach, and HermesVault's permanent shutdown after a $29,000 ALGO withdrawal logic exploit, reflect the reputational and operational fragility of smaller DeFi protocols where a single security failure can trigger existential platform termination—a pattern that disproportionately harms retail users who lack the institutional recourse available to larger protocol participants.

🔑 Identity & Access Security

31 signals1 critical10 highAvg: 7.1
Identity-based attack vectors have consolidated as the central axis of enterprise compromise in 2026, with phishing, OAuth consent abuse, and social engineering against support channels collectively enabling account takeovers that bypass even well-configured multi-factor authentication deployments. The EvilTokens phishing-as-a-service platform's compromise of over 340 Microsoft 365 organizations across five countries in five weeks—by tricking users into approving OAuth consent screens on legitimate identity providers and harvesting refresh tokens valid for the full tenant-policy lifespan—exemplifies a structural gap in identity defenses that focus exclusively on credential replay detection. Because authentication occurs on the legitimate provider before the malicious token grant, these attacks produce no replayed credentials or sign-in events detectable by conventional SIEMs, requiring behavioral analytics and OAuth grant auditing rather than traditional authentication monitoring. Barracuda's 2026 Email Threats Report finding that 90% of high-volume phishing campaigns now use phishing-as-a-service kits, with QR code delivery embedded in trusted PDFs accounting for 70% of malicious documents, reflects a systematic attacker investment in evading URL-filtering and attachment-scanning controls....read full analysis

The Storm-2949 campaign against Microsoft 365 and Azure environments—exploiting Self-Service Password Reset flows through MFA prompt manipulation to gain access to OneDrive, SharePoint, Azure Key Vaults, and SQL databases—demonstrates how legitimate cloud identity management features become attack vectors when social engineering circumvents authentication controls rather than defeating them technically. Microsoft's tracking of this campaign underscores that identity attacks increasingly exploit trusted system workflows rather than vulnerabilities, making them significantly harder to detect through conventional signature-based approaches. The PlayStation Network account takeover vulnerability—where attackers bypass 2FA by providing only a PSN ID and purchase history to Sony support—illustrates the same pattern at consumer scale: social engineering against support channels defeats technical authentication controls regardless of their sophistication. Sophos's finding that 79% of ransomware victims in India confirmed identity attacks as the entry vector, with mean recovery costs reaching $1.64 million, and only 13% of organizations continuously monitoring for unusual login attempts, quantifies the operational consequence of the identity monitoring gap. Operation Ramz's 201 arrests across 13 MENA countries, including dismantlement of phishing-as-a-service infrastructure and financial fraud operations leveraging stolen identity credentials, represents the law enforcement response to an identity threat ecosystem that has industrialized at regional scale.

☁️ Cloud Security

28 signals6 critical2 highAvg: 6.7
The cloud security threat surface expanded significantly during this period, with multiple incidents demonstrating that cloud credential exposure—whether through supply chain compromise, developer misconfiguration, or malicious package injection—provides attackers with direct paths to broad infrastructure compromise. The coordinated Mini Shai-Hulud campaign's primary payload objective was cloud credential harvesting: the worm targeted AWS IAM keys, Azure service account tokens, GCP credentials, HashiCorp Vault tokens, Kubernetes credentials, and SSH keys across npm, PyPI, and Docker Hub simultaneously, with the most severe variant—FIRESCALE, deployed via the compromised Microsoft durabletask PyPI SDK—establishing persistence as a pgsql-monitor.service systemd unit and propagating laterally via AWS SSM and Kubernetes kubectl. The CISA contractor credential exposure incident, in which AWS GovCloud administrative keys remained valid for 48 hours after repository takedown, illustrates that the risk window for exposed cloud credentials extends well beyond initial discovery: any party that cloned the repository during the six-month exposure window retained active access to three U.S. government cloud environments....read full analysis

The ChromaDB pre-authentication RCE vulnerability (CVE-2026-45829) presents a distinct cloud AI infrastructure risk: approximately 73% of internet-exposed ChromaDB instances run vulnerable versions, and successful exploitation grants unauthenticated attackers access to environment variables, API keys, Kubernetes secrets, LLM API keys, and database contents—the crown jewels of AI inference deployments. With no vendor patch available as of version 1.5.8, affected organizations must rely on network isolation, authentication proxies, or migration to the Rust frontend as mitigations. Microsoft's Storm-2949 tracking report documents a cloud-native attack lifecycle—social engineering to Self-Service Password Reset abuse, MFA prompt manipulation, Microsoft Graph API enumeration, and systematic exfiltration from OneDrive, SharePoint, Azure Key Vaults, SQL databases, and storage accounts—that exploits legitimate cloud management capabilities rather than traditional vulnerabilities, complicating detection. Wiz's Runtime Threat Detection for Google Cloud Run, Azure Linux 4.0's pylock sandboxing for Python supply chain risk reduction, and Upwind's AI Agentic Pack for runtime-contextualized cloud alert prioritization represent the defensive vendor response to a threat environment where cloud-native attack paths are outpacing conventional perimeter and endpoint controls.

📜 Regulation & Compliance

25 signals2 critical1 highAvg: 5.7
The regulatory environment surrounding advanced AI capabilities and cybersecurity obligations has entered a period of rapid, reactive evolution driven by the demonstrated offensive potential of frontier AI models. The White House is reportedly preparing an executive order establishing a voluntary framework requiring AI laboratories to provide government access to frontier models at least 90 days prior to public release, with provisions for critical infrastructure providers and a cybersecurity component targeting Pentagon and national security agency hardening. This follows the Pentagon's confirmed deployment of Anthropic's Mythos for U.S. government vulnerability patching and CIA characterization of Mythos as a 'reflection point' for federal agencies managing sensitive information. Anthropic's policy reversal on Project Glasswing—expanding disclosure permissions to allow participating organizations to share Mythos vulnerability findings with external security teams, government agencies, and open-source maintainers under responsible disclosure norms—represents a significant shift in the balance between competitive AI capability restriction and collective defensive benefit. Congressional pressure from both chambers has been a material driver of this evolution, with legislators warning that restricted disclosure frameworks hamper the broader defensive security community....read full analysis

At the compliance and standards layer, NIST finalized SP 800-172 Revision 3 on May 13, 2026, adding 80 new controls for protecting Controlled Unclassified Information on nonfederal systems—specifically targeting Advanced Persistent Threats from China, Russia, Iran, and North Korea through defense-in-depth strategies including penetration-resistant architecture and supply chain risk management. Defense contractors now face the dual pressure of mandatory CMMC third-party assessment requirements (effective November 2025) and the enhanced SP 800-172 control baseline, with industry analysts projecting 33,000–44,000 companies may exit the defense market due to compliance cost burden. The EU's NIS2 directive expansion—from approximately 10,000 to 160,000 covered entities—is simultaneously driving significant cybersecurity hiring demand across Europe. The CISA credential exposure incident has amplified Congressional urgency around federal cybersecurity contractor accountability, while the FBI's warning on rising mobile threats and the FTC's activation of Take It Down Act enforcement with $53,088 per-violation fines for deepfake non-removal indicate regulators are moving to operationalize enforcement mechanisms across multiple threat vectors concurrently.

🏭 ICS/OT Security

24 signals5 critical3 highAvg: 8.1
Critical infrastructure and operational technology environments face an intensifying threat convergence of nation-state targeting, commodity ransomware campaigns, and newly disclosed vulnerabilities in widely deployed ICS platforms. CISA's advisory disclosing four critical vulnerabilities in ScadaBR 1.2.0—including unauthenticated sensor reading injection (CVE-2026-8602, CVSS 9.1), OS command injection enabling root execution (CVE-2026-8603, CVSS 8.8), CSRF (CVE-2026-8604), and hardcoded credentials (CVE-2026-8605)—represents immediate risk to manufacturing, energy, water, chemical, and dam sectors globally. CISA's advisory explicitly notes that ScadaBR's dual identity as both an IT web application and an OT control system amplifies the consequences of ordinary software flaws: unauthenticated RCE on an internet-exposed SCADA instance translates directly to potential process manipulation, safety incidents, and operational disruption. The Huawei enterprise router zero-day that caused Luxembourg's nationwide three-hour telecommunications outage—disabling mobile, landline, and emergency services simultaneously—demonstrates that unpatched critical infrastructure vulnerabilities can produce kinetic, population-scale consequences without requiring any lateral movement or post-exploitation activity....read full analysis

The Iran-linked breach of automatic tank gauge systems at US gas stations represents a continuation of low-threshold, high-visibility critical infrastructure targeting that has characterized Iranian cyber operations throughout the conflict period. Exploitation of internet-exposed Veeder-Root TLS-350 and TLS-450 Plus consoles with no authentication protection to manipulate fuel level sensor readings reflects deliberate targeting of operational visibility rather than physical destruction—a reconnaissance and disruption capability with potential implications for supply chain logistics and emergency response coordination. CISA's guidance directing critical infrastructure operators to plan for operational isolation scenarios—explicitly assuming threat actors may already have access to OT networks, consistent with Volt Typhoon pre-positioning activity—signals that defensive posture must now account for sustained adversary presence rather than perimeter breach detection. The formation of C2 ISAC among major US telecom operators following the Salt Typhoon campaign, and INTECH's OT cybersecurity infrastructure project for Middle Eastern offshore oil fields, reflect growing recognition that information-sharing and purpose-built OT security architecture are prerequisites for resilience against the Iran and China-aligned threat actors most actively targeting energy and communications infrastructure.

🔍 OSINT & Tools

18 signals1 critical1 highAvg: 5.5
The OSINT and threat intelligence tooling domain reflects a broader industry shift toward machine-speed intelligence integration as AI acceleration compresses the timeline between vulnerability disclosure and active exploitation. The core operational challenge articulated across multiple intelligence sources is the growing incommensurability between CVE volume (approximately 50,000 annually) and human analyst capacity to triage, contextualize, and operationalize findings—a gap that AI-accelerated threat actors are actively exploiting to shrink the defense window from months to hours. Recorded Future's autonomous threat operations framework, Tenable's AI-assisted Vulnerability Priority Rating system, and the emerging Lyrie autonomous pentesting agent (reaching version 3.1.0 with enhanced encryption and expanded exploitation capabilities) collectively define the capability frontier that both offensive and defensive practitioners are racing to deploy. Black Kite's supply chain vulnerability analysis finding that only 58 of 48,000+ published CVEs pose genuine exploitable threats to enterprise supply chains underscores the intelligence filtering problem: without precision prioritization, defenders expend resources across a threat space too vast to meaningfully address....read full analysis

International cooperation frameworks are maturing as a force multiplier for threat intelligence operationalization. Operation Ramz—the first large-scale INTERPOL-coordinated cross-regional cybercrime investigation across 13 Middle Eastern and North African countries—resulted in 201 arrests, 382 additional suspect identifications, 53 server seizures, and disruption of 3,867 victim cases, with Kaspersky contributing approximately 8,000 pieces of intelligence on region-specific malware and C2 infrastructure. Finland, the UK, Norway, Sweden, and the US conducted the Cyber Byte multinational exercise in April–May 2026 to develop joint protection of military logistics infrastructure against advanced persistent threats in NATO's northern region. India's National Cybersecurity Coordinator's emphasis on industry-government collaboration and real-time threat information sharing—explicitly citing AI capability proliferation within 6–9 months and practical quantum computing within 4–5 years as planning horizons—indicates that national-level threat intelligence architectures are being redesigned around anticipated capability curves rather than current threat baselines.

10/10
critical
YellowKey (CVE-2026-45585) - Windows BitLocker Zero-Day Encryption Bypass
CVE-2026-45585 (YellowKey) is an actively disclosed, unpatched Windows BitLocker security feature bypass in which an attacker places specially crafted 'FsTx' files on a USB drive or EFI partition, reboots the target into WinRE, and triggers…

CVE-2026-45585 (YellowKey) is an actively disclosed, unpatched Windows BitLocker security feature bypass in which an attacker places specially crafted 'FsTx' files on a USB drive or EFI partition, reboots the target into WinRE, and triggers an unrestricted shell by holding CTRL — granting full access to the BitLocker-protected volume. Microsoft's emergency mitigations require removing the autofstx.exe entry from the Session Manager BootExecute REG_MULTI_SZ registry value, re-establishing BitLocker WinRE trust, and transitioning all encrypted devices from TPM-only to TPM+PIN mode via PowerShell, CLI, or Group Policy/Intune. The disclosure is part of a deliberate multi-vulnerability protest campaign by researcher 'Nightmare Eclipse' against MSRC, which has also produced CVE-2026-33825 (now patched), an unnamed LPE (now patched), a SYSTEM shell privilege escalation, and a Microsoft Defender definition update blocking zero-day.

bleepingcomputer.comAttacks & Vulnerabilities
9/10
critical
Vulnerability Exploitation Overtakes Credential Theft as Top Breach Vector (Verizon DBIR 2026)
The Verizon 2026 DBIR, analyzing 31,000 incidents and over 22,000 confirmed breaches — nearly double last year's 12,195 — finds that unpatched vulnerability exploitation now drives 31% of breaches, surpassing credential abuse (13%) as the…

The Verizon 2026 DBIR, analyzing 31,000 incidents and over 22,000 confirmed breaches — nearly double last year's 12,195 — finds that unpatched vulnerability exploitation now drives 31% of breaches, surpassing credential abuse (13%) as the leading initial access vector for the first time on record. Median time-to-full-patch deteriorated to 43 days in 2025 (up from 32), organizations patched only 26% of CISA KEV entries (down from 38%), and AI is compressing exploitation windows from months to hours, with threat actors documented using AI assistance across a median of 15 distinct attack techniques. Ransomware featured in 48% of confirmed breaches, third-party involvement reached 48% of total breaches (a 60% year-over-year increase), and only 23% of third-party organizations fully remediated missing or improperly configured MFA on cloud accounts.

securityweek.comAttacks & Vulnerabilities
9/10
critical
TeamPCP Supply Chain Attack Campaign (7-Day Arc: Shai-Hulud, Mini Shai-Hulud, GitHub Breach)
The TeamPCP threat group has executed a sustained, escalating supply chain campaign across at least two named waves ('Shai-Hulud' and 'Mini Shai-Hulud'), compromising a single developer account to publish 630 malicious package versions across 317…

The TeamPCP threat group has executed a sustained, escalating supply chain campaign across at least two named waves ('Shai-Hulud' and 'Mini Shai-Hulud'), compromising a single developer account to publish 630 malicious package versions across 317 open source packages — including Alibaba's Antv library — in approximately 20 minutes, targeting downstream credential theft from password managers and connected services. In the most material escalation, TeamPCP confirmed on May 19 that it compromised a GitHub employee via a poisoned VS Code extension, and is now offering approximately 4,000 internal GitHub repositories for sale at $50,000 or more, representing a platform-level compromise that threatens the integrity of hosted source code and CI/CD pipelines globally. Prior Mini Shai-Hulud activity also breached OpenAI via the TanStack open source library; organizations should treat all dependency updates published during the campaign window as suspect and audit package integrity hashes.

techcrunch.comAttacks & Vulnerabilities
9/10
critical
CISA Credential Leak - AWS GovCloud Admin Keys Exposed on Public GitHub Repository
A public GitHub repository associated with a CISA contractor exposed AWS GovCloud administrative credentials, plaintext passwords stored in CSV format, internal deployment files, and backup data, with the repository configured to explicitly disable GitHub's secrets…

A public GitHub repository associated with a CISA contractor exposed AWS GovCloud administrative credentials, plaintext passwords stored in CSV format, internal deployment files, and backup data, with the repository configured to explicitly disable GitHub's secrets detection feature — indicating this was not a passive oversight. GitGuardian researcher Guillaume Valadon assessed the exposure as 'the worst leak I've witnessed in my career,' noting the credentials likely provided privileged access to multiple internal CISA systems and cloud environments prior to repository removal. The incident has escalated to the U.S. Senate, with Sen. Maggie Hassan formally requesting an urgent classified briefing; organizations with any integration to CISA contractor systems or shared GovCloud environments should immediately audit access logs and rotate exposed credentials.

esecurityplanet.comBreaches & Leaks
8/10
high
ChromaToast (CVE-2026-45829) - Unpatched ChromaDB Remote Code Execution
CVE-2026-45829 (ChromaToast) is a pre-authentication remote code execution vulnerability affecting all ChromaDB versions from 1.0.0 through the current release (1.5.8), in which the server trusts and executes attacker-supplied HuggingFace model identifiers before performing any authentication…

CVE-2026-45829 (ChromaToast) is a pre-authentication remote code execution vulnerability affecting all ChromaDB versions from 1.0.0 through the current release (1.5.8), in which the server trusts and executes attacker-supplied HuggingFace model identifiers before performing any authentication check — enabling an unauthenticated attacker to download and execute arbitrary code, gaining full control of the server process and access to API keys, environment variables, mounted secrets, and all files on disk. Discovered and reported by HiddenLayer beginning February 17, 2026, and independently reported by researcher Azraelxuemo in November 2025, the vulnerability remains completely unpatched with no response from Chroma, and approximately 73% of the estimated internet-accessible ChromaDB deployments are currently exposed. With 13 million monthly pip downloads and adoption by high-profile AI organizations including Mintlify, Factory AI, and Weights & Biases, the remediation path until a patch is released is strict network isolation of ChromaDB instances to trusted clients only.

securityweek.comAttacks & Vulnerabilities

Cyber Threatcast is generated by an autonomous AI intelligence pipeline. All assessments are algorithmically derived.

Published by halilozturkci.com