Cyber Rely Blog | Latest Cybersecurity Tips & Updates

CISA Emergency Directive 25-03: DevOps Tasks for Cisco 0-Day

Leave a Comment / Cybersecurity, KEV, Vulnerability & Threat Response / Zubayer A

CISA Emergency Directive 25-03: DevOps Tasks for Cisco 0-Day TL;DR (for dev & SRE leads): Turn CISA Emergency Directive 25-03 into a concrete, sprint-ready checklist: discover your Cisco edge, lock management planes, patch & reimage, rotate CI tokens, restrict runner egress, enforce mTLS to artifacts, gate builds on KEV network CVEs, and verify with config/state […]

CISA Emergency Directive 25-03: DevOps Tasks for Cisco 0-Day Read More »

npm supply chain attack 2025: ‘Shai-Hulud’ CI fixes

Leave a Comment / Vulnerability & Threat Response / Zubayer A

npm supply chain attack 2025: ‘Shai-Hulud’ CI fixes Developers are on the front line of the npm supply chain attack 2025 (the “Shai-Hulud” worm) that targets CI secrets and account tokens. This developer-first incident-response playbook shows exactly how to contain it in hours—not weeks—by enforcing trusted publishing, granular tokens, provenance checks, and safe build defaults

npm supply chain attack 2025: ‘Shai-Hulud’ CI fixes Read More »

Gate CI with CISA KEV JSON: Ship Safer Builds

Leave a Comment / KEV, Vulnerability & Threat Response / Zubayer A

Gate CI with CISA KEV JSON: Ship Safer Builds If you’re already generating SBOMs, you’re a 10-minute script away from turning CISA KEV JSON into a hard gate in CI/CD. The latest KEV additions—like the Chrome V8 type confusion vulnerability (CVE-2025-10585)—show how fast browser/JS engines move. Your pipeline should block risky versions on sight, not

Gate CI with CISA KEV JSON: Ship Safer Builds Read More »

Chrome V8 KEV: CVE-2025-10585 Deep Dive

1 Comment / CVE, Vulnerability & Threat Response / Zubayer A

Chrome V8 KEV: CVE-2025-10585 Deep Dive TL;DR (for engineering leaders) What CVE-2025-10585 is—and why it’s in KEV Impact paths to review Mitigation steps (patch, backport, harden) 1) Patch to fixed versions 2) Consider temporary hardening (risk-based) Electron example (main process): (Use only where user experience permits; track crashes/telemetry.) Screenshot of our Free Website Vulnerability Scanner

Chrome V8 KEV: CVE-2025-10585 Deep Dive Read More »

PyTorch Supply Chain Attack: Dev Guardrails

Leave a Comment / Vulnerability & Threat Response / Zubayer A

PyTorch Supply Chain Attack: Dev Guardrails Open-source registries remain hot targets. In September 2025, PyPI disclosed an attack campaign abusing GitHub Actions to exfiltrate PyPI tokens, and researchers flagged fresh malicious PyPI packages—reminders that ML stacks (including PyTorch projects) are squarely in scope. Lock everything with hashes, gate installs through a curated mirror, fail builds

PyTorch Supply Chain Attack: Dev Guardrails Read More »

CVE-2025-10585: Chrome Zero-Day Patch & Guardrails

Chrome 10585 Zero-Day: Patch & Guardrails

Leave a Comment / CVE, Vulnerability & Threat Response / Zubayer A

CVE-2025-10585: Chrome Zero-Day Patch & Guardrails What Google shipped—and why this RCE matters (confirm SBOM impact) Google’s stable channel shipped 140.0.7339.185/.186 on Sep 17, 2025, addressing four bugs—most urgently CVE-2025-10585, a V8 type-confusion vulnerability exploited in the wild. Type confusion enables memory corruption → potential arbitrary code execution via crafted JS/Wasm, so treat this as

Chrome 10585 Zero-Day: Patch & Guardrails Read More »

Git CVE-2025-48384: Safe Submodules in Practice

Leave a Comment / CVE, Vulnerability & Threat Response / Zubayer A

Git CVE-2025-48384: Safe Submodules in Practice This post is for engineers who live in Git: devs, SREs, CI owners. You’ll get the exact patched Git versions, how to check and enforce them across laptops and pipelines, plus guardrails to stop dangerous submodules from ever running code in your builds. TL;DR Explainer: CR/LF parsing → arbitrary

Git CVE-2025-48384: Safe Submodules in Practice Read More »

7 Best Fixes for Broken Access Control in Node.js

Leave a Comment / Node.js, Broken Access Control / Zubayer A

7 Best Fixes for Broken Access Control in Node.js Broken Access Control in Node.js is one of the most costly, sneaky issues a team can ship. It happens when users can act beyond their permissions—reading another tenant’s data, editing foreign records, downloading restricted files, or elevating roles. In this guide, we’ll demystify Broken Access Control

7 Best Fixes for Broken Access Control in Node.js Read More »

Security Misconfiguration in Node.js: 10 Best Fixes

10 Best Fixes for Security Misconfiguration in Node.js

Leave a Comment / Node.js, Security Misconfigurations / Zubayer A

Security Misconfiguration in Node.js — Risks, Examples & the 10 Best Fixes Security Misconfiguration in Node.js is one of the most common causes of avoidable incidents. From permissive CORS and verbose errors to weak session cookies and missing headers, tiny defaults can grow into big breaches. In this tutorial-style guide, you’ll learn how to find

10 Best Fixes for Security Misconfiguration in Node.js Read More »

Prevent Sensitive Data Exposure in Node.js: 10 Best Ways

10 Best Ways to Prevent Sensitive Data Exposure in Node.js

Leave a Comment / Node.js, Sensitive Data Exposure / Zubayer A

10 Best Ways to Prevent Sensitive Data Exposure in Node.js Sensitive Data Exposure in Node.js is one of those problems that sneaks in through small mistakes—an overly verbose error, a forgotten .env file pushed to Git, or a debug log that prints out access tokens. In this deep, hands-on guide you’ll learn practical steps (with

10 Best Ways to Prevent Sensitive Data Exposure in Node.js Read More »