Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

CVE-2026-23745: A Deep Dive into the node-tar Arbitrary File Overwrite Vulnerability

CVE-2026-23745 is a high-severity path traversal flaw in node-tar (the tar library for Node.js). Versions ≤7.5.2 fail to sanitize linkpath in hardlink and symlink entries when preservePaths is false (default secure mode). Malicious tar archives bypass extraction root restrictions, enabling arbitrary file overwrite via hardlinks and symlink poisoning via absolute targets. Discovered January 2026, patched in 7.5.3. Impacts npm ecosystems, CI/CD pipelines, and apps extracting untrusted archives.

Why Vulnerability Management Falls Short - And How Exposure Management Fixes It

Vulnerability management identifies weaknesses. Exposure management helps prioritize them based on real-world risk and context. Ed and Garrett unpack why traditional vulnerability programs struggle to drive real risk reduction. The challenge isn’t discovery. It’s prioritization and follow-through. Too often, vulnerabilities are treated as isolated IT tasks—handed off, tracked by SLAs, and stripped of the context that explains why they matter in the first place.

Top 3 Skills for AI Security in 2026 #shorts

Are your cybersecurity skills ready for the AI era? In this clip, we reveal which traditional security frameworks still work and the one new mental shift you need to survive. It’s not just about code anymore—it’s about "Socio-Technical" thinking. Raji (Microsoft AI Security) breaks down exactly how to future-proof your career.

ITSP / StudioC60 features Memcyco in latest podcast.

Real-Time Defense Against AI-Driven Account Takeover: How Memcyco Protects Organizations and Their Customers Memcyco recently featured in an ITSP Magazine podcast episode snippet, which this post is based on. You can listen to the full feature here. Our thanks go to the podcasters for having our CEO, Israel Mazin, on with them.

HIPAA Incident Response Plan for Website PHI Leaks

Traditional HIPAA response plans were built for the incidents everyone can picture, like a compromised server, ransomware in the network, or unauthorized access to a clinical database. But website PHI leaks are different altogether. Often, there’s no attacker and no break-in. The leak comes from authorized tracking pixels or third-party analytics scripts simply collecting and sending data as designed, but on pages where it should never touch patient information in the first place.

Understanding Open-Source License Risk in Modern Software

Open source is one of the best things to ever happen to software development. It is also one of the easiest ways to accidentally ship legal obligations you did not sign up for. Most teams know they rely heavily on open-source dependencies. Fewer teams know exactly what licenses those dependencies use, what obligations come with them, or how those licenses travel through transitive dependencies and container images. That gap is what we call open-source license risk.

Testing MiniMax M2.1 for AI Coding: The Results Might Surprise You

Can "lesser-known" AI models actually keep up with the giants like Google, OpenAI, and Anthropic? In today’s video, we put MiniMax M2.1 to the ultimate test: building a production-ready, secure Node.js note-taking application from a single prompt. We’ll explore how to access MiniMax natively in the Windsurf IDE, walk through the debugging process for common errors (like environment variables and OS-specific dependencies), and perform a deep-dive security audit using Snyk. Stick around until the end to learn how to integrate MiniMax M2.1 into VS Code using OpenRouter.

AI Strategy: Building a Future-Proof Framework

Artificial intelligence (AI) adoption is fast becoming a strategic necessity for modern businesses. With adoption continuing at pace, a carefully considered strategy is essential for gaining or maintaining a competitive advantage, managing downside risk and addressing the continued regulatory, legal, ethical and operational complexities presented by AI.

How we mitigated a vulnerability in Cloudflare's ACME validation logic

On October 13, 2025, security researchers from FearsOff identified and reported a vulnerability in Cloudflare's ACME (Automatic Certificate Management Environment) validation logic that disabled some of the WAF features on specific ACME-related paths. The vulnerability was reported and validated through Cloudflare’s bug bounty program. The vulnerability was rooted in how our edge network processed requests destined for the ACME HTTP-01 challenge path (/.well-known/acme-challenge/*).