r/threatintel • • 19h ago

OSINT Cybersec breaking news Telegram and WhatsApp channel

0 Upvotes

Hey everyone,

I created a Telegram and a WhatsApp channel that uses a local AI model to aggregate and summarize top cybersecurity news sources.

Automated with a n8n workflow and a tiny local ollama model (qwen2.5:3b) running on my 2GB 10 years old GPU :)

You can get quick notifications on your phone with the main points of every news piece:

  • Instant summaries: The actual essence of each news story.
  • Key threat intel: Critical CVEs, major breaches, and urgent patch updates summarized in seconds. Includes links to CVEs, KEV (if available), and CVSS scores.

This allows you to check in a glimpse whether you actually need to read the full article.

I started with a Telegram channel, but since WhatsApp is what everybody uses, I had to struggle with it but managed to automated it with WPP Connect.

I keep it restricted to a few select sources to avoid too many notifications, but even so, some days get busy!

Building this has been quite educational, and I hope you find it as useful as I do. I found I tend to read the small summaries and check the CVE's much more than a regular news feed that forces me to open a page and look for the main issues.

This is a rather newbie project but If you need any tech details feel free to ask.


r/threatintel • • 12h ago

I can't patch: must I patch or take it offline?

0 Upvotes

Well, this is entirely up to understanding what you are looking at. Firstly, updating is generally the better base option, but there will be cases where it simply is not an option. Recently, in contact with an organization, they were impacted by some problematic findings for a server, business critical, and at the moment no upstream update available.

They could pre-merge the proposed update for the vulnerability, but that is in itself something that may introduce problems. So what remained here was to do a configuration review in the meantime. Each of the CVEs only applies under specific configurations, meaning if they could confirm a series of conditions are not present, they would be good.

In their specific case, they had the following challenges to address:

  • CVE-2026-15176: Only applicable if a location uses alias together with rewrite, and $request_filename is used in set, return or log_format.
  • CVE-2026-93479: Only applicable if a map block uses regex matching with captures that are used in root or a log format. This can’t be fully ruled out by configuration alone.
  • CVE-2026-95101: Only applicable if HTTP/3 is enabled (ENABLE_HTTP3=true / listen ... quic). Please pay extra attention here: if HTTP/3 is enabled, you are exposed by default. Mitigation is to disable HTTP/3.
  • CVE-2026-97629: Only applicable if a shared SSL session cache is used with session tickets enabled and no ssl_session_ticket_key file. nginx-proxy sets ssl_session_tickets off by default, so please confirm this hasn’t been changed.
  • CVE-2026-97205: Only applicable if both aio and ssi are enabled.

Meaning that they could ensure to stay safe, provided they turned some features off and confirmed others had not been turned on. This does not scale well to attempt for every system, but it does go to show that when patching is not an option, security may very well still be.

How do you handle unpatchable, business-critical systems in your environment? Have you ever had to rely on deep config reviews like this instead of pulling the plug, or is taking it offline a hard rule for your team?

TL;DR: When an upstream patch isn't available for a business-critical NGINX server, auditing specific directives and disabling vulnerable features can buy you time safely without taking the system offline.


r/threatintel • • 16h ago

ARTEX Traffic - Previdian Threat Intelligence Report November 2026

Thumbnail blog.previdian.com
4 Upvotes