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

Microsoft Security Blog

Google Project Zero

Zero Day Initiative

Cisco Talos

Krebs on Security

Palo Alto Unit 42

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

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

Bleeping Computer

Reddit InfoSec News

The Hacker News

Dark Reading

AlienVault OTX Vulnerabilities

AlienVault OTX Malware

nltk

gptline

The NLTK TweetTokenizer in gptline is vulnerable to a denial of service caused by catastrophic regex backtracking in its URL matching regular expression. This flaw allows crafted input with many alternating label separators to cause exponential processing time, potentially stalling services that tokenize untrusted social media text. A fix bounding the label repetition was introduced in version 3.10.1.

The vulnerability (CVE-2026-72818) resides in the URLS regular expression within nltk/tokenize/casual.py, compiled into TweetTokenizer.WORD_RE and used by TweetTokenizer.tokenize. The regex contains an unbounded naked-domain branch with a domain-label prefix pattern that can be partitioned in exponentially many ways when given input with many alternating label separators. Because the regex requires a trailing top-level domain that crafted input lacks, the regex engine explores all partitions before failing, causing severe CPU consumption and denial of service. The HANG_RE substitution does not mitigate this. This affects services applying TweetTokenizer or casual_tokenize to untrusted text. Version 3.10.1 introduced bounding of label repetition to fix the issue.

Detailed information about The URLS regular expression in nltk/tokenize/casual.py, compiled into TweetTokenizer.WORD_RE and applied by TweetTokenizer.tokenize, 

The URLS regular expression in nltk/tokenize/casual.py, compiled into TweetTokenizer.WORD_RE and applied by TweetTokenizer.tokenize, contains a… (CVE-2026-72818) - Live Threat Intelligence - Threat Radar | OffSeq.com

Gptline: NLTK TweetTokenizer vulnerable to denial of service through catastrophic regex backtracking (CVE-2026-72818)

Threats Tagged 'brew-gptline-cve-2026-72818'

Stop chasing alerts. Route them.

Check if your credentials are on the dark web

Filter Threats

Threats Tagged 'brew-gptline-cve-2026-72818'

Lead Pen Test Professional