What's New in HawkScan 6.x
HawkScan 6 ships as a native binary with Java bundled in. You do not need to install or manage a JDK or JRE on your machine or in your CI environment to run HawkScan.
This page shows the main changes in each 6.x release. For every change, including fixes, see the Changelog.
Highlights by Release
| Version | Highlights |
|---|---|
| 6.7 | Protection against Java4Shell (CVE-2026-114938). The install scripts install to ~/.local/bin and add hawk to your PATH. hawk op updates, including changes to hawk op repo link. |
| 6.6 | --sarif-ghas writes SARIF output that GitHub code scanning accepts. OpenAPI scans use the base path that your spec declares. A one-line install script for Windows. An unresolved ${VARIABLE} in your configuration now fails the scan. |
| 6.5 | sessionVerification checks that your scan is still logged in during the scan. See Authenticated Scanning. A one-line install script for macOS and Linux. Organization secrets resolve in your scan configuration. |
| 6.4 | --profile-scan-mode controls plugin coverage across authentication profiles. A new HTTP Header Authentication Bypass scan rule. hawk validate config exits non-zero when validation fails. |
| 6.3 | hawk rescan replays the requests that caused alerts, and does not crawl your app again. crashDetection stops a scan when the target application goes down. |
| 6.2 | hawk upgrade upgrades the CLI with one command. hawk skills status checks that your StackHawk agent skills are current. |
| 6.1 | hawk validate script tests authentication scripts against a live URL. |
| 6.0 | A standalone binary with Java bundled in, hawk op built in, OS-native certificate trust, and hawk init --browser. See the sections below. |
Standalone Binary, No Java Required
On first run, hawk extracts a trimmed Java runtime and its supporting libraries into ~/.hawk/bin/. Later runs go straight to the scan. Extraction occurs again only when you upgrade to a new version. The bundled runtime is self-contained and does not interfere with a JDK that you installed.
No Java prerequisite. Put hawk on any machine or pipeline and run it. You do not need to set JAVA_HOME or check java -version.
Simpler CI/CD. Remove the Java installation steps from your GitHub Actions, GitLab CI, or other pipeline configurations. The hawk binary is the only thing that you need.
Same install paths, same commands. Homebrew (brew install stackhawk/cli/hawk), the macOS PKG, the Windows MSI, the install scripts, and direct binary downloads all deliver the same self-contained executable. The way that you run hawk does not change.
Docker works the same way. The Docker container (stackhawk/hawkscan) continues to work as before. The image build installs the Java runtime into ~/.hawk/bin/, so the container works the same as a local install.
hawk op is built in. Before 6.0.0, StackHawk platform operations needed a separate hawkop binary. Now hawk op is part of hawk. It runs in the Rust layer, so it starts immediately and does not wait for the Java runtime.
OS-Native Certificate Trust
HawkScan trusts the certificate store of your operating system on every platform. Thus it works behind transparent TLS-intercepting proxies, such as Zscaler, Netskope, and corporate CAs, with no manual configuration.
The launcher reads the OS root certificates and adds them to the trust bundle of the scanner. Your JDK truststore stays the same, and the OS roots are added to it. If your browser trusts a certificate, hawk also trusts it.
| Platform | Certificate source |
|---|---|
| macOS | Security.framework (system and user keychains) |
| Windows | Windows Certificate Store (CryptoAPI) |
| Linux | System PEM bundle (e.g. /etc/ssl/certs/ca-certificates.crt) |
This feature is enabled by default. To disable it and use only the bundled roots:
hawk scan --no-native-truststore
# or
USE_NATIVE_TRUSTSTORE=false hawk scan hawk scan --no-native-truststore
# or
$env:USE_NATIVE_TRUSTSTORE = "false"; hawk scan For proxies that need explicit configuration (username and password, NTLM, or a specific CA certificate file), see Outbound Proxy Config Options in the CLI reference.
Non-Interactive Auth: hawk init --browser
hawk init --browser does device-flow authentication with no interactive prompts. It skips the existing-key confirmation and the login menu. It opens the browser immediately. It always prints the authentication URL to stdout, so agents can capture the URL and show it.
hawk init --browser
# Open this URL to authenticate:
# https://auth.stackhawk.com/activate?user_code=XXXX-XXXX
Without --browser, the interactive prompt does not change. It asks if you want to log in with the browser or enter a key manually.
ZIP Distribution Removed
The hawk-{version}.zip download is no longer a distribution format. If your pipelines or scripts download the ZIP directly, use the binary for your OS and architecture:
| Platform | Architecture | Binary |
|---|---|---|
| macOS | Apple Silicon (arm64) | darwin-arm64/hawk |
| macOS | Intel (x64) | darwin-x64/hawk |
| Linux | x86_64 | linux-x64/hawk |
| Linux | arm64 | linux-aarch64/hawk |
| Windows | x64 | windows-x64/hawk.exe |
| Windows | arm64 | windows-arm64/hawk.exe |
Binaries are available at https://download.stackhawk.com/hawk/{VERSION}/{PLATFORM}/hawk (Windows: hawk.exe). Use the platform identifiers from the table above for {PLATFORM}.
CI/CD users: The hawkscan-action v3 and the updated Azure DevOps extension download the binary for you. You do not need manual curl commands.