ThreatNote Briefing #2 – DPDPA’s Real Problem, and This Week’s Wire

ThreatNote Briefing | Week of May 18–24, 2026
Weekly intelligence for Indian cybersecurity practitioners.

Weekly intelligence for Indian cybersecurity practitioners. | Week of May 18–24, 2026


One original piece this week. A short Wire curation below. No filler.


📌 From the Desk

DPDPA Is Not About Tools. It Is About Lawful Processing.

This is the second piece in ThreatNote’s DPDPA series and it takes a different angle from the first. Where the previous piece covered operational readiness gaps, this one goes upstream — to the question most organizations haven’t asked yet: should this personal data even be processed in the first place?

The piece covers three things practitioners don’t hear enough: why strong cybersecurity maturity does not automatically translate into privacy maturity, why DPIAs are architecture reviews not paperwork, and why “internal” does not automatically mean “safe.” The closing distinction between operational maturity and expensive privacy theatre is the one worth sharing with your leadership.

If you missed the first piece — Six Months Into India’s DPDPA Timeline: Why Many Organizations Still Aren’t Operationally Ready — read both together. They’re designed to be complementary.

→ Read: DPDPA Is Not About Tools

→ Read: Six Months Into India’s DPDPA Timeline


🔌 Wire Highlights — Signals Worth Watching

⚠ CVSS 10.0 · Actively Exploited

CVE-2026-20182 — Cisco Catalyst SD-WAN Controller Auth Bypass

Still the most critical signal on the Wire. Authentication bypass granting full admin access. Confirmed active exploitation. If this didn’t get patched after last week’s briefing, it needs to now.

→ Read on ThreatNote Wire

Supply Chain

node-ipc Stealer Backdoor — 3 Versions Confirmed Malicious

Carrying this forward from last week because supply chain compromises don’t resolve themselves. Three versions of node-ipc confirmed targeting developer secrets. If you have node-ipc in your dependency tree and haven’t audited, that’s still open exposure.

→ Read on ThreatNote Wire

RCE · Developer Tooling

CVE-2026-45035 & CVE-2026-45038 — Tabby Terminal: Two RCE Paths in One Release

Two separate code execution paths fixed in Tabby 1.0.233 — one via a system-wide URL scheme handler, one via file drag-and-drop. Two CVEs in the same tool in the same release is worth reading as a pattern, not just as individual bugs. Terminal emulators sitting outside standard patch cycles in developer environments are an underappreciated attack surface. Fixed in 1.0.233.

→ CVE-2026-45035: RCE via URL Scheme

→ CVE-2026-45038: RCE via File Drop

Auth · JWT Forgery

CVE-2026-44699 — LibJWT: Algorithm Confusion Allows JWT Forgery

RSA JWK without an alg parameter accepted as empty-key HMAC — classic algorithm confusion leading to JWT forgery. Affects LibJWT 3.0.0 through 3.3.2. If you have any service doing JWT validation in that version range, token integrity cannot be assumed. Worth checking your authentication stack.

→ Read on ThreatNote Wire

AI/ML · RCE

CVE-2026-44827 — Diffusers: trust_remote_code Safeguard Bypass

Hugging Face Diffusers 0.37.0 allows remote code execution without the trust_remote_code=True safeguard when loading pipelines. If your team is running AI/ML pipelines using Diffusers — in any environment, including development and staging — patch to 0.38.0. The safeguard existing in the first place is the tell: this class of risk is expanding alongside ML tooling adoption.

→ Read on ThreatNote Wire


📊 This Week

  • Original analysis pieces: 1
  • Wire entries this week: 35+
  • Total Wire posts to date: 76
  • Site views since counter reset: 18,429

The Briefing goes out every Monday at 10 AM IST. No vendor pitches. No awareness-month content. No AI-generated summaries dressed up as research.

If this is useful, forward it to one practitioner who should be reading it.

threatnote.substack.com  |  threatnote.com


ThreatNote — Security research. Operational reality. Hacker culture.

The views and opinions expressed are personal and belong solely to the author. They do not represent the views of any employer, organization, or affiliated entity.