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

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 BlueTeam

Reddit ThreatIntel

Reddit Reverse Engineering

Reddit Malware

Reddit Cybersecurity

Reddit NetSec

ThreatFox MISP Feed

CIRCL OSINT Feed

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

netty

Netty versions prior to 4.1.135.Final and 4.2.15.Final have a vulnerability where the DefaultHttp2Connection.DefaultEndpoint initializes maxActiveStreams and maxStreams to Integer.MAX_VALUE, effectively imposing no limit on concurrent HTTP/2 streams. This can lead to excessive resource consumption on the server side, as each open stream allocates multiple objects and state entries. The issue is patched in versions 4.1.135.Final and 4.2.15.Final.

Netty, a network application framework, had a flaw in versions before 4.1.135.Final and 4.2.15.Final where DefaultHttp2Connection.DefaultEndpoint set maxActiveStreams and maxStreams to Integer.MAX_VALUE by default. Additionally, Http2Settings did not insert SETTINGS_MAX_CONCURRENT_STREAMS by default, meaning a Netty HTTP/2 server would advertise no limit on concurrent streams and enforce none locally unless explicitly configured. This allows a single TCP connection to create hundreds of thousands of long-lived stream objects, consuming significant server resources. This condition also sets the stage for amplification attacks similar to CVE-2023-44487. The vulnerability is addressed in versions 4.1.135.Final and 4.2.15.Final.

Netty versions prior to 4.1.135.Final and 4.2.15.Final have a vulnerability where the DefaultHttp2Connection.DefaultEndpoint initializes maxActiveStreams and maxStreams to Integer.MAX_VALUE, effectively imposing no limit on concurrent HTTP/2 streams. This can lead to excessive resource consumption o

Netty: Prior to versions 4.1.135.Final and 4.2.15.Final, DefaultHttp2Connection.DefaultEndpoint initialises maxActiveStreams/maxStreams to… (CVE-2026-47244)

Threats Tagged 'ubuntu-cve-2026-47244'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'ubuntu-cve-2026-47244'

Lead Pen Test Professional