Add a way to specify the chrome binary path

[B-i-t-K]

Right now it's not possible to specify the path of the chrome browser binary. There is the option -system-chrome but this can fail on some environment. Also it can be useful to be able to specify a specific chrome binary if multiple version of the browser are present on the OS.

I've already made a patch to add the feature on my repo, and I can do a pull request if you find the feature interesting.

I wanted to submit a pull request but the guideline ask to fill an issue first but I'm not allowed to create non-bug issue. So I'm posting it there instead.

Are you interested by this patch, and if yes, should I submit the pull request directly ?

[dwisiswant0]

but I'm not allowed to create non-bug issue

You can though.

[bad-antics]

Great idea — this is a common pain point for headless scanning in containerized environments and CI/CD pipelines.

Current workarounds until your PR is merged:

1. Symlink your chrome binary to where nuclei expects it:

# Find where nuclei looks for chrome
which google-chrome || which chromium-browser || which chromium

# Create symlink to your preferred binary
sudo ln -sf /path/to/your/chrome /usr/bin/google-chrome

2. Use the CHROME_PATH environment variable — some versions of the underlying go-rod/chromedp library respect this:

export CHROME_PATH=/opt/chrome/chrome-linux64/chrome
nuclei -u https://example.com -headless -t headless/

3. Use -system-chrome with PATH manipulation:

export PATH="/path/to/chrome/dir:$PATH"
nuclei -u https://example.com -headless -system-chrome

4. Docker approach — mount your chrome binary:

FROM projectdiscovery/nuclei:latest
COPY --from=chromedp/headless-shell:latest /headless-shell /usr/bin/google-chrome

I'd encourage you to open the PR — this is definitely a useful feature. The flag could be something like -chrome-path or -browser-path to stay consistent with the existing CLI style. Make sure to also update the types.Options struct so it works with the SDK as well.