Latest

AI-Assisted Exploits Make OT Reachability the Real Control

White-Label Router Backdoors Show Why Edge Provenance Matters

PaperCut Zero-Day Exploitation Shows Why Print Servers Need Edge-Asset Discipline

AI Infrastructure Is Becoming a Control Plane Attack Surface

QScan and QTRouter Show Why Proxy Infrastructure Is an Espionage Force Multiplier

vCenter Exploitation Shows Patching Alone Is Not Incident Response

Edge Infrastructure Convergence Shows Why Perimeter Devices Need Their Own Patch SLAs Signed ClickOnce Lures Show Why Hiring Workflows Need Endpoint Guardrails

ShieldBreak Shows Why Endpoint Protection Needs Compensating Controls

AI-Enabled Malware Still Behaves Like Malware

Private APNs Are Becoming OT Attack Paths

vCenter Exploitation Shows Why Control Planes Need Containment

Apollo Breach Shows Why Helpdesk Vishing Is a Cloud-Control Problem

BTR.sys Shows Why Trusted Security Drivers Need Behavioral Monitoring

Threat Intelligence · Historical Research

IOC Archive

Historical article-derived observables that no longer fall inside the current reporting-recency window for their type. Provider-supported values enter only after the applicable enabled services complete the required boundary check without qualifying positive evidence. They remain available for research, pivots, and attribution review. Archived does not mean clean, benign, remediated, resolved, or safe. This archive is not a blocklist.

Reporting-window dates come from Bulwark Black report publication dates, not provider sightings. IP/CIDR observations use 14 days, domains and URLs 30 days, file identifiers 730 days, and other context 90 days. Types without an applicable exact provider check archive by recency alone. Current verified-feed admission is evaluated separately on each IOC Passport and in the machine-readable feeds.

458 archived unique observations

← Current observations (2167)Revalidation queue (1660)IOC Archive (458)

200 archived observations on this page

Showing 1–200 of 458

CVE

CVE-2026-22554

Last reported May 27, 2026 · Reporting window ended Aug 25, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-25104

Last reported May 27, 2026 · Reporting window ended Aug 25, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-25713

Last reported May 27, 2026 · Reporting window ended Aug 25, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-28764

Last reported May 27, 2026 · Reporting window ended Aug 25, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-48172

Last reported May 26, 2026 · Reporting window ended Aug 24, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-5426

Last reported May 25, 2026 · Reporting window ended Aug 23, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2022-30190

Last reported May 24, 2026 · Reporting window ended Aug 22, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-9082

Last reported May 23, 2026 · Reporting window ended Aug 21, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2025-33073

Last reported May 22, 2026 · Reporting window ended Aug 20, 2026 · Context-only recency placement · 2 source reports

IOC Passport →

CVE

CVE-2025-53521

Last reported May 22, 2026 · Reporting window ended Aug 20, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2021-22204

Last reported May 20, 2026 · Reporting window ended Aug 18, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-3102

Last reported May 20, 2026 · Reporting window ended Aug 18, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2022-0543

Last reported May 20, 2026 · Reporting window ended Aug 18, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2025-11953

Last reported May 20, 2026 · Reporting window ended Aug 18, 2026 · Context-only recency placement · 2 source reports

IOC Passport →

CVE

CVE-2025-49844

Last reported May 20, 2026 · Reporting window ended Aug 18, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7301

Last reported May 18, 2026 · Reporting window ended Aug 16, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7302

Last reported May 18, 2026 · Reporting window ended Aug 16, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7304

Last reported May 18, 2026 · Reporting window ended Aug 16, 2026 · Context-only recency placement · 1 source report

Source report →

CIDR

173[.]239[.]211[.]0/24

Last reported Aug 1, 2026 · Reporting window ended Aug 15, 2026 · Context-only recency placement · 1 source report

Source report →

CIDR

45[.]131[.]194[.]0/24

Last reported Aug 1, 2026 · Reporting window ended Aug 15, 2026 · Context-only recency placement · 1 source report

Source report →

CIDR

45[.]146[.]54[.]0/24

Last reported Aug 1, 2026 · Reporting window ended Aug 15, 2026 · Context-only recency placement · 1 source report

Source report →

CIDR

63[.]135[.]161[.]0/24

Last reported Aug 1, 2026 · Reporting window ended Aug 15, 2026 · Context-only recency placement · 1 source report

Source report →

Email Addresses

victim[.]user@company[.]com

Last reported May 15, 2026 · Reporting window ended Aug 13, 2026 · Context-only recency placement · 1 source report

Source report →

Email Addresses

victim[.]user@organization[.]com

Last reported May 15, 2026 · Reporting window ended Aug 13, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-20122

Last reported May 14, 2026 · Reporting window ended Aug 12, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-20128

Last reported May 14, 2026 · Reporting window ended Aug 12, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-20133

Last reported May 14, 2026 · Reporting window ended Aug 12, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2025-54518

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-21530

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-26129

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-26164

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-32161

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-32170

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-32175

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-32177

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-32185

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-32204

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-32207

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-32209

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33109

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33110

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33111

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33112

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33117

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33821

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33823

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33833

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33834

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33835

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33837

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33838

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33839

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33840

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33841

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-33844

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34327

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34329

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34330

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34331

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34332

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34333

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34334

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34336

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34337

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34338

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34339

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34340

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34341

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34342

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34343

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34344

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34345

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34347

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34350

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34351

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34645

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34646

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34647

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34648

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34649

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34650

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34651

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34652

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34653

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34654

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34655

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34656

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-34658

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35415

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35416

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35417

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35418

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35419

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35420

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35421

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35422

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35423

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35424

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35428

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35429

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35432

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35433

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35435

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35436

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35438

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35439

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-35440

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40357

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40358

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40359

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40360

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40361

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40362

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40363

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40364

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40365

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40366

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40367

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40368

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40369

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40370

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40374

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40377

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40379

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40380

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40381

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40382

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40397

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40398

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40399

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40401

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40402

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40403

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40405

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40406

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40407

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40408

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40410

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40413

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40414

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40415

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40416

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40417

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40418

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40419

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40420

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-40421

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41086

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41088

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41089

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41094

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41095

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41096

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41097

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41100

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41101

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41102

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41103

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41105

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41107

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41109

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41610

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41611

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41612

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41613

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-41614

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42823

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42825

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42826

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42830

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42831

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42832

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42833

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42838

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42891

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42893

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42896

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42898

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-42899

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7896

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7897

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7898

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7899

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7900

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7901

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7902

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7903

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7904

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7905

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7906

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7907

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7908

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7909

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7910

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7911

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7912

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7913

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7914

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7915

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

CVE

CVE-2026-7916

Last reported May 13, 2026 · Reporting window ended Aug 11, 2026 · Context-only recency placement · 1 source report

Source report →

Newsletter

The House-Of-L Brief.

Two short reads a day on markets, cyber threats, AI, and geopolitics. A "why it matters" line on every story.

Double opt-in. One-click unsubscribe on every issue. We never share your address.