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

rabbitmq-server

CVE-2026-67238 is a vulnerability in RabbitMQ server prior to versions 4.2.7 and 4.3.1. It involves improper handling of caller-supplied ETF-encoded binaries in the rabbit_pid_codec:decompose_from_binary/1 function, which can lead to exhaustion of atoms in the Erlang VM. An authenticated AMQP client can exploit this by sending approximately one million crafted requests, causing the entire Erlang VM to crash, affecting all virtual hosts and connections. The issue is fixed in RabbitMQ versions 4.2.7 and 4.3.1.

RabbitMQ versions prior to 4.2.7 and 4.3.1 contain a vulnerability in the rabbit_pid_codec:decompose_from_binary/1 function. This function parses a caller-supplied ETF-encoded binary and calls binary_to_atom(Node, utf8) on the node-name field without using binary_to_existing_atom, leading to atom exhaustion since atoms are not garbage collected. The vulnerability is reachable via rabbit_volatile_queue:pid_from_name/2 for any queue name or routing key beginning with amq.rabbitmq.reply-to.. An authenticated AMQP 0-9-1 client can trigger this by sending around one million crafted requests, causing the Erlang VM to crash and disrupt all virtual hosts and connections. The vulnerability requires no user interaction and has a low attack complexity but requires authentication and no rate limiting to be effective. The issue is resolved in RabbitMQ versions 4.2.7 and 4.3.1.

CVE-2026-67238 is a vulnerability in RabbitMQ server prior to versions 4.2.7 and 4.3.1. It involves improper handling of caller-supplied ETF-encoded binaries in the rabbit_pid_codec:decompose_from_binary/1 function, which can lead to exhaustion of atoms in the Erlang VM. An authenticated AMQP client

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

Threats Tagged 'ubuntu-cve-2026-67238'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'ubuntu-cve-2026-67238'

Lead Pen Test Professional