Links submitted by the Threat Radar community and AI curated for defenders.

Community Curated

CVE Database V5

AlienVault OTX General

Real-world exploitation and exposure telemetry from the OffSeq Mirage honeypot fleet and Sonar internet scans — which CVEs attackers are actually exploiting and which are exposed in the wild, plus attacker IoCs. All IPs are masked; no raw victim or sensor identity is ever published.

OffSeq Mirage

Bleeping Computer

SANS ISC Handlers Diary

Threatpost

SecurityWeek

Reddit ExploitDev

Latest exploits, shellcode, and vulnerability proofs-of-concept from Exploit-DB

Exploit-DB RSS Feed

Reddit ThreatIntel

Reddit BlueTeam

Reddit Reverse Engineering

Reddit Malware

Reddit Cybersecurity

Reddit NetSec

ThreatFox MISP Feed

CIRCL OSINT Feed

NCSC UK

JVN Japan

GCP Compute Engine Security

GCP Kubernetes Security

AWS Security Bulletins

CERT/CC

Tenable Research

Google Project Zero

Microsoft Security Blog

Cisco Talos

Zero Day Initiative

Palo Alto Unit 42

Krebs on Security

Kaspersky Security Blog

Check Point Research

GCVE Database

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

spdystream

spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.

The vulnerability in spdystream (CVE-2026-35469) arises from the SPDY/3 frame parser failing to validate counts and lengths before memory allocation, specifically in SETTINGS frame entry counts, header counts, and individual header field sizes. These values are attacker-controlled and read as 32-bit integers without bounds checking, enabling a small compressed SPDY payload to decompress into large memory allocations. This can cause out-of-memory crashes in services using spdystream, including Kubernetes components Kubelet, CRI-O, and kube-apiserver. Exploitation requires elevated cluster roles permitting pod port forwarding, exec, attach, or node proxying. The issue is fixed in spdystream version 0.5.1. Red Hat advisories recommend restricting these Kubernetes cluster roles to trusted entities to mitigate risk.

Detailed information about CVE-2026-35469: CWE-770: Allocation of Resources Without Limits or Throttling in moby spdystream affecting moby spdystream. Get real-

CVE-2026-35469: CWE-770: Allocation of Resources Without Limits or Throttling in moby spdystream - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2026-35469: CWE-770: Allocation of Resources Without Limits or Throttling in moby spdystream

Threat Intelligence Database

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threat Intelligence

Lead Pen Test Professional