Alerts

How to receive CVE alerts by webhook in your system and verify the signature (HMAC)

Get your stack's CVEs in a JSON POST signed with HMAC-SHA256, straight into the SIEM, SOAR or ticketing system, with the same identifier on every attempt so nothing is processed twice.

  • Who it's forFor developers, SOCs and MSSPs bringing alerts into their own system.
  • PlanSOC and MSSP plans
  • Timeabout 20 min

What you need

  • A Vexday account on the SOC or MSSP plan with technologies added under Alerts.
  • A public https address in your system, on port 443 or 8443, that accepts JSON POSTs.

Step by step

  1. Register the endpoint

    Under Alerts, in the Destinations section, pick JSON endpoint, paste your system's URL and click Register. An internal network address, a private IP or a port other than 443 and 8443 is refused.

  2. Store the secret

    On the endpoint card, click Show and copy the secret into your system. You use it to verify the signature; Generate a new secret invalidates the old one immediately.

  3. Verify the signature

    Each POST carries the X-Vexday-Signature header. Recompute the HMAC-SHA256 of "t.body" with the secret, over the raw body bytes, before parsing the JSON, compare in constant time and reject a t more than five minutes off.

    X-Vexday-Event: cve.alerts
    X-Vexday-Delivery: 4bf933c7-c07a-4a45-a1b0-8729d2eebc8e
    X-Vexday-Signature: t=1762178700,v1=<HMAC-SHA256 hex>
    The verification code in Python and Node, with the JSON example →
  4. Answer fast and skip repeats

    Answer with a 2xx code as soon as it arrives and process it afterwards. X-Vexday-Delivery is the same on every attempt: skip a delivery you already processed. Without a 2xx, Vexday retries over a few hours, and a 410 turns the endpoint off.

  5. Test it

    Click Test: the endpoint gets a signed ping event, and the dashboard shows what it answered and how fast. Deliveries keeps the history of every attempt.

Something went wrong?

The URL is not acceptedUse https, port 443 or 8443, a public address and no username or password in the URL. Internal networks and private IPs are refused to protect both sides.
The signature does not matchCompute over the raw body bytes, before any JSON parsing, and use that endpoint's secret (each one has its own). Check the server clock too: a t more than five minutes off is rejected.
The endpoint was turned offThree days of nothing but failures turn the endpoint off, and the owner gets an email; a 410 turns it off immediately. Fix the receiver and click Turn back on.
The same alert arrived twiceIt is a retry, with the same X-Vexday-Delivery. Keep the identifiers you already processed and skip repeats.

Frequently asked questions

Which events arrive?

cve.alerts, with the CVEs sent right away; cve.digest, the daily digest; and ping, the test. The type comes in the body and in the X-Vexday-Event header.

Can the JSON change?

The body carries the format version (api_version), and new fields arrive without changing it. Your receiver should ignore fields it does not know.

Can I send the alerts to Jira?

Yes. The n8n guide has a ready-made workflow that checks the signature and keeps one ticket per CVE and client.

Keep going