Latest

Trojanized Terraform Providers Show IaC Pipelines Are Developer Endpoints

Malicious AI Agent Skills Turn Prompt Instructions Into Supply-Chain Risk

ARTEX AI Bank Attacks Show Agentic Tools Are Now an Incident-Response Problem

Ransomware Negotiation Arrest Shows Why Extortion Response Needs Guardrails

Internet Scanning Turns Open Ports Into Threat-Intel Pivots

AnyDesk Linux Exploit Shows Remote Access Tools Need Exposure Controls

Go Security Release Shows Why HTTP/2 and Proxy Paths Need Patch Discipline

Midnight Mimosa Shows Why Cheap Android Devices Need Supply-Chain Controls

AI-Analysis Evasion Shows Why Malware Triage Needs Prompt Boundaries

Web3 C2 Shows Why Build Pipelines Need Egress Controls

AI Agent Swarms Turn Security Basics Into Cost Controls

Q3 Attack Trends Show Trusted Paths Are Becoming the Real Target

FortiBleed Shows Why VPN Credential Compromise Needs Full Incident Response

GitHub Enterprise SSRF Shows Why Secret Scanning Needs Network Guardrails

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.

1129 archived unique observations

← Current observations (2808)Revalidation queue (2067)IOC Archive (1129)

200 archived observations on this page

Showing 401–600 of 1129

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 →

CVE

CVE-2026-7917

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

Source report →

CVE

CVE-2026-7918

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

Source report →

CVE

CVE-2026-7919

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

Source report →

CVE

CVE-2026-7920

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

Source report →

CVE

CVE-2026-7921

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

Source report →

CVE

CVE-2026-7922

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

Source report →

CVE

CVE-2026-7923

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

Source report →

CVE

CVE-2026-7924

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

Source report →

CVE

CVE-2026-7925

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

Source report →

CVE

CVE-2026-7926

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

Source report →

CVE

CVE-2026-7927

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

Source report →

CVE

CVE-2026-7928

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

Source report →

CVE

CVE-2026-7929

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

Source report →

CVE

CVE-2026-7930

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

Source report →

CVE

CVE-2026-7931

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

Source report →

CVE

CVE-2026-7932

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

Source report →

CVE

CVE-2026-7933

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

Source report →

CVE

CVE-2026-7934

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

Source report →

CVE

CVE-2026-7935

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

Source report →

CVE

CVE-2026-7936

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

Source report →

CVE

CVE-2026-7937

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

Source report →

CVE

CVE-2026-7938

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

Source report →

CVE

CVE-2026-7939

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

Source report →

CVE

CVE-2026-7940

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

Source report →

CVE

CVE-2026-7941

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

Source report →

CVE

CVE-2026-7942

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

Source report →

CVE

CVE-2026-7943

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

Source report →

CVE

CVE-2026-7944

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

Source report →

CVE

CVE-2026-7945

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

Source report →

CVE

CVE-2026-7946

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

Source report →

CVE

CVE-2026-7947

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

Source report →

CVE

CVE-2026-7948

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

Source report →

CVE

CVE-2026-7949

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

Source report →

CVE

CVE-2026-7950

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

Source report →

CVE

CVE-2026-7951

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

Source report →

CVE

CVE-2026-7952

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

Source report →

CVE

CVE-2026-7953

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

Source report →

CVE

CVE-2026-7954

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

Source report →

CVE

CVE-2026-7955

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

Source report →

CVE

CVE-2026-7956

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

Source report →

CVE

CVE-2026-7957

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

Source report →

CVE

CVE-2026-7958

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

Source report →

CVE

CVE-2026-7959

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

Source report →

CVE

CVE-2026-7960

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

Source report →

CVE

CVE-2026-7961

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

Source report →

CVE

CVE-2026-7962

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

Source report →

CVE

CVE-2026-7963

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

Source report →

CVE

CVE-2026-7964

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

Source report →

CVE

CVE-2026-7965

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

Source report →

CVE

CVE-2026-7966

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

Source report →

CVE

CVE-2026-7967

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

Source report →

CVE

CVE-2026-7968

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

Source report →

CVE

CVE-2026-7969

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

Source report →

CVE

CVE-2026-7970

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

Source report →

CVE

CVE-2026-7971

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

Source report →

CVE

CVE-2026-7972

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

Source report →

CVE

CVE-2026-7973

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

Source report →

CVE

CVE-2026-7974

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

Source report →

CVE

CVE-2026-7975

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

Source report →

CVE

CVE-2026-7976

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

Source report →

CVE

CVE-2026-7977

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

Source report →

CVE

CVE-2026-7978

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

Source report →

CVE

CVE-2026-7979

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

Source report →

CVE

CVE-2026-7980

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

Source report →

CVE

CVE-2026-7981

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

Source report →

CVE

CVE-2026-7982

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

Source report →

CVE

CVE-2026-7983

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

Source report →

CVE

CVE-2026-7984

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

Source report →

CVE

CVE-2026-7985

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

Source report →

CVE

CVE-2026-7986

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

Source report →

CVE

CVE-2026-7987

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

Source report →

CVE

CVE-2026-7988

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

Source report →

CVE

CVE-2026-7989

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

Source report →

CVE

CVE-2026-7990

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

Source report →

CVE

CVE-2026-7991

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

Source report →

CVE

CVE-2026-7992

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

Source report →

CVE

CVE-2026-7993

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

Source report →

CVE

CVE-2026-7994

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

Source report →

CVE

CVE-2026-7995

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

Source report →

CVE

CVE-2026-7996

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

Source report →

CVE

CVE-2026-7997

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

Source report →

CVE

CVE-2026-7998

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

Source report →

