Automated CVE scanning of Bug Bounty programs with Nuclei and Project Discovery

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Description Automates daily CVE driven scanning against bug bounty scopes. It fetches bug bounty domains, pulls newly published Project Discovery templates, converts them to Nuclei rules, runs targ...

Best for

SecOps automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.converttofile, n8n-nodes-base.ssh, n8n-nodes-base.splitinbatches, n8n-nodes-base.splitout, n8n-nodes-base.filter, n8n-nodes-base.if

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Javier Rieiro.

Original n8n.io source

1.1 Workflow description

Title: Automated CVE scanning of Bug Bounty programs with Nuclei and Project Discovery
Workflow name: Automated CVE scanning of Bug Bounty programs with Nuclei and Project Discovery

Description

Automates daily CVE-driven scanning against bug bounty scopes. It fetches bug-bounty domains, pulls newly published Project Discovery templates, converts them to Nuclei rules, runs targeted scans, and emails findings.

Objective

Help security researchers and bug bounty hunters discover exploitable instances quickly by automatically running the latest public templates from Project Discovery against a consolidated bug-bounty scope. Reduce manual steps and maintain continuous reconnaissance.

How it works

The workflow accepts or fetches a domain list that covers HackerOne, Bugcrowd, Intigriti, and YesWeHack.
It downloads the latest public templates from Project Discovery.
For each new template published since the last run it: creates a file, uploads it to a remote host, and converts it to a Nuclei-compatible YAML.
It uploads a consolidated domains wordlist to the remote host.
It executes Nuclei with the new templates against the domains list using configured flags (concurrency, rate limits, severity tags).
It collects and deduplicates Nuclei output.
If results exist, it sends the findings via Gmail.

Requirements

• SSH access (root or equivalent) to a VPS or host. • Nuclei installed on the remote host. • Gmail OAuth2 credentials for sending notifications. • Recommended: VPS with enough CPU and network capacity for concurrent scanning when scope is large.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.2

Block 2 - Get All Bug Bounty Domains

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 3 - Create domains.txt

Type / Role: n8n-nodes-base.convertToFile - convertToFile
Config choices: Version 1.1

Block 4 - Upload domains.txt

Type / Role: n8n-nodes-base.ssh - ssh
Config choices: Version 1

Block 5 - Loop Over CVEs

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 6 - Split CVEs

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 7 - GET Last CVEs (PROJECT DISCOVERY)

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 8 - Template Exists Filter

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.2

Block 9 - Date Filter

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 10 - Set Variables

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 11 - Set Null Variable

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 12 - Loop Over Templates

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 13 - Create Template

Type / Role: n8n-nodes-base.convertToFile - convertToFile
Config choices: Version 1.1

Block 14 - Upload Template

Type / Role: n8n-nodes-base.ssh - ssh
Config choices: Version 1

Block 15 - Convert Template to .yaml

Type / Role: n8n-nodes-base.ssh - ssh
Config choices: Version 1

Block 16 - Execute Nuclei

Type / Role: n8n-nodes-base.ssh - ssh
Config choices: Version 1

Block 17 - Remove Templates

Type / Role: n8n-nodes-base.ssh - ssh
Config choices: Version 1

Block 18 - Set Results Variable

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 19 - Check Results

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 20 - Send a message

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.1

Block 21 - Remove Items

Type / Role: n8n-nodes-base.summarize - summarize
Config choices: Version 1.1

Block 22 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 23 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 32 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Automated CVE scanning of Bug Bounty programs with Nuclei and Project Discovery
Complexity	advanced
Nodes	32
Categories	SecOps
Author	Javier Rieiro
Published	22 Oct 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/10054/10054.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source SecOps workflows

Frequently asked questions

What does Automated CVE scanning of Bug Bounty programs with Nuclei and Project Discovery do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your SecOps use case.

Javier Rieiro

4 workflows

Nodes

n8n-nodes-base.scheduletrigger n8n-nodes-base.httprequest n8n-nodes-base.converttofile n8n-nodes-base.ssh n8n-nodes-base.splitinbatches n8n-nodes-base.splitout n8n-nodes-base.filter n8n-nodes-base.if

Complexity

advanced

Published 22 Oct 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/10054/10054.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Generate incident response reports with Supabase, Gemini and Claude

## Quick Overview This workflow ingests incident and playbook content from GitHub into Supabase (including pgvector embeddings with Google Gemini) and, on a webhook trigger, enriches a test incident with historical matches, a routed response playbook, and live web threat intel (via Tavily + OpenRouter) to generate a validated incident response report. ## How it works 1. Receives a POST webhook containing the incident payload (including an encrypted OpenRouter API key) and decrypts the key for downstream LLM calls. 2. Creates a tracking row in a Supabase table and loads configuration values used by the retrieval and report-generation steps. 3. Retrieves similar resolved incidents from a Supabase pgvector store using Google Gemini embeddings and returns structured historical patterns. 4. Retrieves the best-matching reference playbook from a Supabase pgvector store and fetches the full playbook text from Supabase, falling back to a built-in generic playbook when no match is found. 5. Uses Tavily Search plus an OpenRouter-backed agent to gather external threat intelligence, IOCs, and phased mitigation guidance when the incident is classified as security-relevant. 6. Merges the three intelligence branches and uses an OpenRouter LLM to synthesize a structured JSON output and an 11-section Markdown incident response report. 7. Validates that required report fields exist and, if valid, writes the structured output and Markdown report back to the Supabase test incident record; otherwise it skips the write. ## Setup 1. Create Supabase tables for test incidents and vector stores (for resolved incidents and reference playbooks) and configure the matching SQL functions used for retrieval (for example, `match_resolved_incidents_v1` and `match_reference_playbooks_v1`). 2. Add Supabase credentials in n8n and set the correct table names and query function names in the workflow’s configuration nodes. 3. Add Google Gemini (PaLM) API credentials and ensure the embedding model name used in the config (for example, `models/gemini-embedding-001`) is available to your account. 4. Add an OpenRouter API credential for the chat models used by the agents and synthesizer, and ensure your webhook caller sends an `encrypted_openrouter_key` value that matches the workflow’s decryption format. 5. Add a Tavily API credential for web search, then copy the webhook URL and configure your incident source to POST the incident JSON to it.

