This is the version that shipped with Nightjar Browser 0.3.18. The current one is at /security.html.
Security — Nightjar Browser
Last updated: 2026-11-04 · Applies to: Nightjar Browser 0.3.18
Reporting something
contact@nightjarbrowser.ai. There is no bug bounty and no formal SLA — this is a small project and pretending otherwise would waste your time. What you will get is a reply, and a fix if the finding is real.
If you would rather not send details by email first, send a one-line "I have found something in X" and we can arrange somewhere better.
Please do report publicly if we go quiet. A finding nobody acts on is worth more to users disclosed than sat on, and the Licence §2a explicitly permits publishing what you find, including when it is unflattering.
Updates
How do I get security updates?
| Component | When a fix reaches you | What you do |
|---|---|---|
| Page engine (WebView2 on Windows, WebKit on macOS) | When Microsoft or Apple ships one | Nothing. Restart Nightjar if it has been a while |
| llama.cpp (the AI engine) | Inside the next Nightjar update | Nothing beyond updating Nightjar |
| Python dependencies | Inside the next Nightjar update | Nothing beyond updating Nightjar |
| Nightjar itself | Downloaded in the background when we release | Nothing: it installs the next time you close Nightjar |
The AI engine and the Python packages ship inside Nightjar, so their fixes reach you the same way Nightjar's own do.
Two different things check for updates:
- The browser, on launch, asks whether there is a newer Nightjar.
- A daily job on our side reads published advisories for everything Nightjar ships and watches llama.cpp's releases. It runs on our infrastructure, never touches your machine, and exists so that "nobody noticed" is not why a fix is late.
Chrome and Edge just announced a batch of CVEs. Am I affected?
Almost certainly the fix has already reached you, or will without you doing anything.
On Windows, Nightjar renders pages with WebView2 in Evergreen mode: the same Chromium engine Edge uses, updated through the same Microsoft update service. When Microsoft patches those CVEs, your copy is patched, with no Nightjar release involved. On a Mac, pages are drawn by WebKit, which macOS updates with Safari.
Two things can interrupt it on Windows:
- A running WebView2 keeps the version it loaded. Restart the browser.
- Some machines have Edge Update disabled by policy, usually in managed environments. Then the engine stays where it is and nothing tells you.
How do I check which engine version I have?
The AI panel shows it: Page engine: WebView2 <version>. Compare it with Microsoft's WebView2 release notes. If it says version not reported, the engine is old enough not to expose it, which is itself a reason to update it.
Why is llama.cpp pinned if that delays its fixes?
Because the alternative is worse. Each Nightjar build uses one exact llama.cpp release, checked against its fingerprint, so a tampered copy upstream cannot end up inside Nightjar.
The cost is real: an upstream fix reaches you only when we move to the newer release and ship it. The daily job above is what makes sure we notice.
Does Nightjar update itself?
Yes. Once on launch it asks GitHub whether there is a newer version, sending only the version you have. A newer one is downloaded in the background, checked against the checksum GitHub publishes (on a Mac, also that Apple notarized it), and installed the next time you close Nightjar.
You can have it ask before downloading, or switch the check off, in Settings → Privacy & blocking. The copy from the Microsoft Store is updated by the Store.
What is verified
What stops a tampered download running?
- Nightjar's own updates must match the checksum GitHub publishes for the release, and on a Mac carry Apple's notarization.
- Built-in app updates, such as Scribble's, must carry our signature.
- The WebView2 installer, on the rare machine that needs one, must be signed by Microsoft before it is run.
- AI models come straight from Hugging Face over HTTPS, and where the catalogue records a model's fingerprint, it is checked.
Does it block phishing and malware sites?
Yes, through the page engine's own protection, which Nightjar switches on explicitly so a changed default cannot remove it.
- Windows: Microsoft Defender SmartScreen, as in Edge. It follows Windows Security's SmartScreen for Microsoft Edge setting; turned off there, it is off here too.
- macOS: Safari's fraudulent-website warning.
- Downloads are not checked by the browser itself, as Edge checks them. What still stands in the way is Windows: every download is marked as coming from the internet, so SmartScreen checks a program when it is opened, and Microsoft Defender scans files as they are saved.
Is the local AI server exposed to anything?
No. It listens only on this computer, and accepts requests only with a key that is made fresh each time it starts.
Can a web page reach the browser's internals?
Not its settings, your profile or the AI. Pages can send Nightjar a few kinds of messages, for things like ad blocking, and those are treated as untrusted. Settings and the PDF editor accept messages only from Nightjar's own pages.
What this does not protect against
-
Prompt injection. A web page can hide text meant to steer an AI assistant. No AI browser can fully prevent this today, including the assistants in Chrome and Edge, and Nightjar is no exception. It removes text it can tell is hidden before the assistant reads a page, which makes this harder. It does not stop it: some hiding techniques get through, and text inside images, scans and PDFs is not checked the same way. On web pages this happens quietly, with a note in the Activity tab, so ordinary sites do not fill the chat with warnings. Be careful letting the assistant act for you — filling in a form or carrying out a task — on a site you do not trust.
-
Fingerprinting. A page can still identify your machine by its fonts, screen and hardware.
-
Your network. Your internet provider or employer still sees which sites you open. Nightjar is not a VPN.
-
A compromised machine. Everything is stored on your computer, so a program that takes over your computer can reach it. That is the trade for having no servers.
That includes the sign-in cookies of sites you choose to stay signed in to. They are protected by your computer account, as every browser's are. Chrome and Edge add one more lock that Nightjar's page engine does not have yet, which makes it a little harder for malware to copy them. But a program running as you can already read your files, record what you type and watch your screen, so the protection that matters is keeping it off your computer in the first place. Nightjar keeps what is exposed small: sites you have not chosen to stay signed in to are forgotten when it closes, and Nightjar does not store passwords — use a password manager.
-
Small-model mistakes. A local model will get things wrong that a large hosted one would not. The assistant labels where an answer came from; it cannot make a wrong answer right.
Can I verify the binary matches the source?
Not yet. The source is not public, and builds are not reproducible. What you can check is that a download came from us unchanged: the Windows build is signed by Purple Comet LLC, and the Mac build is signed by us and notarized by Apple.
Known unfixed items
- Builds are not reproducible — above.
- Accessibility has not been audited, which is a usability failure before it is a security one but can be both.
Questions, or something that belongs on this page: contact@nightjarbrowser.ai · Purple Comet LLC, California.