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

Community Curated

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 ThreatIntel

Reddit BlueTeam

Reddit Reverse Engineering

Reddit Malware

Reddit NetSec

Reddit Cybersecurity

ThreatFox MISP Feed

CIRCL OSINT Feed

NCSC UK

JVN Japan

GCP Compute Engine Security

AWS Security Bulletins

GCP Kubernetes Security

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

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

logging-operator

A critical injection vulnerability (CVE-2026-54680) exists in kube-logging logging-operator versions prior to 6.6.0. The Fluentd configuration renderer writes certain CRD strings directly into configuration files without proper escaping, allowing an attacker with permission to create Flow resources to inject malicious Fluentd <match **> blocks. This can lead to arbitrary command execution within the Fluentd aggregator. The issue is resolved in version 6.6.0.

The kube-logging logging-operator prior to version 6.6.0 contains an injection vulnerability due to improper neutralization of special elements in output used by the FluentRender component. Specifically, the Flow record_transformer.records values are written directly into fluent.conf without escaping, enabling a user who can create Flow resources to inject a Fluentd <match **> block using @type exec. This allows execution of arbitrary commands inside the Fluentd aggregator. The vulnerability is tracked as CVE-2026-54680 with a CVSS 3.1 score of 9.9, indicating critical severity. The vulnerability is fixed in version 6.6.0.

Detailed information about CVE-2026-54680: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in kube-lo

CVE-2026-54680: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in kube-logging logging-operator - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2026-54680: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in kube-logging logging-operator

Insecure permissions in logging-operator v4.6.0 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

CVE-2024-36541 is a vulnerability identified in logging-operator version 4.6.0, a Kubernetes operator used to manage logging configurations and pipelines. The root cause is insecure permissions set on resources managed by the operator, specifically allowing attackers to access the service account token associated with the operator. Service account tokens in Kubernetes provide authentication credentials that can be used to interact with the Kubernetes API server with the privileges assigned to that account. By obtaining this token, an attacker can escalate privileges beyond their initial access level, potentially gaining control over cluster resources, accessing sensitive data, or disrupting services. The vulnerability is classified under CWE-276, which refers to improper permissions or access control. The CVSS v3.1 score of 8.8 reflects a network attack vector with low attack complexity, requiring privileges but no user interaction, and impacting confidentiality, integrity, and availability at a high level. Although no public exploits have been reported yet, the vulnerability's nature and the critical role of logging-operator in Kubernetes environments make it a serious threat. The lack of patch links suggests that a fix may not yet be publicly available, emphasizing the need for immediate mitigation strategies. This vulnerability highlights the importance of strict permission management in Kubernetes operators and the risks posed by overly permissive configurations.

Detailed information about CVE-2024-36541: n/a. Get real-time updates, technical details, and mitigation strategies.

CVE-2024-36541: n/a - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2024-36541: n/a


CVE-2026-54680: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in kube-logging logging-operatorCVE-2026-54680 0 A critical injection vulnerability (CVE-2026-54680) exists in kube-logging logging-operator versions prior to 6.6.0. The Fluentd configuration renderer writes certain CRD strings directly into configuration files without proper escaping, allowing an attacker with permission to create Flow resources to inject malicious Fluentd <match **> blocks. This can lead to arbitrary command execution within the Fluentd aggregator. The issue is resolved in version 6.6.0. CriticalVulnerability#cve #cve-2026-54680 #cwe-74 Join the discussion	CVE Database V5	07/29/2026, 16:57:16 UTC Added: 07/29/2026, 17:07:43 UTC
CVE-2024-36541: n/aCVE-2024-36541 0 Insecure permissions in logging-operator v4.6.0 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token. HighVulnerabilityUnited StatesGermanyUnited Kingdom+8#cve #cve-2024-36541 Join the discussion	CVE Database V5	07/24/2024, 00:00:00 UTC Added: 02/25/2026, 21:40:47 UTC

Threat Intelligence Database

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threat Intelligence

Lead Pen Test Professional