16 Nov 2026 The Apache Software Foundation with Ruth Suehle
Open source sustainability requires treating the ecosystem as a community rather than a supply chain, with foundations addressing governance and security challenges.
More Open Source Security episodes

Published 1 Nov 2026
Duration: 29:34
AI enables mass discovery of unbackported open source vulnerabilities, outpacing under-resourced maintainers who struggle to fix them effectively.
Josh chat with Roi Nisimi about some research he's done into missing backport security fixes. Roi calls these Backport Gaps. The idea is looking for s...
Roey Nassimi, principal security researcher at Orca Security, describes his research into "backporting gaps" in open source projects. He found that maintainers frequently fix security vulnerabilities on the main branch but fail to cherry-pick those commits to the latest release, leaving the release vulnerable while the fix is publicly visible in Git history. He scanned the entire internet for these gaps and reports results "in the thousands," including a NEOVIM vulnerability with CVSS 8.8 that was fixed on main but absent from the latest release before he reported it.
The research began when a friend's self-hosted open source database platform was hacked. Investigating the project, Nassimi discovered multiple unbackported vulnerabilities in what he calls a "100k stars project," then scaled the search using AI to identify commits referencing GitHub security advisory IDs. He attributes the root cause to maintenance maturity: backporting is a manual practice, and many projects lack the automation or staffing to handle it reliably.
Nassimi also highlights the asymmetry between finding and fixing vulnerabilities in the AI era. Attackers can exploit CVEs before defenders are aware of them, while maintainers remain underfunded. He observes that AI-written patches are frequently "easily bypassed" and that many maintainers perceive the cost of releasing a patch as greater than the risk of leaving users exposed.
What if you audit your own project's Git history for unbackported security fixes before an attacker does?
What if you add a lightweight backport automation to your CI so security fixes never silently skip a release?
What if you publish a clear, low-friction vulnerability disclosure channel so reporters don't have to hunt you down?
Run a one-time audit of your project's Git history: search for commits that reference a GitHub security advisory ID on main and verify each one is present in the latest release tag. Nassimi's findings show that "most often the commit actually refers to a GitHub security advisory issue, GitHub security advisory ID," making this a concrete, scriptable check.
If you maintain a project, wire your backport label to an actual automation (e.g., a GitHub Action that opens a cherry-pick PR). Many projects "added a label, a backboard label that you can actually assign to the PR, but they never use it," so the label alone does nothing without a trigger.
Publish a GitHub security advisory or a dedicated security contact in your repository. Without one, Nassimi found it "near impossible" to reach maintainers, and reporters may default to public disclosure or give up entirely.
If you depend on open source libraries, check whether the version you pin includes the latest security fixes on the upstream main branch. A fix that is "public inside the Git history" but absent from your pinned release means you are exposed to a known vulnerability.
When reporting a vulnerability to a maintainer, include the specific commit hash, the GitHub advisory ID, and the affected release tag. Nassimi notes that the advisory reference in the commit is what made findings "really easy to actually see," so providing the same reference speeds up the maintainer's triage.
16 Nov 2026 The Apache Software Foundation with Ruth Suehle
Open source sustainability requires treating the ecosystem as a community rather than a supply chain, with foundations addressing governance and security challenges.
9 Nov 2026 Trusting your computing with Lance and Anton
Verifiable computing uses deterministic builds and hardware attestation to prove deployed software matches source code, mitigating supply chain attacks.
5 Oct 2026 Dependency attacks in 2026 with James Matchett
"Software supply chain security faces evolving risks like install-time attacks, transitive dependencies, and AI-generated threats, requiring proactive monitoring, dependency firewalls, and regulatory compliance to balance security with developer flexibility."
21 Sept 2026 The curl summer of Bliss with Daniel and Stefan
"Explored open-source security challenges, highlighting curl's 'Summer of Bliss' initiative to reduce maintainer burnout, the impact of AI-generated vulnerability reports, and the need for human expertise in security management, while advocating for sustainable practices in open-source development."
14 Sept 2026 CRA vulnerability reporting with Daniel Thompson
"Cyber Resilience Act imposes strict vulnerability reporting rules on manufacturers, raising concerns over inefficiency, ethical disclosures, and industry compliance challenges."