More Open Source Security episodes

Finding missing security backports with Roi Nisimi thumbnail

Finding missing security backports with Roi Nisimi

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.

Episode Description

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...

Overview

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

  • What if you audit your own project's Git history for unbackported security fixes before an attacker does?

    • Move: Propose a script that diffs commits referencing a GitHub security advisory ID on main against the latest release tag, flagging gaps. Nassimi notes "most often the commit actually refers to a GitHub security advisory issue, GitHub security advisory ID," making that reference a concrete matching point.
    • Why Now? Attackers are already scanning at scale; Nassimi reports "the results are in the thousands" across the internet, and "attackers can now exploit CVEs before defenders know there's even a CVE to defend against."
    • Expected Upside: You may close a gap that would otherwise sit exposed. Cherry-picking the fix and tagging a patch release removes a publicly visible vulnerability from your project.
  • What if you add a lightweight backport automation to your CI so security fixes never silently skip a release?

    • Move: Propose a label-triggered workflow that, when a PR is tagged with a security-advisory label, opens a cherry-pick PR against the latest release branch. Nassimi notes many projects "added a label, a backboard label that you can actually assign to the PR, but they never use it," so wiring the label to an actual action is the missing step.
    • Why Now? Backporting is "in and of itself a manual practice," and underfunded projects are most likely to skip it. A small automation removes the human step Nassimi identifies as the root cause.
    • Expected Upside: Future security fixes propagate to release branches without relying on a maintainer remembering, reducing the window users are exposed to a known, publicly documented vulnerability.
  • What if you publish a clear, low-friction vulnerability disclosure channel so reporters don't have to hunt you down?

    • Move: Propose adding a GitHub security advisory template or a dedicated security@ address to your README and SECURITY.md. Nassimi calls the reporter experience without one "a complete nightmare," with LinkedIn and email going unanswered for "decades."
    • Why Now? AI has made it easy for many to find backporting gaps; "everyone can research vulnerabilities" now. Without an easy contact path, a reporter may open a public issue or remain silent while the gap persists.
    • Expected Upside: You gain early, private notice of gaps, giving you time to patch before the information becomes public or is exploited.

Takeaway

  • 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.

Recent Episodes of Open Source Security

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."

More Open Source Security episodes