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

A vulnerability in Netty prior to versions 4.1.137.Final and 4.2.17.Final causes the SslClientHelloHandler#decode method to check the wrong offset when reading the TLS handshake header. This can lead to an IndexOutOfBoundsException and fallback to the default SslContext instead of the SNI-specific context. In configurations where mutual TLS authentication is enforced per SNI, this fallback can allow an unauthenticated attacker to bypass the mutual TLS requirement. The issue is fixed in versions 4.1.137.Final and 4.2.17.Final.

Netty versions before 4.1.137.Final and 4.2.17.Final contain a flaw in the io.netty.handler.ssl.SslClientHelloHandler#decode method where it incorrectly checks the offset before reading the four-byte TLS handshake header. This causes an IndexOutOfBoundsException when a ClientHello message's handshake header spans multiple records, triggering a fallback to the default SslContext rather than the SNI-specific context. If the deployment relies solely on per-SNI clientAuth=REQUIRE for mutual TLS enforcement, and the default SslContext uses clientAuth=NONE or OPTIONAL without additional certificate verification, an unauthenticated remote attacker can bypass mutual TLS protections. The vulnerability is resolved in versions 4.1.137.Final and 4.2.17.Final.

Detailed information about Prior to 4.1.137.Fina and 4.2.17.Final, io.netty.handler.ssl.SslClientHelloHandler#decode checks the wrong offset before reading the 

Prior to 4.1.137.Fina and 4.2.17.Final, io.netty.handler.ssl.SslClientHelloHandler#decode checks the wrong offset before reading the four-byte TLS… (CVE-2026-75595) - Live Threat Intelligence - Threat Radar | OffSeq.com

Prior to 4.1.137.Fina and 4.2.17.Final, io.netty.handler.ssl.SslClientHelloHandler#decode checks the wrong offset before reading the four-byte TLS… (CVE-2026-75595)

Threats Tagged 'ubuntu-cve-2026-75595'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'ubuntu-cve-2026-75595'

Lead Pen Test Professional