How to report
Email security@akev.dev with:
- what is affected: the app (its version, from
akev version, and your OS), the website or the licensing service; - what an attacker can do, and what they need first (a network position, local access, a malicious server, a crafted capture file…);
- steps or a proof of concept to reproduce it.
Please don’t open a public GitHub issue for a vulnerability, and don’t include real captured traffic, licence keys or other people’s data in your report: it can contain secrets.
What happens next
- We confirm we got your report, and tell you whether we can reproduce it.
- We fix confirmed issues in a release, and agree with you when to publish the details: after the fix is out.
- Unless you’d rather stay anonymous, we credit you in the release notes and the advisory.
In scope
- The Akev app: the proxy, the API and the web UI it serves, the desktop app, the CLI, the MCP server, the update check and the signed update packages, and the release packages and Docker image (source: github.com/akevdev/akev).
- This website and its licensing service (
/api): accounts, licence keys, the Stripe webhook.
By default, Akev’s proxy serves only this computer and private networks, refuses requests from other machines to this computer’s own loopback services, serves its API to other machines over HTTPS only, and shows AI agents captured secrets as [redacted]; a way around any of these is in scope.
Akev is a man-in-the-middle proxy by design: the clients you connect trust its certificate authority, and its private key is in your data directory. Findings that need that key, or an attacker who already controls your computer or account, are usually expected behaviour; tell us anyway if Akev makes it worse than it has to be (for example, if another user on the machine can read the key or reach the API). Denial of service through heavy traffic, missing hardening headers without an impact, and social engineering are out of scope.
Good faith
Test against your own installation and your own account. Don’t access other people’s data, don’t degrade the website for others, and don’t use what you find beyond what you need to show it. If you follow this policy, we won’t pursue legal action over your research.
Everything else
Bugs that aren’t security issues go to the issue tracker; questions about a purchase to support. The machine-readable version of this page is /.well-known/security.txt.