Actions181
- Account Actions
- Accounts Actions
- App Block Actions
- Assets Actions
- Content Filtering Actions
- Create Content Filtering Rule
- Create Update DNS Settings
- Delete Content Filtering Rule
- Enable Disable Content Filtering Rule
- Enable Disable Content Filtering Rule For Policy
- Get A Content Filtering Rule Details
- Get A List Of Content Filtering Rules
- Get DNS Settings
- Get Domain Details
- Get Frequently Used Domain Names
- Get List Of Policies
- Update Content Filtering Rule
- CVE Actions
- Detections Actions
- Device Control Actions
- DNS Actions
- Endpoints Actions
- All Suspicious Activity Of An Endpoint
- Close Suspicious Activity Of An Endpoint
- Delete A Machine
- Delete Multiple Machines
- Endpoint Status
- Export Endpoints
- Get A Scan Of An Endpoint
- Get Endpoint
- Get Endpoint Agent Info
- Get Endpoint Assets
- Get Quarantined Items
- Get Scans Of An Endpoint
- Get The Detections Of A Scan
- Network Information
- Open Suspicious Activity Of An Endpoint
- Remediate Suspicious Activity Of An Endpoint
- Search Endpoints
- Search Grouped Endpoints
- Set Endpoint Tags
- Specific Suspicious Activity Of An Endpoint
- Events Actions
- Exclusions Actions
- Flight Recorder Actions
- Grid Actions
- Export CVEs
- Export Detections
- Export Device Control Events
- Export DNS Activity
- Export Endpoints
- Export Events
- Export OS Patches
- Export RID Rules
- Export Software Assets
- Search CVEs
- Search Detections
- Search Device Control Events
- Search DNS Activity
- Search Endpoints
- Search Events
- Search Events Groupby
- Search Grouped CVEs
- Search Grouped Detections
- Search Grouped Device Control Events
- Search Grouped DNS Activity
- Search Grouped Endpoints
- Search Grouped OS Patches
- Search Grouped RID Rules
- Search Grouped Software Assets
- Search OS Patches
- Search RID Rules
- Search Software Assets
- Groups Actions
- Installation Token Actions
- Installers Actions
- Jobs Actions
- Notifications Actions
- OS Patches Actions
- Policies Actions
- Products Actions
- Quarantine Actions
- Reports Actions
- RID Actions
- SA Actions
- Schedules Actions
- Usage Actions
- Users Actions
- Webhooks Actions
CVE → Search CVE
AI-generatedSummary
Searches CVE (vulnerability) records in Threatdown (Malwarebytes) by sending a POST request whose JSON body is built from filter fields and optional raw JSON. Returns matching vulnerabilities, with paging and sorting controlled through the body.
Inputs
- Body Fields (op29_bodyFields) — Collection of optional filters added to the request body. Covers CVE ID, vendor/product/version (raw, display and normalized forms), severity and severity score ranges, CVSS 2.0 and 3.0 score comparisons (eq/gt/gte/lt/lte), CISA exploitable flag, published/created/installation date ranges (after/before), host, machine, account, group and OS info fields, plus
not.*exclusion variants. Many fields also have a.keywordexact-match variant. Also holds page_size (default 50), next_cursor for pagination, sort_field and sort_order, and name_multi_search. - Additional JSON Body (op29_body) — Raw JSON object merged with the Body Fields values. It can supply any request body property not exposed in the UI. The source suggests it takes precedence over Body Fields on conflicts, but this is not confirmed because the pack shows only function signatures.
Output shape
Items produced from the API response, which the node normalizes into n8n items. This is expected to be the matching CVE records, likely a list.
Results are paged: use page_size and next_cursor in the body to fetch further pages. The exact response envelope is not visible in the provided source, which contains only function signatures. Note that the property metadata lists the operation value as
postCve.
Examples
Example 1: Find critical vulnerabilities that CISA marks as exploitable
Body Fields: Cisa Exploitable = true, Severity = Critical, Page Size = 100.
Example 2: List high-CVSS vulnerabilities for a specific product
Body Fields: Normalized Product = chrome, Cvss30 Score Gte = 7.0, Sort Field/Order set as desired.
Example 3: Fetch the next page of results
Reuse the previous filters and set Next Cursor to the cursor value from the previous response, or pass it via Additional JSON Body.