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

Community Curated

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

CVE Database V5

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

AlienVault OTX General

SANS ISC Handlers Diary

SecurityWeek

Threatpost

Reddit ExploitDev

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

Exploit-DB RSS Feed

Reddit ThreatIntel

Reddit BlueTeam

Reddit Malware

Reddit Reverse Engineering

Reddit Cybersecurity

Reddit NetSec

ThreatFox MISP Feed

CIRCL OSINT Feed

Bleeping Computer

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 contain a vulnerability in the MqttEncoder component where client identifiers, will topics, usernames, and PUBLISH topic names are not validated before encoding. This allows prohibited null bytes in MQTT UTF-8 string fields, potentially causing routing, access-control, or identity mismatches in downstream brokers. The issue is fixed in versions 4.1.137.Final and 4.2.17.Final.

Netty is an asynchronous, event-driven network application framework. In versions before 4.1.137.Final and 4.2.17.Final, the MqttEncoder does not validate MQTT UTF-8 string fields such as client identifiers, will topics, usernames, and PUBLISH topic names before encoding. This lack of validation permits prohibited null bytes in these fields, which can lead to routing, access-control, or identity mismatches in downstream MQTT brokers. The vulnerability is exploitable when applications use Netty's MQTT encoder to construct messages from user-controlled input. The issue is resolved in versions 4.1.137.Final and 4.2.17.Final.

Netty versions prior to 4.1.137.Final and 4.2.17.Final contain a vulnerability in the MqttEncoder component where client identifiers, will topics, usernames, and PUBLISH topic names are not validated before encoding. This allows prohibited null bytes in MQTT UTF-8 string fields, potentially causing 

Netty: Prior to versions 4.1.137.Final and 4.2.17.Final, MqttEncoder does not validate client identifiers, will topics, usernames, and PUBLISH topic names… (CVE-2026-76816)

Threats Tagged 'cve-2026-76816'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'cve-2026-76816'

Lead Pen Test Professional