When people think about a cyberattack, they usually picture stolen passwords, malware, ransomware or someone exploiting a vulnerability to break into a system.
Side-channel attacks work differently. Instead of directly stealing a secret, an attacker studies the traces a computer produces while carrying out normal operations. Tiny differences in processing time, electricity consumption, electromagnetic signals, sounds or hardware activity can reveal clues about what is happening inside the machine.
Think of a locked safe. A thief may not know its combination or be able to break the lock, but if turning the dial produces different clicks or pauses, listening closely could reveal information about the combination. The safe is not deliberately revealing anything. Its physical behavior is simply giving away clues.
Computers can do much the same thing.
A problem that is decades old
Side-channel attacks are not a new phenomenon.
In 1985, Dutch researcher Wim van Eck demonstrated that electromagnetic emissions from video display units could be captured and decoded, potentially revealing what was being displayed. The screen was not intentionally broadcasting its contents, but its normal operation produced signals that could be observed externally.
The technique became particularly important in cryptography during the 1990s. In 1996, researcher Paul Kocher showed that measuring tiny differences in the time taken by cryptographic operations could reveal information about private keys. In 1999, Kocher, Joshua Jaffe and Benjamin Jun demonstrated that measuring power consumption could similarly expose information from cryptographic devices.
Researchers later showed that sound could become another source of leakage. Experiments demonstrated that acoustic emissions from laptops performing cryptographic operations could be analyzed to recover a 4,096-bit RSA key under controlled conditions.
These discoveries changed the way security engineers evaluated systems. A cryptographic algorithm could be mathematically secure while its implementation still leaked information through timing, power, sound or electromagnetic radiation.
When processor performance became a security problem
The rise of modern CPUs created another class of side channels.
Processors use speculative execution to predict which instructions a program will need and execute them ahead of time, improving performance. In 2018, researchers disclosed Meltdown and Spectre, demonstrating that traces left by speculative execution could allow malicious code to infer information that should have remained protected.
The attacks challenged an important assumption in computing: that programs running on the same machine can be reliably isolated from one another. They also demonstrated that security problems could originate from performance features built deep inside the processor rather than from conventional software bugs.
Researchers have continued finding similar problems in newer hardware.
In 2022, Hertzbleed showed that dynamic voltage and frequency scaling, a feature used to manage processor power and performance, could become a timing side channel. Because processor frequency can vary with the computation being performed, an attacker could potentially infer information remotely without directly measuring power consumption. The researchers demonstrated implications for cryptographic key extraction on modern Intel and AMD processors.
In 2023, Downfall exposed another weakness in certain Intel processors through the Gather instruction, while Zenbleed affected AMD's Zen 2 architecture and could expose information from another execution context under particular conditions.
The pattern is becoming difficult to ignore: features designed to make computers faster or more efficient can also create unexpected paths for information leakage.
Side channels are spreading beyond CPUs
Researchers are now finding these channels in other parts of the computing stack.
GPU.zip demonstrated how hardware-based graphics compression could create a side channel capable of exposing visual information processed by graphics processors. The research showed that the problem could extend beyond the CPU and into the way GPUs handle graphical data.
In 2024, GoFetch exposed another hardware-level problem in Apple processors. The attack targeted a feature called a data memory-dependent prefetcher, which predicts future memory requirements to improve performance. Researchers demonstrated that this behavior could undermine protections in cryptographic software and help extract secret keys.
These attacks illustrate why simply securing software is not always enough. Hardware underneath the software can produce information that applications never intended to expose.
The SSD can become a side channel too
The latest research pushes the idea even further.
In 2026, researchers at Graz University of Technology introduced FROST, short for "Fingerprinting Remotely using OPFS-based SSD Timing." The attack targets the browser's Origin Private File System, or OPFS, a feature that allows websites to store and access files within their own sandboxed storage area.
FROST does not give a malicious website direct access to another application's files.
Instead, it measures delays caused when multiple programs compete for the same SSD.
The concept is similar to traffic on a shared road. A driver does not need to see another vehicle to know that it is there. If traffic suddenly makes the journey slower, the delay itself provides information.
FROST applies the same principle to storage. A malicious webpage can repeatedly perform storage operations through OPFS and measure tiny changes in how long they take. Those changes can reveal patterns in other activity occurring on the same computer.
The researchers found that the technique could be used to fingerprint websites and applications. In their evaluation, FROST achieved an F1 score of 88.95% for website fingerprinting and 95.83% for application fingerprinting on tested systems. It can also operate remotely through JavaScript without requiring native code execution.
That does not mean websites can simply read a user's files or see everything happening on a computer. FROST is an inference attack. It identifies activity from the timing patterns produced by shared hardware resources.
A specialised threat, but an important warning
Side-channel attacks are not currently the everyday attack method most users are likely to encounter. Cybercriminals generally have easier options, including phishing, credential theft, malware, ransomware and exploiting vulnerable software.
But their importance extends beyond how frequently criminals use them.
Side-channel research repeatedly reveals that security boundaries can be weaker than they appear. A processor, GPU, browser or storage device may never intentionally disclose sensitive information, yet its normal operation can leave behind measurable clues.
From electromagnetic emissions and cryptographic timing to speculative execution, processor frequency, GPU compression and SSD activity, the side channel keeps changing as computing technology evolves.
Computers do not always need to be hacked for them to leak secrets.
Sometimes, all an attacker needs is to listen to what the machine reveals while it is doing its job.
Metabase revealed the attacks last week and warned that its Metabase Cloud SaaS platform was hacked via an earlier unknown bug impacting variants 1.58 and above. Metabase warned that self-hosted deployments may also be vulnerable.
In a blogpost, Metabase CEO, Sameer Al-Sakran said that, “"We recently identified that Metabase Cloud was attacked by someone utilizing an unknown ("0-day") security vulnerability in versions 1.58 and above."
Metabase stopped the endpoints used for the attack and released a fix for the flaw.
"The vulnerability is an unauthenticated SQL injection flaw in Metabase that can ultimately give a remote attacker administrator access to a customer's instance."
Although Metabase has not given the flaw a CVE identifier, its security advisor labels it as Critical with CVSS score of 10.0 and acknowledges that it has been actively exploited.
"This is a CRITICAL vulnerability that allows an unauthenticated remote attacker to inject arbitrary SQL into the Metabase application database, which can give them administrator access to the instance,” said a GitHub security advisory.
"From there, the attacker could change the application configuration, steal stored credentials for the connected databases, read any data accessible through those connections, and export data. Metabase has confirmed active exploitation of this vulnerability.
Metabase is available both as Metabase Cloud, the organization’s managed SaaS offering, and as software that companies can host themselves.
According to Metabase, its Cloud consumers have already been patched and upgraded while businesses running flawed self-hosted deployments should update manually.
Metabase has recommended self-hosted customers to immediately upgrade, review API keys and administrator accounts for illegal changes, remove all active user sessions, check logs and query history for any compromise, and rotate credentials for linked databases.
Framework, a laptop maker company has confirmed data theft after hackers breached its Metabase instance. The hackers stole customer information, such as names, login IP addresses, email addresses, company names, contacts, shipping and billing addresses.
For Framework, stolen information of Business customers may include contacts, VAT, company names, billing email address, and EIN.
Tally also informed its users that its Metabase analytics environment was hacked on August 3.
Atlassian's Rovo AI assistant has been exposed to two independent attack techniques that could cause it to retrieve Jira and Confluence data accessible to an authenticated user and transmit the information to an attacker-controlled server.
AI security firm PromptArmor and Varonis Threat Labs identified the techniques through different attack paths. Varonis' RovoBlast vulnerability has been fixed by Atlassian, while PromptArmor said its separate content-based attack remained exploitable when it published its findings on August 5, 2026.
Neither finding demonstrated a direct bypass of Jira or Confluence permissions. Instead, both attacks abused the legitimate access available to a victim's Rovo session.
Malicious content can manipulate Rovo
PromptArmor demonstrated an indirect prompt-injection attack in which attacker-controlled instructions were embedded inside content processed by Rovo.
In its example, a user uploaded a malicious document and asked Rovo to organize Jira tickets. The concealed instructions directed the assistant to search Jira and Confluence, collect information available to the user and place the results into an attacker-controlled URL request.
The attacker could then recover the stolen ticket and page contents through server logs.
PromptArmor said the victim would later see the expected ticket suggestions without an obvious indication that information had also been transmitted externally. The attack was not entirely zero-click, as the victim still had to expose Rovo to the malicious content and initiate a normal request. However, the subsequent exfiltration did not require a separate human approval step.
The firm also reported that disabling Rovo's web-search capability did not prevent its demonstrated attack because the exfiltration relied on a separate URL-retrieval capability.
PromptArmor identified the lack of a control preventing Rovo from opening a URL constructed by the model as a root cause. It also noted that Rovo can render Markdown images from model output, which could provide another potential route for data leakage, although the firm did not demonstrate a complete Rovo attack through that mechanism.
PromptArmor said it disclosed the issue to Atlassian on May 23, followed up on June 4 and July 29, and published after reporting no further communication. Its disclosure did not establish whether the content-based attack was remediated after publication.
RovoBlast used a malicious link
Varonis discovered a separate vulnerability involving Rovo's "rovoChatPrompt" URL parameter.
An attacker could place instructions directly into a specially crafted Rovo Chat link. When an authenticated user clicked the link, Rovo would load the attacker-controlled prompt and execute it using the user's existing permissions.
Varonis demonstrated the technique by instructing Rovo to retrieve sensitive information, place it into an attacker-controlled image URL and fetch the resource, thereby sending the data to the attacker.
The researchers successfully exfiltrated a private API key stored in Confluence. They also tested the technique against Jira information and data accessible through SharePoint and Outlook connectors.
The vulnerability, dubbed RovoBlast, was reported through Bugcrowd, received a P2 priority rating and earned a $6,000 bounty. Bugcrowd records Atlassian as deploying a server-side fix on July 8, 2026, after which the researcher validated the remediation and the report was marked resolved.
Enterprise permissions remain central to the risk
Rovo operates across Atlassian products and can incorporate information from connected third-party applications. Atlassian says Rovo access follows the permissions available to the user, meaning the demonstrations did not provide attackers with unrestricted tenant access.
However, the findings expose a different problem: an attacker can attempt to make the AI assistant use a victim's legitimate permissions for an unintended purpose.
Atlassian provides administrators with controls to restrict Rovo by application and, for Enterprise customers, by user group. Rovo is available on Standard, Premium and Enterprise Cloud plans, while disabling Rovo for one Jira-family application may not remove shared Rovo Search, Chat and Create capabilities if another Jira application on the same site still has Rovo enabled.
Neither disclosure reported confirmed exploitation against a real organization, and neither issue has a CVE or entry in CISA's Known Exploited Vulnerabilities catalog as of August 8.
The immediate status is therefore split: Atlassian has confirmed the RovoBlast link vulnerability is closed, while the post-publication status of PromptArmor's separate content-borne attack remains unconfirmed.
Organizations using Rovo should review which applications, user groups and third-party connectors have access, tighten underlying data permissions and avoid treating the web-search setting alone as a complete defense against AI-assisted data exfiltration.
Experts found a live campaign that abused spoofed customer-side safe sender exclusions and RingCentral emails to escape email gateway checks and send phishing traps attacking Microsoft 365 accounts.
"Greatness supports AiTM [adversary-in-the-middle] credential and token theft, device code phishing, and OAuth consent abuse, all from the same operator panel and shared backend infrastructure," ZeroBec, who discovered the campaign, said in a report.
"The platform now supports AiTM token theft, device code phishing, OAuth consent abuse, and multiple target platforms, including iCloud, Yahoo, and Google Workspace. This evolution reflects the broader trend of PhaaS platforms expanding from simple credential harvesting to integrated attack ecosystems."
The phishing platform was first found by Cisco Talos in May 2023, showing how hackers are including it in their campaigns to attack Microsoft 365 business users since May 2022.
Built to ease cybercrime, access to Greatness is given through a subscription available on Telegram channel called @GreatnessPage having over 3,250 subscribers and works as a central hub for feature updates and announcements. Hackers can get a subscription at $289 per month, rising from $120 per month from January 2024. The subscription offers access to an operator that consists of a dashboard with CAPTCHA selection, domain configuration, campaign statistics, and more than 11 downloadable trap templates including QR codes, voicemail, and document sharing.
The operators of Telegram channel in November 2025 said that Greatness keeps stolen cookies secure through one-way hash protection and the information can be taken out only by the customers via their Telegram account two factor authentication code.
Threat actors that buy a subscription by giving their bot API token and Telegram chat ID can use the panel via an “O365 Panel” login page that needs a 9-character license key and a user ID. Once registered, customers are shown a dashboard and an operator-particular domain.
The dashboard is a standard place that provides campaign statistics such as heat map of victims and captured cookies. "Observed templates include: AudioLogin, ChatAssistance, WindowsExplorer, Voicemail, OneDrive, QR, VideoPlayer, and additional variants. "Each template contains pre-built HTML, PDF redirectors, SVGs, and letter templates, lowering the barrier to entry so operators do not need to build lures from scratch."