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

rabbitmq-server

RabbitMQ versions prior to 4.3.5 contain a vulnerability where an authenticated user who can bind a queue to a topic exchange and publish to it can exploit consecutive '#' segments in a binding key. This causes the topic matchers to revisit the same trie-node and routing-key-suffix states without memoization, leading to duplicate destination materialization before deduplication. The resulting combinatorial CPU and memory load can disrupt routing for all tenants. This issue is fixed in version 4.3.5.

CVE-2026-67419 affects RabbitMQ messaging broker versions prior to 4.3.5. An authenticated user with permissions to bind queues to topic exchanges and publish messages can craft binding keys with consecutive '#' segments. This triggers the topic matchers to revisit the same trie-node and routing-key-suffix states multiple times without memoization, causing the matcher to materialize duplicate destinations before deduplication. The excessive CPU and memory consumption can disrupt message routing for all tenants sharing the broker. The vulnerability is resolved in RabbitMQ version 4.3.5.

RabbitMQ versions prior to 4.3.5 contain a vulnerability where an authenticated user who can bind a queue to a topic exchange and publish to it can exploit consecutive '#' segments in a binding key. This causes the topic matchers to revisit the same trie-node and routing-key-suffix states without me

Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-67419)

Threats Tagged 'ubuntu-cve-2026-67419'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'ubuntu-cve-2026-67419'

Lead Pen Test Professional