Daily CVE exploitation alerts for your Slack security channel

Each weekday morning, check your CVE watchlist against live GreyNoise exploitation data and alert your Slack security channel only when it matters.

Agentic Task
GreyNoiseSlack BotEngineeringOperationsNotifications & AlertsResearch & Monitoring
PromptCreate

Every weekday at 8am, run an early-warning check on my CVE watchlist and post a prioritized exploitation summary to our security channel in Slack, but only on days when something on the watchlist is actually being exploited.

My watchlist is the set of CVEs that affect our stack and key vendors. Store the list of CVE IDs inside the workflow so I can maintain it over time. I will fill in the specific CVE IDs; treat that list as the input for each run. Post the alert into our security channel (I will specify the exact channel, for example #security).

Run a GreyNoise Bulk CVE Lookup across the entire watchlist in a single request to see which of those CVEs GreyNoise is currently observing under active internet exploitation, along with the exploitation trend and the number of attacking IPs it is seeing. For any CVE that looks notable, meaning it is actively exploited or its scanning and exploitation activity appears to be surging, call GreyNoise Retrieve CVE Information for that single CVE to pull the full timeline and observed exploitation detail so I can judge the trend and roughly how many IPs are involved.

Remember which watchlist CVEs were under active exploitation on the previous run. Flag any CVE that has newly crossed into active exploitation since the last run and lead the summary with those, since a fresh surge in activity often precedes wider attacks and new disclosures.

When at least one watchlist CVE is under active exploitation, post a prioritized summary to our security channel in Slack using the Slack Bot Send a Message action, posting as our automated bot rather than as a specific person. Order the summary by urgency and lead with anything newly exploited since the last run. For each flagged CVE include the exploitation trend (rising, steady, or declining), roughly how many attacking IPs GreyNoise is observing, and a one-line recommended action of patch now, monitor, or no action. Use Slack formatting so the message is easy to skim.

If nothing on the watchlist is under active exploitation that day, do not post to Slack at all. The channel should only light up when there is real exploitation activity worth acting on.

Example output

CVE exploitation alert: 2 watchlist CVEs under active exploitation New since the last check - CVE-2026-1234 (Acme VPN): exploitation rising sharply, ~180 attacking IPs observed. Recommended action: patch now. Ongoing - CVE-2025-9871 (CorePlatform): exploitation steady, ~40 attacking IPs. Recommended action: monitor. Everything else on the watchlist is quiet.

Additional information

What does this prompt do?
  • Checks your watchlist of known vulnerabilities (CVEs) against live GreyNoise data every weekday morning to see which are being actively exploited across the internet right now.
  • Leads with any CVE that just crossed into active exploitation since the last check, so the newest threats are front and center.
  • For each flagged CVE, tells you the exploitation trend, roughly how many attacking IPs GreyNoise is seeing, and a one-line recommended action: patch now, monitor, or no action.
  • Only posts to Slack when something on your watchlist is actually under attack, so your security channel stays quiet on calm days.
What do I need to use this?
  • A GreyNoise account with CVE lookup access (GreyNoise grants this to accounts registered with a business email address).
  • A Slack workspace and a security channel to post alerts into.
  • Your watchlist of CVEs that affect your stack and key vendors.
How can I customize it?
  • Change the schedule (for example run twice a day, or only on Mondays) and the time the check runs.
  • Edit your CVE watchlist as your stack and vendors change.
  • Pick which Slack channel gets the alerts and adjust what counts as worth flagging.

Frequently asked questions

What happens on days when nothing is being exploited?
Nothing gets posted. The workflow only messages your Slack channel when at least one CVE on your watchlist is showing active exploitation, so quiet days stay quiet.
How does it know which CVEs are newly exploited?
It remembers which CVEs were being exploited on the previous run and flags any that have newly crossed into active exploitation, leading the summary with those.
Where does the exploitation data come from?
GreyNoise, which observes internet-wide scanning and exploitation traffic. The workflow looks up your whole watchlist at once and pulls detailed timelines for anything notable.
Do I need a paid GreyNoise plan?
CVE lookups require GreyNoise's CVE-search access, which is granted to accounts registered with a business email address. A free personal email account will not have it.
Can it post as a shared bot instead of as me?
Yes. Alerts post to Slack through an automated bot into your chosen channel, so they are not tied to any one person's account.

Stop hunting through CVE feeds every morning.

Let an agent watch your CVE watchlist and ping your security channel only when something is actually being exploited.