Shuffle
Security
Features
Usecases
Docs
Sign InGet Started

Search

Ctrl+K

Usability

5

  • Getting Started
  • About Shuffle
  • Tenants & Multi-Tenancy
  • Features Overview
  • API Reference

Automation

3

Security

4

Infrastructure

4

Vulnerabilities in Shuffle Security

7 min read
ayush0033
frikky
Edit on GitHub
7m to read

On this page

Overview
Using the Vulnerabilities dashboard
Navigation & Filtering
Table Columns
Vulnerability Detail View (/vulnerabilities/:id)
Looking up & ingesting vulnerabilities
1. Live OSV.dev Advisory Lookup
2. Host Monitor Code & Software Scanner
3. Inbound Webhook (Push from CI/CD & Scanners)
4. Polling Scanners (Scheduled Pull)
Vulnerability categories
Host & package correlation
Per-Host Resolution Status
Automating vulnerability management
Vulnerability Use Cases
Datastore architecture & finding schema
Deleting Erroneously Ingested Vulnerabilities (Admin Only)
Vulnerability Record Schema
Writing Findings in Python Apps & Workflows
Key Revisions, Audit Trail & Rollback Protection
API & Datastore reference
REST API Endpoints
In Custom Python Apps & Workflows

Documentation for triaging vulnerabilities, looking up CVE/GHSA advisories, tracking affected hosts and packages, and automating remediation workflows in Shuffle Security.

Overview

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.

  • Unified Vulnerability Queue: Filter findings by category (Software / CVE, User / Identity, Cloud Misconfig, Code / Deps), severity, and remediation status at /vulnerabilities.
  • Live OSV.dev Advisory Lookup: Search any CVE, GHSA, or open-source package name (npm, PyPI, Go, Cargo, Maven, Debian, Alpine) to inspect affected versions and published fixes immediately.
  • Host & Package Correlation: Endpoints running Host Monitors scan installed software and local code manifests (package.json, requirements.txt, Cargo.toml, go.mod), linking advisories to exact hostnames and filesystem paths.
  • Per-Host Resolution Tracking: Mark vulnerabilities individually per host as Patched, Mitigated, Accepted, False Positive, or Not Applicable.
  • Workflow Automation: Automatically ingest scanner results, notify engineering teams in Slack/Teams, open Jira tickets, or escalate critical unpatched flaws into Incidents.
Note

Zero 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.


Using the Vulnerabilities dashboard

Navigate to /vulnerabilities to view and triage findings across your organization:

Navigation & Filtering

  • Category Tabs: Switch between All, Software / CVE, User / Identity, Cloud Misconfig, and Code / Deps.
  • Severity Filter: Filter by Critical, High, Medium, Low, or Info.
  • Status Filter: View Open, In Progress, Resolved, or Accepted findings.
  • Search Bar: Search by CVE/GHSA identifier, affected package name, hostname, or keyword.

Table Columns

  • Severity: Normalized severity rating (Critical, High, Medium, Low, Info) and CVSS score.
  • Identifier / Title: Advisory identifier (e.g. CVE-2024-3094) with a summary headline.
  • Category: Classification badge (software_cve, code_dependency, user_identity, cloud_misconfig).
  • Source: Discovery origin (e.g. osv:npm, osv:pypi, host monitor, or external scanner).
  • Status: Current lifecycle state (Open, In Progress, Resolved, Accepted).
  • First Seen: Timestamp when the finding was first detected.

Vulnerability Detail View (/vulnerabilities/:id)

Clicking any finding opens its detail page at /vulnerabilities/:id, where you can:

  • Read the full advisory description, CVSS score, published/modified dates, and upstream references.
  • Inspect affected package ecosystems, vulnerable version ranges, and the minimum fixed version.
  • View every affected host along with the exact filesystem path where the package was found.
  • Update the overall status or set a per-host resolution status.
  • Ask the inline AI assistant questions about exploitability, remediation steps, or upgrade impact.

Looking up & ingesting vulnerabilities

Shuffle provides multiple ways to look up advisories and bring vulnerability findings into your queue:

