Search
Ctrl+K
Usability
5
Automation
3
Security
4
Infrastructure
4
On this page
Documentation for triaging vulnerabilities, looking up CVE/GHSA advisories, tracking affected hosts and packages, and automating remediation workflows in Shuffle Security.
Shuffle Security (shuffle.security/vulnerabilities) helps you discover, prioritize, and remediate vulnerabilities across your endpoints, cloud infrastructure, user identities, and code dependencies.
Instead of tracking scanner exports in static spreadsheets, you can see exactly which hosts and file paths are affected by a CVE, track per-host patching status, look up live advisories, and trigger automated remediation playbooks.
Software / CVE, User / Identity, Cloud Misconfig, Code / Deps), severity, and remediation status at /vulnerabilities.package.json, requirements.txt, Cargo.toml, go.mod), linking advisories to exact hostnames and filesystem paths.Patched, Mitigated, Accepted, False Positive, or Not Applicable.NoteZero License Paywalls
Vulnerabilities is included in both Shuffle Cloud and self-hosted open-source instances with no per-seat or per-asset license fees. App runs only execute when your automation workflows trigger.
Navigate to /vulnerabilities to view and triage findings across your organization:
All, Software / CVE, User / Identity, Cloud Misconfig, and Code / Deps.Critical, High, Medium, Low, or Info.Open, In Progress, Resolved, or Accepted findings.Critical, High, Medium, Low, Info) and CVSS score.CVE-2024-3094) with a summary headline.software_cve, code_dependency, user_identity, cloud_misconfig).osv:npm, osv:pypi, host monitor, or external scanner).Open, In Progress, Resolved, Accepted)./vulnerabilities/:id)Clicking any finding opens its detail page at /vulnerabilities/:id, where you can:
Shuffle provides multiple ways to look up advisories and bring vulnerability findings into your queue:
Use the lookup bar above, or enter any CVE ID (e.g. CVE-2024-3094), GitHub Security Advisory ID (e.g. GHSA-xxxx-xxxx-xxxx), or package name into the search bar at /vulnerabilities:
https://api.osv.dev/v1/vulns/<id>) in real time to display advisory details, severity, affected version ranges, and fixed versions—even if the CVE has not been ingested into your tenant yet.When endpoints run Shuffle Host Monitors with Installed Software or Code Package Scanner enabled:
package.json, requirements.txt, Cargo.toml, go.mod)./vulnerabilities with the affected hostname and file path./packages/<name> or software binary at /software/<name> and click Sync to Vulnerabilities to persist affected advisories.Push findings from CI/CD pipelines, container scanners (Trivy, Grype), or external vulnerability tools directly into Shuffle:
/vulnerabilities and click the Webhook button in the top header bar.Code
Editable
Response
vulnerabilities_webhook workflow and normalize findings into your queue.Connect vulnerability scanners (such as Snyk, Qualys, Tenable, or Rapid7) using the source icons in the /vulnerabilities header bar. Scheduled workflows (such as Ingest Vulnerabilities) pull findings on a regular cadence, deduplicate advisories, and update affected hosts.
Shuffle organizes findings into four categories so you can filter by remediation owner (SecOps, IT/Endpoint, Cloud Engineering, or Application Developers):
| Category | Identifier Key | Scope & Typical Sources |
|---|---|---|
| Software / CVE | software_cve | Operating system packages, installed desktop applications, and server binaries. |
| User / Identity | user_identity | IAM drift, missing MFA, stale credentials, and excessive privileges. |
| Cloud Misconfig | cloud_misconfig | Open storage buckets, permissive firewall rules, and cloud infrastructure drift. |
| Code / Dependencies | code_dependency | Third-party packages and libraries scanned from code repositories (package.json, requirements.txt, Cargo.toml, go.mod). |
A vulnerability finding is much easier to remediate when you know exactly which machines and repositories are affected.
When Host Monitors or asset scans detect a vulnerable package, Shuffle links the finding to each affected host:
/home/user/projects/web-api/package.json or /usr/lib/x86_64-linux-gnu/liblzma.so.5.6.0).Because a vulnerability may affect dozens of machines that get patched at different times, you can update the resolution status individually for each host inside /vulnerabilities/:id:
| Resolution Reason | Meaning |
|---|---|
| Patched | The dependency or software package on this host has been upgraded to a non-vulnerable version. |
| Mitigated | Compensating controls (such as network ACLs or disabled features) neutralize the flaw on this host. |
| Accepted | Risk is formally accepted for this host. |
| False Positive | The detected package is not exploitable in this specific environment. |
| Not Applicable | The vulnerable function or subcomponent is not used on this host. |
Shuffle Security verifies whether your core vulnerability ingestion, correlation, and response workflows are active:
| Readiness Pillar | Verification Check | Target Workflow | Status | Purpose & Configuration |
|---|---|---|---|---|
| Vulnerability Webhook | Inbound webhook trigger running | vulnerabilities_webhook | Active | Ingests findings pushed from external scanners. Configure at /vulnerabilities -> Webhook. |
| Vulnerability Ingestion | Schedule trigger running | Ingest Vulnerabilities | Active | Regularly polls external vulnerability APIs on a recurring schedule. Activate in /usecases. |
| Vulnerability Correlation | Workflow exists with actions | Vulnerability Correlation | Active | Compares scanner results across runs and correlates findings with assets. Activate in /usecases. |
| Vulnerability Response | Automated remediation | asset_management_case_management_vuln_response_1 | In Development | Automated remediation, ticketing, and containment actions for detected vulnerabilities (coming soon). |
Code
Editable
Response
TipEnabling Automations
Click Enable all on the readiness banner at/vulnerabilities(or click the rocket button in the/vulnerabilitiesheader bar) to configure automatic ingestion and response workflows.
Under the hood, all vulnerability findings are stored in Shuffle's Datastore under the shuffle-security_vulns category. Each entry is keyed by its primary advisory identifier (e.g. CVE-2024-3094 or GHSA-7867-xwm8-2v3q) and stores a structured JSON document.
You can inspect, query, and modify raw records in the Datastore console:
/admin/datastore?category=shuffle-security_vulns. Queries the local datastore if configured, and falls back to Shuffle Core if local storage is not initialized.https://shuffler.io/admin?tab=datastore&category=shuffle-security_vulns or /admin?tab=datastore&category=shuffle-security_vulns on self-hosted instances).shuffle-security_vulns.In day-to-day triage at /vulnerabilities, findings are resolved, mitigated, or accepted rather than deleted so your audit history stays intact.
If a scanner misbehaved or a test script ingested dummy CVEs that need to be permanently removed, an admin (isAdmin) can delete them in the Datastore:
/admin/datastore?category=shuffle-security_vulns.CVE-2024-3094).| Field | Type | Description |
|---|---|---|
id | String | Canonical advisory identifier (e.g. CVE-2024-3094, GHSA-xxxx). Serves as the primary datastore key. |
title | String | Descriptive title or headline of the vulnerability. |
severity | String | Severity rating: critical, high, medium, or low. |
score | Number | CVSS base numerical score (e.g. 10.0 or 7.4). |
category | String | Classification: software_cve, code_dependency, user_identity, or cloud_misconfig. |
status | String | Workflow status: open, in_progress, mitigated, accepted, or resolved. |
affected_package | String | Name and version constraint of the affected component (e.g. xz-utils 5.6.0, lodash <4.17.21). |
fixed_version | String | Minimum version containing the remediation patch (e.g. 5.6.1). |
affected_hosts | Array | Endpoints running the vulnerable software or dependency, including hostname, filesystem path, and per-host resolution. |
Python
Editable
Response
All vulnerability records stored in shuffle-security_vulns are versioned with immutable revisions. Every scanner sweep, automated triage run, or manual status change preserves historical snapshots:
API Call
Response
No response received.
Python
Editable
Response
GET /api/v1/vulnerabilitiesGET /api/v1/vulnerabilities/{id}API Call
Response
No response received.
API Call
Response
No response received.
Python
Editable
Response
For more details on backend API endpoints and datastore caching rules, see the API documentation.