Hermes Pentest
From its catalog listing
Guided local Vite/Supabase source input discovery, fresh human approval, offline build and isolated testing with synthetic data. Populated/absent SQL controls and authenticated persisted-text XSS checks verify actual input/render paths. Reports distinguish rejected probes from failed controls and count planned versus completed same-user and cross-user stored workflows separately. Uses the provider already configured in Hermes. Also supports explicit local web/API discovery, controlled SQL injection, browser-proven reflected/DOM/stored XSS, access contracts, owner-approved localhost servers, multi-service applications and native/CLI checks. Durable budgets, supervised execution, stop/recovery, immutable evidence, fixed-build regression and reports.
Good to know before installing
trusted Python controllers use the local Docker socket to manage exact run-owned containers; Docker targets get no host mounts, published ports or external network. Existing localhost servers are unmanaged and are tested only at origins the owner lists in `allowed_localhost_origins` (empty by default), which receive state-changing requests with the configured test-session headers. macOS supervised-local mode runs only executables the owner lists in `allowed_native_executables` (empty by default), under Seatbelt plus an RSS watchdog, not Docker isolation. Guided preparation reads the selected source and dependency trees and may fetch lockfile-verified Linux build packages from registry.npmjs.org. Guided assessments need a fresh one-shot human approval. Evidence stays in the selected profile's plugin data; no telemetry or model calls.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-pentest - Said no? Turn it on later:
hermes plugins enable hermes-pentest - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Security & privacy
- Maintained by
- WebisityStudio (Community)
- Needs
- No API keys declared
- Adds tools
pentest_inspectpentest_preparepentest_assesspentest_discoverpentest_preflightpentest_createpentest_executepentest_resumepentest_statuspentest_stoppentest_cleanuppentest_export- Adds hooks
pre_tool_callpre_approval_requestpost_approval_responsepost_tool_callagent_loop_stoppedon_session_end- Works on
- linux, macos
- Version
- 0.5.1
- In the catalog
- 2026-11-10
Known issues (from its catalog listing)
- Guided preparation currently supports Vite with an installed compatible npm cache and optional Supabase migrations. Other frameworks return setup gaps or require explicit adapters. Cached local toolchain images are required.
- Guided execution requires Hermes public tool-execution middleware and all six declared hooks; missing approval integration refuses execution. Approval is one-use and bound to the exact source, runtime, plan and budget.
- The v0.5.1 real-application follow-up completed all 15 selected checks: 10 data/Auth/browser contracts, 3 controlled SQL probes on a text preference-key filter and 2 same-user stored-XSS workflows. No confirmed vulnerabilities. Cross-user workflows: 0 planned, 0 completed. The earlier 3 rejected numeric-input SQL checks remain inconclusive; this follow-up does not relabel them or establish exhaustive coverage.
- Source hints require model verification of route reachability and positive controls. Authenticated stored-XSS viewer proof requires a real final-document Bearer GET /auth/v1/user with its Referer; missing proof remains inconclusive. No arbitrary auth-state injection.
- Localhost and supervised-local native targets are denied until the owner configures exact origins/executable paths in profile plugin settings. Plan acknowledgement flags do not grant permission. To revoke access, stop affected runs, end affected Hermes sessions, remove the entry, and start a new session. Managed sessions retain frozen settings; active attempts retain their bounded snapshot.
- Bounded check catalogue, not exhaustive vulnerability coverage. Native support exercises CLI/app-bundle executables, not GUI/mobile interactions.
- Managed web/Linux and browser checks require local Docker and prepared local images. Existing-localhost mode does not support HTTPS or interactive login/cookie rotation. Arbitrary Compose features are unsupported.
- Existing localhost cannot be isolated or independently source-pinned. Interrupted unmanaged assessments require owner reset/new run. macOS native memory uses an RSS watchdog, not a hard limit.
- MySQL/PostgreSQL timing has unit controls, but live dialect timing is unverified. PostgreSQL static dependency data flow is verified. SQLite and stacked MSSQL timing are explicitly skipped.
- The local acceptance harness imports version-sensitive Hermes discovery internals, producing a validation warning. Plugin runtime registration/storage and secret access use public APIs.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in security & privacy
All security & privacy plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher