VULNSOCIAL
ollyo / sp_page_builderFix what matters first
Ranked by live signal for this scope. Use the feed below to prioritize fixes.
What to fix first
exploited 1
Vendors by Exposure
Select to apply CPE scope
Products by Exposure: ollyo
Narrow scope by product
Attention over time (30D)
Mention volume for the top 1 CVEs in this view. Toggle series to compare momentum.
Threat signal metrics
41,185
CVEs in scope
127,044
Signal volume
234
24h volume
21,027
Active exploitation
34,375
Patches / workarounds
Aggregate signal volume (30D)
Total mentions across in-scope CVEs. Spikes usually track advisories, PoC chatter, or exploitation reporting, not random drift.
Signal classification
Where discussion is coming from. Useful context when a CVE suddenly dominates a category.
- Disclosure58,442(47.3%)
- Patch21,796(17.7%)
- Active Exploitation19,318(15.6%)
- General19,315(15.6%)
- PoC4,598(3.7%)
Threat indicators
PoC references, exploit code, active exploitation, patches, and technical detail, aggregated for the current scope.
- Technical Details92,260(56.9%)
- Patch Available34,375(21.2%)
- Active Exploitation21,027(13.0%)
- PoC Mentioned10,136(6.3%)
- Exploit Code4,329(2.7%)
> pipeline.stream (live)
How it works
One post becomes signal: watch it move through ingest → classify → enrich → route.
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
- [ 01 ]
Ingest signals
We collect and classify mentions across channels that move before tickets do: advisories, researcher posts, exploit references, and technical discussion.
- [ 02 ]
Score attention
CVEs surface by signal volume and trajectory, not a static severity label, so spikes in discussion map to spikes in urgency.
- [ 03 ]
Surface threat context
Exploit momentum, PoC noise, active exploitation flags, and patch availability appear alongside each CVE so triage is factual, not guesswork.
- [ 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.