The Fix Window

Safeguard

A weekly vulnerability and zero-day podcast for AppSec, DevSecOps and security teams. Each episode covers recent CVE and KEV news, an exploit explained, vulnerability management, patching and remediation, SBOM, SCA, open source security and software supply chain security. Topics: zero-day, CVE, exploit, container security, patch management. Learn more at safeguard.sh.

Episodes

  1. Oct 29

    Three days: how fast to patch a bug that is already being used

    A message lands on a Monday: a flaw in something you run has just been added to the known exploited list. You used to have three weeks. Now you may have three days. Mira and Cal explain how CISA's BOD 26-04, issued in June 2026, replaced one patch deadline with four facts: is the asset exposed to the internet, is the flaw on the KEV catalog, can an attacker automate the exploit, and does it give partial or total control. They cover what forensic triage means, the permission to wait at the bottom of the table, and how a private team can borrow the idea for vulnerability prioritisation: a fast lane for exploited flaws on exposed assets, a CI gate on known exploited CVEs, and honest risk acceptance. It is a practical episode on vulnerability management and patch management for AppSec and DevSecOps teams: how CVSS, EPSS and KEV fit together, why reachability and a software inventory (an SBOM) decide how fast you can do remediation, and what to say to a federal customer who asks about your patch SLA. In the news, in October: two exploited flaws added to the KEV catalog on 27 October, PolyShell in Adobe Commerce and Magento and a Brotli decoder flaw bundled in Node.js, and why their federal due date was fourteen days when two PHP flaws added the day before got three days plus a compromise check. Theo explains why to keep your old deadlines as a baseline, and the episode ends with six things to do this week. Topics: BOD 26-04, CISA KEV, forensic triage, CVSS, EPSS, CVE, exploit, Node.js, Brotli, Adobe Commerce, Magento, PolyShell, PHP, vulnerability prioritisation, CI gate, software supply chain security, open source security Chapters 00:00 Cold open00:36 Intro01:00 News: two exploited flaws, two due dates03:41 What changed: the day the 21 day clock went away06:03 Deep dive: four facts, a fast lane and a floor09:32 Practitioner corner (Theo)10:23 Fix it this week11:35 OutroLinks SafeguardBOD 26-04: the deadlines and forensic triage, explainedShould a CI gate block on known exploited vulnerabilities?Can you accept risk on a known exploited vulnerability?Free scan (Gold Open Source, no login)Full dated source list: see the show notes.

    Three days: how fast to patch a bug that is already being used
  2. Oct 28

    The Fix Window, Ep 2: Your AI coding agent is a new log source

    In August 2025, malicious releases of the nx build tool on npm ran a postinstall script that looked for AI coding CLIs on the developer's machine, launched them with their permission bypass flags, and asked them to hunt for wallets, SSH keys, .env files and credentials. The agents did what their flags allowed, and unless someone had turned on the agents' telemetry, there was no central record of what they were told or what they ran. Mira and Cal walk through the incident and why a process list alone can't tell an agent's work from an intruder's. Then the practical part for platform engineers and AppSec leads: what a coding agent actually does on a developer machine, what OpenTelemetry and OTLP are in plain words, which Claude Code and Codex events matter (tool decisions, and whether a person or a setting approved them), why prompt text should stay out by default, how managed settings stop developers redirecting telemetry, and how to stream it, plus Claude organization activity, into one place that someone reviews. Theo answers which agent actions to log at all, and the episode ends with five things to do this week. For platform engineers and AppSec teams worried about AI coding agent security: how Claude Code and Codex activity becomes an audit trail through OpenTelemetry (OTLP), what to watch when a malicious npm package abuses agent permissions, how MCP and managed settings fit in, and how to review agent activity for compliance and incident response. Chapters00:00 Cold open00:31 Intro01:06 The incident: malware that put the coding agent to work04:49 Deep dive: agent telemetry, from the laptop to a reviewer12:35 Practitioner corner13:38 Fix it this week15:20 Outro Sources (published Safeguard research)Send Claude Code and Codex telemetry to Safeguard with OpenTelemetry (OTLP) (the episode's main guide): https://safeguard.sh/resources/blog/send-claude-code-and-codex-telemetry-to-safeguard-with-opentelemetry-otlp?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep02Stream Claude audit and compliance activity into Safeguard: https://safeguard.sh/resources/blog/stream-claude-audit-and-compliance-activity-into-safeguard?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep02Find and connect Safeguard from the official MCP Registry: verify the publisher and connect your assistant: https://safeguard.sh/resources/blog/find-and-connect-safeguard-from-the-official-mcp-registry-verify-the-publisher-and-connect-your-assistant?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep02Safeguard MCP and frontier AI integrations: https://safeguard.sh/mcp?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep02Nx npm package AI coding agent weaponization: https://safeguard.sh/resources/blog/nx-npm-package-ai-coding-agent-weaponization?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep02Nx build system s1ngularity supply chain attack (2025): https://safeguard.sh/resources/blog/nx-build-system-s1ngularity-supply-chain-attack-2025?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep02 LinksSafeguard: https://safeguard.sh/?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep02More episodes: https://open.spotify.com/show/03400iIvo19RZbfRDfPECc The script was written by the Safeguard team and checked against our published research. Learn more at safeguard.sh. Topics: AI coding agents, Claude Code, Codex, OpenTelemetry, OTLP, MCP, MCP security, nx npm supply chain attack, malicious npm package, postinstall script, agent permissions, credential theft, audit trail, incident response, DevSecOps, agent security.

    The Fix Window, Ep 2: Your AI coding agent is a new log source
  3. Oct 28

    The Fix Window, Ep 1: A zero-day has no CVE

    A zero-day has no CVE record, no advisory and usually no fix, so a scanner that only matches your software against public feeds has nothing to match. Mira and Cal walk through why, using the September 2023 libwebp heap overflow: exploited in a zero-click spyware chain before any CVE existed, first filed as a Chrome bug, later rescored from high to critical, and buried inside browsers, Electron apps and mobile apps that many teams did not know they shipped. Then the practical part. How to detect what nobody has catalogued (static analysis with dataflow for your own code, a validated research pipeline for open source), how to rank a finding with no exploit score, why the fix should be a tested pull request that ships switched off until you turn it on, and what to do when upstream has no fix at all. Theo answers how to justify dropping everything for a zero-day, and the episode ends with six things a team can do this week. If you triage vulnerabilities for a living, this is a plain-English look at zero-day vulnerability management: why CVE and KEV based patching, SBOM matching and scanning miss an exploit nobody has catalogued yet, how to prioritise a vulnerability without an exploit score (EPSS and reachability analysis), and how remediation can ship as a tested fix for open source dependencies without waiting for upstream. Written for AppSec, DevSecOps and platform teams working on software supply chain security. Chapters00:00 Cold open00:32 Intro01:01 The incident: why a zero-day leaves scanners blind05:48 Deep dive: the loop, and fixing without waiting for upstream12:36 Practitioner corner13:48 Fix it this week15:32 Outro Sources (published Safeguard research)Autonomous Novel Vulnerability Detection and Elimination at Scale (the episode's main guide): https://safeguard.sh/resources/blog/autonomous-novel-vulnerability-detection-and-elimination-at-scale-zero-day-discovery-autonomous-remediation-and-gold-open-source?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep01libwebp heap buffer overflow zero-day (CVE-2023-4863): https://safeguard.sh/resources/blog/libwebp-heap-buffer-overflow-zero-day-cve-2023-4863?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep01CVE-2023-4863: The libwebp Zero-Day That Hit Chrome and More: https://safeguard.sh/resources/blog/cve-2023-4863-the-libwebp-zero-day-explained?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep01When Upstream Won't Fix It: Fork and Patch, Explained Honestly: https://safeguard.sh/resources/blog/fork-and-patch-vulnerable-packages?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep01 LinksSafeguard: https://safeguard.sh/?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep01Gold Open Source (free, no login): https://gold.safeguard.sh/?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep01Safeguard blog: https://safeguard.sh/blog?utm_source=podcast&utm_medium=audio&utm_campaign=the-fix-window&utm_content=ep01More episodes: https://open.spotify.com/show/03400iIvo19RZbfRDfPECc The script was written by the Safeguard team and checked against our published research. Learn more at safeguard.sh. Topics: zero-day vulnerability, CVE-2023-4863, libwebp, WebP, Chrome, Electron, heap buffer overflow, zero-click exploit, spyware, Citizen Lab, CISA KEV, NIST NVD, vulnerability management, vulnerability prioritisation, remediation, fork and patch, SBOM, SCA, static analysis, open source security, software supply chain security, AppSec, DevSecOps, EPSS, reachability analysis, Safeguard Gold.

    The Fix Window, Ep 1: A zero-day has no CVE
  4. Oct 28

    The Fix Window, Ep 3: What an AI vendor's filing tells your risk review

    In the news, in October: two sets of flaws that CISA added to its Known Exploited Vulnerabilities catalog. Two PHP flaws nicknamed php2shell that allow unauthenticated remote code execution, and flaws in Collabora Online and Arista's VeloCloud Orchestrator. Mira and Cal cover what the public sources say, what is not known, and how to find every place PHP hides, patch the internet-facing systems first and check Nextcloud for web shells. Then a vendor story. In October a large IT services company said a subcontractor it uses for development and maintenance had been attacked, and that the subcontractor's legitimate accounts were then used against its customers. Two universities came forward with two very different failures: ransomware on a core platform, reached through a maintenance account, and a leak of personal data affecting about 78,000 people from a vendor's cloud storage that held files from finished work, shared with a partner the university had never been told about. Then the deep dive. A large AI lab filed its S-1 in late October, and its risk factors are more candid than any trust portal. Cal shows how to read a filing for security-relevant facts, how to separate boilerplate from things that already happened, and how to turn dated disclosures into vendor questions on data retention, agents, SBOMs, model withdrawal and incident notice. Theo answers what to ask an AI vendor before approving a tool, and the episode ends with five things to add to your vendor intake. If you run vendor risk management or third-party risk, this episode covers how to read an AI vendor's filing for your risk review, what to ask for in a security questionnaire, how to request and validate an SBOM, how to keep an AI-BOM, and how to handle vulnerability management and patch management when CISA adds exploited flaws to its KEV catalog. It also covers software supply chain security, subcontractor risk and prompt injection in AI agents. 00:00 Cold open, 00:32 Intro, 00:40 In the news, 03:32 The incident, 07:35 Deep dive, 15:25 Practitioner corner, 16:38 Fix it this week, 18:23 Outro. Sources S-1 guide Incident CISA PHP alert CISA KEV News Topics: vendor risk management, third-party risk, TPRM, SBOM, AI-BOM, security questionnaire, CISA KEV, CVE-2026-109618, CVE-2026-109619, CVE-2026-110447, CVE-2026-114625, PHP, Nextcloud, patch management, software supply chain security, prompt injection, S-1 filing.

    The Fix Window, Ep 3: What an AI vendor's filing tells your risk review
  5. Oct 28

    The Fix Window, Ep 4: SOC 2 for startups: what auditors ask for first

    A short one for anyone who has just been asked for a SOC 2 report. A big customer has sent a form that says "SOC 2 Type 2 report, yes or no", and there is no security team to hand it to. Mira and Cal start with a story from the auditors' own profession: in May 2026 the AICPA told peer reviewers to watch for SOC 2 engagements with identical reports, risk assessments, sample sizes and testing procedures. They explain why that matters when you pick your first CPA firm, and why only a licensed CPA firm can issue the report. Then the practical part. What a Type 1 and a Type 2 are, how long the observation window runs, and the populations an auditor asks for first: leavers and account removal dates, joiners and approvals, production changes and reviews. How to run an access review that holds up, why fewer policies beat a template pack, what to tell a buyer when you have no report yet, and how an answer bank and a trust center speed up the next review. Theo answers whether a Type 1 is enough for your first deals, and the episode ends with five things to do this week. If your startup needs SOC 2 for the first time, this episode covers what a SOC 2 auditor asks for first, how SOC 2 Type 1 and Type 2 differ, how long the observation window runs, and what evidence to keep. We also cover the AICPA peer review alert, what to ask a CPA firm before you sign, how to answer a security questionnaire without a report, and what belongs in a trust center. 00:00 Open, 00:28 Intro, 00:57 Incident, 03:28 Deep dive, 10:29 Corner, 11:43 Checklist, 12:53 Outro. Sources AICPA alert Evidence Window length Timeline After Type 1 Access reviews Policies No report yet Answer bank Trust center SOC 2 page Topics: SOC 2, SOC 2 Type 1, SOC 2 Type 2, observation window, auditor, CPA firm, AICPA peer review, evidence, access review, trust center, security questionnaire.

    The Fix Window, Ep 4: SOC 2 for startups: what auditors ask for first

About

A weekly vulnerability and zero-day podcast for AppSec, DevSecOps and security teams. Each episode covers recent CVE and KEV news, an exploit explained, vulnerability management, patching and remediation, SBOM, SCA, open source security and software supply chain security. Topics: zero-day, CVE, exploit, container security, patch management. Learn more at safeguard.sh.