Exploitation timeline
Threadlinqs has recorded 6 picklescan CVEs published between and . The busiest month was 2026-06 (6 new CVEs). None of them is listed in CISA KEV yet.
Most exploited vulnerabilities
Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 6 of 6 tracked picklescan CVEs.
- CVE-2026-3490critical 10EPSS 0.6%
- CVE-2026-53874critical 9.8EPSS 0.5%
- CVE-2026-53872high 7.5EPSS 0.5%
- CVE-2026-53873critical 9.8EPSS 0.5%
- CVE-2026-53875high 7.1EPSS 0.4%
- CVE-2026-56304medium 6.5
Products affected
Threadlinqs normalises CPE and CNA product records across all 6 CVEs; 1 distinct picklescan product is affected. The most frequently affected:
- picklescan 6 CVEs
Threat activity
No tracked threat campaign references picklescan products or CVEs yet. Vulnerability records are still monitored for exploitation and linked as campaigns are ingested.
How to prioritise picklescan patching
This order follows the data Threadlinqs holds for picklescan, not a generic severity checklist:
- No picklescan CVE is in CISA KEV yet, so rank by exploit probability instead.
- Outside KEV, the highest EPSS scores are CVE-2026-3490 (0.6%), CVE-2026-53874 (0.5%), CVE-2026-53872 (0.5%).
- 3 CVEs score Critical and 2 High on CVSS v3 (maximum 10, average 8.5); sequence these after KEV and high-EPSS items.
About this data
Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-10-05 and refresh daily.