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 from 3.13.0 up to but not including 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18 contain a vulnerability where the JWKS key fetching mechanism ignores HTTP response status codes. This causes the system to treat error responses as successful, leading to destruction of cached signing keys and a persistent denial of service for OAuth2 authentication until a new successful JWKS refresh occurs. This allows an attacker to deny access to all OAuth2 users on the RabbitMQ server. The issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18.

CVE-2026-67409 affects RabbitMQ's OAuth2 JWKS key fetching mechanism in uaajwt.erl, which does not validate HTTP response status codes when downloading signing keys. Non-200 HTTP responses with valid JSON but missing keys cause all cached signing keys to be destroyed, resulting in a persistent authentication denial of service for all OAuth2 users until a successful JWKS refresh. This vulnerability affects RabbitMQ versions from 3.13.0 up to but not including 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18. The flaw is fixed in these versions. The vulnerability has a CVSS 3.1 score of 6.5 (medium severity) with an impact on availability but no confidentiality or integrity impact.

RabbitMQ versions from 3.13.0 up to but not including 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18 contain a vulnerability where the JWKS key fetching mechanism ignores HTTP response status codes. This causes the system to treat error responses as successful, leading to destruction of cached signing ke

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

Threats Tagged 'ubuntu-cve-2026-67409'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'ubuntu-cve-2026-67409'

Lead Pen Test Professional