<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/handling-vulnerability-reports-recipe-card-n1e4fjzin" -->

---
title: Handling vulnerability reports: Recipe card | daily.dev
description: A practical, step-by-step guide from CNCF's TAG Security for maintainers of small and medium open source projects on handling vulnerability reports, framed as...
canonical: https://daily.dev/posts/handling-vulnerability-reports-recipe-card-n1e4fjzin
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Handling vulnerability reports: Recipe card | daily.dev
og:description: A practical, step-by-step guide from CNCF's TAG Security for maintainers of small and medium open source projects on handling vulnerability reports, framed as...
og:url: https://daily.dev/posts/handling-vulnerability-reports-recipe-card-n1e4fjzin
og:image: https://api.daily.dev/og/posts/n1E4fJZin.png
og:image:alt: Handling vulnerability reports: Recipe card
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Handling vulnerability reports: Recipe card

**[CNCF](https://daily.dev/sources/cncf)** · 8 min read · 0 upvotes · 0 comments

## Summary

A practical, step-by-step guide from CNCF's TAG Security for maintainers of small and medium open source projects on handling vulnerability reports, framed as a cooking recipe. It covers setting up a clear reporting path via README.md and SECURITY.md, triaging whether a report is a genuine vulnerability, managing an embargo with minimal trusted people, developing and testing patches privately, and coordinating a public release with a CVE disclosure within roughly 90 days. Links to GitHub's private vulnerability reporting feature and the OpenSSF vulnerability disclosure guide for larger projects.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.cncf.io/blog/2026/09/07/handling-vulnerability-reports-recipe-card>

## Questions this post answers

### How long after receiving a vulnerability report should an open source project publish the disclosure and patch?

It is generally considered best practice to publish a patch and public disclosure within 90 days of receiving the vulnerability report. Coordinating the release and the CVE announcement to happen at the same time gives all users the fix simultaneously, avoiding a window where attackers know about the flaw before users can patch.

_daily.dev surfaces security process guidance for maintainers coordinating disclosure timelines and patch releases._

### Where should an open source project document how to report a security vulnerability?

Include a security section directly in the README.md, or point readers to a SECURITY.md file placed at the root of the repository. That file should specify the threat model, where to report (such as GitHub's private vulnerability reporting or a private email list), the expected report format, response and disclosure timelines, and any bug bounty policy.

_maintainers setting up a security policy can track best practices like this on daily.dev._

### Who assigns a CVE number for an open source vulnerability?

A CVE number must be assigned by a CNA, a CVE Numbering Authority. GitHub is itself a CNA and can assign a CVE number directly from its private vulnerability reporting UI, or a maintainer and reporter can report to any other listed CNA. Once published, the CVE gets added to OSV and other vulnerability databases so it appears in users' scans.

_developers tracking CVE workflows and disclosure tooling can follow updates on daily.dev._

## Similar posts on daily.dev

- [Do excellent vulnerability reports](https://daily.dev/posts/do-excellent-vulnerability-reports-okekhmxxc) · daniel.haxx.se · 2 upvotes · 0 comments
- [Securing GitHub Actions CI dependencies: Recipe card](https://daily.dev/posts/securing-github-actions-ci-dependencies-recipe-card-ttkzb5tpj) · CNCF · 0 upvotes · 0 comments
- [Structured forms for private vulnerability reports](https://daily.dev/posts/structured-forms-for-private-vulnerability-reports-uzdwl315v) · GitHub Changelog · 0 upvotes · 0 comments
- [Practical Package Security: The Unofficial Guide](https://daily.dev/posts/practical-package-security-the-unofficial-guide-a1efmte4m) · Tech Lead Digest · 1 upvotes · 0 comments
- [A year of open source vulnerability trends: CVEs, advisories, and malware](https://daily.dev/posts/a-year-of-open-source-vulnerability-trends-cves-advisories-and-malware-xirztt4ff) · GitHub Blog · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#open-source](https://daily.dev/tags/open-source), [#github](https://daily.dev/tags/github)

[View this post on daily.dev](https://daily.dev/posts/handling-vulnerability-reports-recipe-card-n1e4fjzin)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Handling vulnerability reports: Recipe card","url":"https://daily.dev/posts/handling-vulnerability-reports-recipe-card-n1e4fjzin","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/handling-vulnerability-reports-recipe-card-n1e4fjzin"},"datePublished":"2026-09-07T11:34:39.721Z","dateModified":"2026-09-07T15:14:51.031Z","description":"A practical, step-by-step guide from CNCF's TAG Security for maintainers of small and medium open source projects on handling vulnerability reports, framed as...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d690799313d512493409efd3a03be111?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d690799313d512493409efd3a03be111?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"CNCF","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"CNCF","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/55536a03390741eebd96d2f9b74d2d8d","url":"https://daily.dev/sources/cncf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/handling-vulnerability-reports-recipe-card-n1e4fjzin","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,open-source,github","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"CNCF","item":"https://daily.dev/sources/cncf"},{"@type":"ListItem","position":3,"name":"Handling vulnerability reports: Recipe card"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/handling-vulnerability-reports-recipe-card-n1e4fjzin#faq","mainEntity":[{"@type":"Question","name":"How long after receiving a vulnerability report should an open source project publish the disclosure and patch?","acceptedAnswer":{"@type":"Answer","text":"It is generally considered best practice to publish a patch and public disclosure within 90 days of receiving the vulnerability report. Coordinating the release and the CVE announcement to happen at the same time gives all users the fix simultaneously, avoiding a window where attackers know about the flaw before users can patch. daily.dev surfaces security process guidance for maintainers coordinating disclosure timelines and patch releases."}},{"@type":"Question","name":"Where should an open source project document how to report a security vulnerability?","acceptedAnswer":{"@type":"Answer","text":"Include a security section directly in the README.md, or point readers to a SECURITY.md file placed at the root of the repository. That file should specify the threat model, where to report (such as GitHub's private vulnerability reporting or a private email list), the expected report format, response and disclosure timelines, and any bug bounty policy. maintainers setting up a security policy can track best practices like this on daily.dev."}},{"@type":"Question","name":"Who assigns a CVE number for an open source vulnerability?","acceptedAnswer":{"@type":"Answer","text":"A CVE number must be assigned by a CNA, a CVE Numbering Authority. GitHub is itself a CNA and can assign a CVE number directly from its private vulnerability reporting UI, or a maintainer and reporter can report to any other listed CNA. Once published, the CVE gets added to OSV and other vulnerability databases so it appears in users' scans. developers tracking CVE workflows and disclosure tooling can follow updates on daily.dev."}}]}
```

