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

Community Curated

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

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

NCSC UK

JVN Japan

GCP Compute Engine Security

GCP Kubernetes Security

AWS Security Bulletins

CERT/CC

Tenable Research

Microsoft Security Blog

Google Project Zero

Cisco Talos

Zero Day Initiative

Palo Alto Unit 42

Krebs on Security

Kaspersky Security Blog

Check Point Research

GCVE Database

Bleeping Computer

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

pymanager

pymanager included the current working directory in sys.path meaning modules could be shadowed by modules in the current working directory. As a result, if a user executes a pymanager-generated command (e.g., pip, pytest)
 from an attacker-controlled directory, a malicious module in that 
directory can be imported and executed instead of the intended package.

CVE-2026-5271 identifies a vulnerability in the Python Software Foundation's pymanager package, specifically related to the inclusion of the current working directory (CWD) in the sys.path module search path. In Python, sys.path determines the order in which modules are searched and loaded. By including the CWD, pymanager allows modules located in the current directory to shadow or override standard library or installed modules. This can lead to a situation where an attacker with the ability to place a malicious module in the working directory causes pymanager to load that malicious module instead of the legitimate one. The vulnerability is classified with a CVSS 4.0 base score of 5.6 (medium severity), reflecting that exploitation requires local access (AV:L), low attack complexity (AC:L), no privileges (PR:N), but user interaction (UI:A) is needed. The impact primarily affects integrity (VI:H), with no direct impact on confidentiality or availability. The vulnerability does not require authentication but does require the user to execute or interact with the vulnerable environment. No patches or known exploits are currently reported. This vulnerability is particularly relevant in environments where pymanager is used in development or runtime contexts where the working directory is not tightly controlled, such as shared or multi-user systems, or automated build and deployment pipelines.

Detailed information about CVE-2026-5271: Vulnerability in Python Software Foundation pymanager affecting Python Software Foundation pymanager. Get real-time up

CVE-2026-5271: Vulnerability in Python Software Foundation pymanager - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2026-5271: Vulnerability in Python Software Foundation pymanager

Threats Tagged 'cve-2026-5271'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'cve-2026-5271'

Lead Pen Test Professional