| Version | Supported |
|---|---|
| 0.1.x | Yes |
Please do not open a public issue for a security bug. Use GitHub's private security advisory feature (Security tab → Report a vulnerability), or contact the maintainer directly.
Include:
- the version and commit,
- the affected tool or endpoint,
- a minimal reproduction,
- the impact you believe it has.
The daemon runs at High integrity, so issues in authentication, path handling, or the Procmon flag allowlist are treated as high priority. You can expect an acknowledgement within a few days.
In scope:
- bypassing the bearer-token check,
- reaching the daemon from a non-loopback interface,
- escaping the capture directory,
- making the daemon spawn anything other than the allowlisted Procmon flags,
- reading or deleting captures without authorization,
- a Medium-integrity daemon staying alive when it should exit.
Out of scope:
- a malicious local administrator (they already have the same capabilities),
- physical access to the machine,
- a modified or trojaned
Procmon64.exe, - findings that require
PROCMON_ALLOW_MEDIUM=1(test-only mode).
See docs/security.md for the full threat model.