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

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 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

poco v1.14.1-release was discovered to contain weak encryption. NOTE: this issue has been disputed on the basis that key lengths are expected to be set by an application, not by this library. This dispute is subject to review under CNA rules 4.1.4, 4.1.14, and other rules; the dispute tagging is not meant to recommend an outcome for this CVE Record.

CVE-2025-45766 identifies a vulnerability in the poco library version 1.14.1-release related to weak encryption implementation. The core issue revolves around the use of cryptographic algorithms or key lengths that do not meet strong security standards, potentially allowing attackers to compromise the confidentiality and integrity of data protected by this library. However, this vulnerability is disputed because the poco library itself does not enforce key lengths; instead, it expects the application using the library to specify appropriate cryptographic parameters. This dispute is currently under review according to CNA rules, indicating that the final classification of this vulnerability may evolve. The vulnerability is categorized under CWE-327, which pertains to the use of broken or risky cryptographic algorithms. The CVSS v3.1 score assigned is 7.0 (high severity), with a vector indicating network attack vector (AV:N), high attack complexity (AC:H), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), low confidentiality and integrity impact (C:L, I:L), and high availability impact (A:H). This suggests that while confidentiality and integrity impacts are limited, the vulnerability could cause significant availability disruption, possibly through denial-of-service conditions triggered by cryptographic failures. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability affects the poco library broadly, without specific version details beyond 1.14.1-release, and the dispute highlights that the risk may depend heavily on how applications implement cryptographic key management when using poco.

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

CVE-2025-45766: n/a - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2025-45766: n/a

Threats Tagged 'cve-2025-45766'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'cve-2025-45766'

Lead Pen Test Professional