View

Check JWT security of API endpoints with HTTP requests and Google Sheets

## Quick Overview This workflow reads API endpoints and JWTs from Google Sheets, tests each endpoint with multiple token scenarios using HTTP requests, and writes a risk-scored security summary back to Google Sheets. ## How it works 1. Triggers manually (or on an optional daily schedule). 2. Loads the target Google Sheets document ID and the endpoint/results tab names. 3. Reads endpoint definitions from Google Sheets and keeps only rows marked as active. 4. For each endpoint, decodes the provided JWT and generates test variants (no auth, tampered payload, and alg:none). 5. Sends HTTP requests to the endpoint using the valid token and, if that succeeds, repeats the request with each test token variant and captures the response status codes. 6. Evaluates the status codes and token metadata to flag issues (for example, unauthenticated access, tampered token acceptance, alg:none acceptance, or missing exp) and assigns a risk level. 7. Appends the timestamped results and summary to the results tab in Google Sheets. ## Setup 1. Create a Google Sheet with an endpoints tab containing columns like `label`, `endpoint_url`, `method`, `token`, and `active`, and a results tab with columns like `timestamp`, `label`, `risk_level`, `t1_valid`, `t2_no_auth`, `t3_tampered`, `t4_alg_none`, and `summary`. 2. Add a Google Sheets Service Account credential in n8n and share the spreadsheet with the service account email. 3. Update the Sheet ID and tab names in the workflow’s variables (Sheet ID, endpoints sheet name, and results sheet name). 4. Ensure each endpoint row includes a valid JWT in the `token` column and set `active` to TRUE for endpoints you want to test. 5. If you want it to run automatically, enable the schedule trigger and adjust the cron expression as needed.

View

Monitor SSL certificate expiry with Google Sheets, Slack, Gmail and Jira

## Quick Overview This workflow runs daily to check SSL certificate expiry for domains listed in Google Sheets, using ssl-checker.io to fetch certificate details, then creating Jira issues and sending Slack and Gmail alerts for risky certificates while logging results and posting a daily Slack digest. ## How it works 1. Runs every day at 08:00 on a schedule trigger. 2. Reads the domain list from a Google Sheets “Domains” sheet and filters out blank rows or domains marked as disabled. 3. Processes domains one by one, calling the ssl-checker.io API to retrieve each site’s live SSL certificate details. 4. Calculates days remaining until expiry, assigns a status (Expired, Critical, Warning, Healthy, or Unknown), and flags items that require attention. 5. For certificates that need attention, creates a Jira task and sends an alert to Slack and an email via Gmail with the certificate details. 6. For healthy certificates, writes the latest check results to a Google Sheets “Log” sheet. 7. Aggregates all results from the run into a single summary message and posts the daily digest to Slack. ## Setup 1. Create a Google Sheet with a “Domains” sheet containing at least a `domain` column (and optionally an `enabled` column) and a “Log” sheet to store results, then add your Google Sheets credentials and set the spreadsheet ID. 2. Add an API key for ssl-checker.io (or a compatible SSL lookup endpoint) and place it in the HTTP Authorization header. 3. Add your Jira credentials and set the target project key for ticket creation. 4. Add your Slack credentials and set the channel ID used for alerts and the daily digest. 5. Add your Gmail credentials and set the recipient address for email alerts. 6. (Optional) Adjust the warning and critical thresholds (30 and 7 days) in the expiry calculation code if your policy differs.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Automated CVE scanning of Bug Bounty programs with Nuclei and Project Discovery

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Description

Objective

How it works

Requirements

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Block 2 - Get All Bug Bounty Domains

Block 3 - Create domains.txt

Block 4 - Upload domains.txt

Block 5 - Loop Over CVEs

Block 6 - Split CVEs

Block 7 - GET Last CVEs (PROJECT DISCOVERY)

Block 8 - Template Exists Filter

Block 9 - Date Filter

Block 10 - Set Variables

Block 11 - Set Null Variable

Block 12 - Loop Over Templates

Block 13 - Create Template

Block 14 - Upload Template

Block 15 - Convert Template to .yaml

Block 16 - Execute Nuclei

Block 17 - Remove Templates

Block 18 - Set Results Variable

Block 19 - Check Results

Block 20 - Send a message

Block 21 - Remove Items

Block 22 - Sticky Note

Block 23 - Sticky Note1

Block 24 - Sticky Note2

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions