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

SecurityWeek

Threatpost

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

Exploit-DB RSS Feed

Reddit ExploitDev

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

Tenable Research

CERT/CC

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

netty

Netty versions prior to 4.1.137.Final and 4.2.17.Final have a vulnerability in the default io.netty.handler.ssl.SniHandler constructors that causes excessive CPU usage during TLS handshake. This occurs because the pre-handshake ClientHello aggregation path inefficiently processes large ClientHello messages delivered in many small TLS records, leading to quadratic CPU work on the event loop. This degrades TLS handling performance for other clients. The issue is fixed in versions 4.1.137.Final and 4.2.17.Final.

The vulnerability (CVE-2026-75596) affects Netty's io.netty.handler.ssl.SniHandler default constructors prior to versions 4.1.137.Final and 4.2.17.Final. The flaw lies in the pre-handshake ClientHello aggregation path where the handshakeBuffer.clear() and writeBytes() methods recopy all previously received body bytes for every additional TLS record. An unauthenticated remote peer can exploit this by sending a large ClientHello message fragmented into thousands of tiny TLS records, causing quadratic CPU consumption on the event loop before the TLS handshake completes. This results in degraded TLS handling performance for other clients sharing the event loop. The issue is resolved in the specified fixed versions.

Detailed information about Prior to 4.1.137.Final and 4.2.17.Final, the default io.netty.handler.ssl.SniHandler constructors use the pre-handshake ClientHello a

Prior to 4.1.137.Final and 4.2.17.Final, the default io.netty.handler.ssl.SniHandler constructors use the pre-handshake ClientHello aggregation path… (CVE-2026-75596) - Live Threat Intelligence - Threat Radar | OffSeq.com

Prior to 4.1.137.Final and 4.2.17.Final, the default io.netty.handler.ssl.SniHandler constructors use the pre-handshake ClientHello aggregation path… (CVE-2026-75596)

Threats Tagged 'cve-2026-75596'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'cve-2026-75596'

Lead Pen Test Professional