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

Community Curated

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 BlueTeam

Reddit ThreatIntel

Reddit Reverse Engineering

Reddit Malware

Reddit Cybersecurity

Reddit NetSec

ThreatFox MISP Feed

CIRCL OSINT Feed

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

Bleeping Computer

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

rabbitmq-server

RabbitMQ versions from 4.2.0 until 4.2.9 and 4.3.3 contain a vulnerability in OAuth2 token expiry validation. The issue arises because the code only checks token expiry if the 'exp' claim is an integer, skipping expiry checks if 'exp' is a float, which is allowed by RFC 7519. This allows acceptance of expired tokens if the Identity Provider emits 'exp' as a float, causing login-time expiry checks and mid-connection disconnect timers to be bypassed. The vulnerability is fixed in versions 4.2.9 and 4.3.3.

The RabbitMQ server's OAuth2 implementation improperly validates the 'exp' (expiry) claim in JWT tokens when the 'exp' value is a floating-point number. The functions validatetokenexpiry/1 and expirytimestamp/1 only perform expiry checks when 'exp' is an integer, ignoring float values. Since RFC 7519 permits fractional NumericDate values, tokens with float 'exp' values bypass expiry validation entirely. This flaw allows an attacker possessing a previously valid signed token with a float 'exp' to use expired tokens indefinitely, as neither login-time expiry checks nor mid-connection disconnect timers are enforced. This vulnerability affects RabbitMQ versions from 4.2.0 up to but not including 4.2.9 and 4.3.3, where the issue has been fixed.

RabbitMQ versions from 4.2.0 until 4.2.9 and 4.3.3 contain a vulnerability in OAuth2 token expiry validation. The issue arises because the code only checks token expiry if the 'exp' claim is an integer, skipping expiry checks if 'exp' is a float, which is allowed by RFC 7519. This allows acceptance 

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

Threats Tagged 'ubuntu-cve-2026-67242'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'ubuntu-cve-2026-67242'

Lead Pen Test Professional