CVE

CVE-2026-7999

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

Source report →

CVE

CVE-2026-8000

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

Source report →

CVE

CVE-2026-8001

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

Source report →

CVE

CVE-2026-8002

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

Source report →

CVE

CVE-2026-8003

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

Source report →

CVE

CVE-2026-8004

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

Source report →

CVE

CVE-2026-8005

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

Source report →

CVE

CVE-2026-8006

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

Source report →

CVE

CVE-2026-8007

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

Source report →

CVE

CVE-2026-8008

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

Source report →

CVE

CVE-2026-8009

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

Source report →

CVE

CVE-2026-8010

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

Source report →

CVE

CVE-2026-8011

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

Source report →

CVE

CVE-2026-8012

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

Source report →

CVE

CVE-2026-8013

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

Source report →

CVE

CVE-2026-8014

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

Source report →

CVE

CVE-2026-8015

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

Source report →

CVE

CVE-2026-8016

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

Source report →

CVE

CVE-2026-8017

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

Source report →

CVE

CVE-2026-8018

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

Source report →

CVE

CVE-2026-8019

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

Source report →

CVE

CVE-2026-8020

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

Source report →

CVE

CVE-2026-8021

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

Source report →

CVE

CVE-2026-8022

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

Source report →

CVE

CVE-2025-32433

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

Source report →

Domain

bleacherreport[.]com

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 26, 2026 · 1 source report

Source report →

Domain

justwatch[.]com

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 26, 2026 · 1 source report

Source report →

Domain

pool[.]supportxmr[.]com

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 26, 2026 · 1 source report

Source report →

Domain

supportxmr[.]com

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 26, 2026 · 1 source report

Source report →

CVE

CVE-2026-46300

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

Source report →

CVE

CVE-2026-25592

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

Source report →

CVE

CVE-2026-26030

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

Source report →

URL

hxxp://194[.]233[.]92[.]26:2222/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 1, 2026 · 1 source report

Source report →

URL

hxxp://194[.]233[.]92[.]26:8088/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 29, 2026 · 1 source report

Source report →

URL

hxxp://217[.]15[.]160[.]247:2222/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 29, 2026 · 1 source report

Source report →

URL

hxxp://217[.]15[.]160[.]247:8088/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 7, 2026 · 1 source report

Source report →

URL

hxxp://217[.]15[.]160[.]247:99/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 7, 2026 · 1 source report

Source report →

URL

hxxp://217[.]15[.]164[.]147:2222/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 29, 2026 · 1 source report

Source report →

URL

hxxp://217[.]15[.]164[.]147:8088/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 1, 2026 · 1 source report

Source report →

URL

hxxp://217[.]15[.]164[.]147:99/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 1, 2026 · 1 source report

Source report →

URL

hxxp://95[.]182[.]100[.]231:2222/

Last reported Jul 7, 2026 · Reporting window ended Aug 6, 2026 · Archive check completed Sep 1, 2026 · 1 source report

Source report →

Domain

ns1[.]fbi[.]seized[.]gov

Last reported Jul 2, 2026 · Reporting window ended Aug 1, 2026 · Archive check completed Sep 11, 2026 · 1 source report

Source report →

Domain

clear90489058903-document[.]workers[.]dev

Last reported Jul 1, 2026 · Reporting window ended Jul 31, 2026 · Archive check completed Sep 26, 2026 · 1 source report

Source report →

Domain

mononapfp[.]sharepoint[.]com

Last reported Jul 1, 2026 · Reporting window ended Jul 31, 2026 · Archive check completed Sep 26, 2026 · 1 source report

Source report →

Domain

mononapfpcom[.]sharepoint[.]com

Last reported Jul 1, 2026 · Reporting window ended Jul 31, 2026 · Archive check completed Sep 26, 2026 · 1 source report

Source report →

Domain

sharepoint[.]com

Last reported Jul 1, 2026 · Reporting window ended Jul 31, 2026 · Archive check completed Sep 26, 2026 · 2 source reports

IOC Passport →

Domain

workers[.]dev

Last reported Jul 1, 2026 · Reporting window ended Jul 31, 2026 · Archive check completed Oct 3, 2026 · 3 source reports

IOC Passport →

URL

hxxps://mononapfp[.]sharepoint[.]com/:f:/document/INV-IgCx1X50pgUjR7iAjZL2fuQaAW4GfKVs6wHT3BYv9sgwW7g

Last reported Jul 1, 2026 · Reporting window ended Jul 31, 2026 · Archive check completed Sep 1, 2026 · 1 source report

Source report →

URL

hxxps://mononapfpcom[.]sharepoint[.]com/:f:/g/IgAdH_aaBPMcQbtINZzC1TsLARj3dHj63MnKjvnY-QJrKEc

Last reported Jul 1, 2026 · Reporting window ended Jul 31, 2026 · Archive check completed Sep 26, 2026 · 1 source report

Source report →

URL

hxxps://blackpointcyber[.]com/blog/a-djinn-in-the-machine-taskweavers-node-js-intrusion-chain/

Last reported Jun 30, 2026 · Reporting window ended Jul 30, 2026 · Archive check completed Sep 12, 2026 · 1 source report

Source report →

URL

hxxps://horizon3[.]ai/attack-research/disclosures/cve-2026-48558-simplehelp-authentication-bypass-iocs/

Last reported Jun 30, 2026 · Reporting window ended Jul 30, 2026 · Archive check completed Sep 1, 2026 · 1 source report

Source report →

URL

hxxps://simple-help[.]com/release-news

Last reported Jun 30, 2026 · Reporting window ended Jul 30, 2026 · Archive check completed Sep 1, 2026 · 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.