Imagine you’re in a confidential meeting. You jot down a quick note, then click a link a colleague sent you. Suddenly, every transcript, every strategy session, every password you’ve ever typed into that app — gone. Handed to an attacker on a silver platter.
This isn’t a hypothetical. It’s real. And it’s happening to thousands of professionals who trust their AI note-taking apps.
Granola, a popular AI note-taking tool used by execs and founders, just disclosed a vulnerability that lets a single click steal your entire session — and everything inside it. The technical write-up from security firm Strix.ai is terrifyingly simple: the desktop app uses a webview with a weak navigation protocol. A malicious link can hijack that protocol, grab your session tokens, and walk away with your digital life.
Your local desktop app is not safer than a browser. It’s often less safe. That’s the uncomfortable truth nobody wants to hear.
Here’s the problem: we’ve been taught that native apps are more secure. They run on your machine, not in the cloud. They don’t have the same attack surface as a website. But Granola is built on web technologies — Electron, webviews, JavaScript. That means it inherits every web vulnerability, plus a few new ones. The ‘local’ illusion gives you a false sense of security while the real danger is hiding in plain sight.
You’ve probably installed Granola, Otter, or Fireflies on your laptop. You trust them because they’re on your desktop, not in a browser tab. But here’s the truth: that trust is a liability. The most dangerous security assumption you can make is that a local app is safer than a browser.
The attack works like this: the app registers a custom URL scheme (e.g., granola://). If you click a link that triggers that scheme, the app opens and processes the request. But the app doesn’t validate where the request came from. An attacker can craft a URL that loads a malicious page inside the app’s webview, which then steals the session cookie — the same cookie that keeps you logged in. No 2FA, no password, no second chance. One click, and you’re owned.
This isn’t a bug in Granola’s code. It’s a design flaw in how we build modern desktop apps. We’ve traded security for convenience. The ‘one-click’ experience that makes these apps so frictionless is the exact same mechanism that makes them so dangerous. Convenience is the enemy of security, and nowhere is that more true than in the ‘one-click’ promise.
So what do you do? You could stop using hybrid desktop apps altogether. Or you could demand that every app vendor implements proper origin validation, sandboxed webviews, and can’t trust any URL scheme. But the real solution is simpler: stop treating your desktop app like a fortress. It’s a glass house. And a single click can shatter it.
I’ll leave you with this: next time you’re about to click a link in your note-taking app, ask yourself — is this note worth my entire digital workspace? Because that’s the bet you’re making.
FAQ
Q: I use two-factor authentication. Doesn't that protect me from this kind of attack?
A: No. 2FA protects your login, but this attack steals your session token after you're already authenticated. The attacker doesn't need your password or 2FA code — they just need that live token, which is stored in the app's insecure webview. 2FA is useless once the session is active.
Q: I use Granola for my work notes. What should I do right now to protect myself?
A: First, check if you have the latest version of Granola — they released a fix. If you can't update, stop clicking any links inside the app. Better yet, treat the app as if it's a browser: use it only for note-taking, never for navigation. For maximum safety, switch to a browser-based note-taking tool that enforces strict origin isolation.
Q: Isn't this just a niche bug in one app? Why should I care about 'hybrid desktop app' architecture?
A: It's not niche. Hundreds of modern apps — from Slack to Discord to VS Code — use the same Electron/webview architecture. The vulnerability pattern is universal. Granola just happened to get caught. The real issue is that we've normalized a design where local apps run untrusted remote content, and that's a systemic risk. Every Electron app is a potential attack surface.