1. Live OSV.dev Advisory Lookup

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:

  • Shuffle queries OSV.dev (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.

2. Host Monitor Code & Software Scanner

When endpoints run Shuffle Host Monitors with Installed Software or Code Package Scanner enabled:

  • The monitor agent catalogs installed OS applications and scans local project directories for manifest files (package.json, requirements.txt, Cargo.toml, go.mod).
  • Discovered packages and versions are evaluated against OSV.dev and synced directly into /vulnerabilities with the affected hostname and file path.
  • You can also browse any discovered package at /packages/<name> or software binary at /software/<name> and click Sync to Vulnerabilities to persist affected advisories.

3. Inbound Webhook (Push from CI/CD & Scanners)

Push findings from CI/CD pipelines, container scanners (Trivy, Grype), or external vulnerability tools directly into Shuffle:

  • Navigate to /vulnerabilities and click the Webhook button in the top header bar.
  • Copy your inbound webhook endpoint:

    Code

    Editable

    Response

  • Send scanner JSON payloads to this URL to trigger the vulnerabilities_webhook workflow and normalize findings into your queue.

4. Polling Scanners (Scheduled Pull)

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.


Vulnerability categories

Shuffle organizes findings into four categories so you can filter by remediation owner (SecOps, IT/Endpoint, Cloud Engineering, or Application Developers):

CategoryIdentifier KeyScope & Typical Sources
Software / CVEsoftware_cveOperating system packages, installed desktop applications, and server binaries.
User / Identityuser_identityIAM drift, missing MFA, stale credentials, and excessive privileges.
Cloud Misconfigcloud_misconfigOpen storage buckets, permissive firewall rules, and cloud infrastructure drift.
Code / Dependenciescode_dependencyThird-party packages and libraries scanned from code repositories (package.json, requirements.txt, Cargo.toml, go.mod).

Host & package correlation

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:

  • Hostname & Asset ID: Identifies the exact endpoint or server running the vulnerable software or dependency.
  • Filesystem Paths: Shows the exact path where the binary or manifest was found (e.g. /home/user/projects/web-api/package.json or /usr/lib/x86_64-linux-gnu/liblzma.so.5.6.0).
  • Installed vs. Fixed Version: Compares the currently installed version on the host against the minimum patched version from the advisory.

Per-Host Resolution Status

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 ReasonMeaning
PatchedThe dependency or software package on this host has been upgraded to a non-vulnerable version.
MitigatedCompensating controls (such as network ACLs or disabled features) neutralize the flaw on this host.
AcceptedRisk is formally accepted for this host.
False PositiveThe detected package is not exploitable in this specific environment.
Not ApplicableThe vulnerable function or subcomponent is not used on this host.

Automating vulnerability management

Shuffle Security verifies whether your core vulnerability ingestion, correlation, and response workflows are active:

Readiness PillarVerification CheckTarget WorkflowStatusPurpose & Configuration
Vulnerability WebhookInbound webhook trigger runningvulnerabilities_webhookActiveIngests findings pushed from external scanners. Configure at /vulnerabilities -> Webhook.
Vulnerability IngestionSchedule trigger runningIngest VulnerabilitiesActiveRegularly polls external vulnerability APIs on a recurring schedule. Activate in /usecases.
Vulnerability CorrelationWorkflow exists with actionsVulnerability CorrelationActiveCompares scanner results across runs and correlates findings with assets. Activate in /usecases.
Vulnerability ResponseAutomated remediationasset_management_case_management_vuln_response_1In DevelopmentAutomated remediation, ticketing, and containment actions for detected vulnerabilities (coming soon).

Code

Editable

Response

Tip

Enabling Automations
Click Enable all on the readiness banner at /vulnerabilities (or click the rocket button in the /vulnerabilities header bar) to configure automatic ingestion and response workflows.

Vulnerability Use Cases


Datastore architecture & finding schema

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:

  • Shuffle Security Datastore: Navigate to /admin/datastore?category=shuffle-security_vulns. Queries the local datastore if configured, and falls back to Shuffle Core if local storage is not initialized.
  • Shuffle Datastore: Open in Shuffle Datastore (https://shuffler.io/admin?tab=datastore&category=shuffle-security_vulns or /admin?tab=datastore&category=shuffle-security_vulns on self-hosted instances).
  • Manual UI Navigation: Go to Admin -> Datastore -> select category shuffle-security_vulns.

Deleting Erroneously Ingested Vulnerabilities (Admin Only)

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:

  1. Navigate to Admin -> Datastore, or open /admin/datastore?category=shuffle-security_vulns.
  2. Search for the vulnerability key you want to remove (such as CVE-2024-3094).
  3. Delete one finding: Click the delete button on the right side of the row and confirm.
  4. Bulk cleanup: Select the checkboxes next to the records you want to remove and click Delete Selected in the bulk action bar.

Vulnerability Record Schema

FieldTypeDescription
idStringCanonical advisory identifier (e.g. CVE-2024-3094, GHSA-xxxx). Serves as the primary datastore key.
titleStringDescriptive title or headline of the vulnerability.
severityStringSeverity rating: critical, high, medium, or low.
scoreNumberCVSS base numerical score (e.g. 10.0 or 7.4).
categoryStringClassification: software_cve, code_dependency, user_identity, or cloud_misconfig.
statusStringWorkflow status: open, in_progress, mitigated, accepted, or resolved.
affected_packageStringName and version constraint of the affected component (e.g. xz-utils 5.6.0, lodash <4.17.21).
fixed_versionStringMinimum version containing the remediation patch (e.g. 5.6.1).
affected_hostsArrayEndpoints running the vulnerable software or dependency, including hostname, filesystem path, and per-host resolution.

Writing Findings in Python Apps & Workflows

Python

Editable

Response

Key Revisions, Audit Trail & Rollback Protection

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:

  • Protection Against Ingestion Drift & Overwrites: If an external scanner runs an incomplete scan that drops existing CVE findings or overwrites host resolutions, previous revisions remain accessible and can be restored.
  • Audit Attribution: Tracks which workflow execution or analyst changed the finding's severity, updated the CVSS score, or marked a host as mitigated, complete with timestamps and execution IDs.
  • Rollback via API & Workflows:
    • Fetch all revisions for a vulnerability advisory:

      API Call

      GET
      cURL
      Python
      HTTP

      Response

      No response received.

    • Roll back or restore in Python:

      Python

      Editable

      Response


API & Datastore reference

REST API Endpoints

  • List Vulnerabilities: GET /api/v1/vulnerabilities
  • Get Vulnerability Finding: GET /api/v1/vulnerabilities/{id}
  • List Findings from Datastore Directly:

    API Call

    GET
    cURL
    Python
    HTTP

    Response

    No response received.

  • Upsert Finding in Datastore:

    API Call

    POST
    cURL
    Python
    HTTP
    JSON

    Response

    No response received.

In Custom Python Apps & Workflows

Python

Editable

Response

For more details on backend API endpoints and datastore caching rules, see the API documentation.