docker / mcp_gatewayFix what matters first

Ranked by live signal for this scope. Use the feed below to prioritize fixes.

0CVEs in scopecurrent filter

Vendors by Exposure

Select to apply CPE scope

Products by Exposure: docker

Narrow scope by product

Threat signal metrics

CVEs in scope

51,357

Signal volume

172,502

24h volume

0

Active exploitation

31,280

Patches / workarounds

54,330

Aggregate signal volume (30D)

Total mentions across in-scope CVEs. Spikes usually track advisories, PoC chatter, or exploitation reporting, not random drift.

03627241085144710-2310-2610-2911-0111-0411-0711-1011-1311-1611-1911-20

Signal classification

Where discussion is coming from. Useful context when a CVE suddenly dominates a category.

164,566Total

Threat indicators

PoC references, exploit code, active exploitation, patches, and technical detail, aggregated for the current scope.

228,672Total

> pipeline.stream (live)

How it works

One post becomes signal: watch it move through ingest → classify → enrich → route.

Pipeline stage 1 of 4: Ingest signals
Ingestcapture
Classifytag + score
Enrichcontext
Emitroute

Simo @SimoKohonen

Example post · pipeline demo

Webshells be flowing into Cisco SD-WAN honeypots now.. Exploitation of CVE-2026-20127 is looking pretty heavy, new actors popping up by the hour

ingest: raw post · CVE-2026-20127

15.7K views65 likes19 RTs2 replies20 bookmarks

  1. [ 01 ]

    Ingest signals

    We collect and classify mentions across channels that move before tickets do: advisories, researcher posts, exploit references, and technical discussion.

  2. [ 02 ]

    Score attention

    CVEs surface by signal volume and trajectory, not a static severity label, so spikes in discussion map to spikes in urgency.

  3. [ 03 ]

    Surface threat context

    Exploit momentum, PoC noise, active exploitation flags, and patch availability appear alongside each CVE so triage is factual, not guesswork.

  4. [ 04 ]

    Scope to your stack

    Filter by vendor and product (Microsoft, Apple, Cisco, and more) so the feed reflects exposure you actually run, not the entire internet’s backlog.

> loop: raw social post → classify → enrich with threat context → emit to your scoped feed

About VulnSocial

VulnSocial is not a generic scanner. We aggregate and classify vulnerability signals from the channels that move first: researchers, advisories, exploit references, and community discussion. CVEs are ordered by attention and momentum, not CVSS alone. Active exploitation indicators, PoC noise, and patch availability sit next to each CVE so triage is grounded in what is happening now.

Scope the dashboard with vendor and product filters to match your stack. Security teams use VulnSocial to cut through alert fatigue: SOC analysts for ranked triage, leads for credible briefings, DevSecOps for stack-specific trending and remediation timing. Share snapshots with your team from the feed when you need to align on what matters today.