The purpose of this blog is to establish a dialogue and get your input on issues and topics important to CVE. We encourage you to use Medium , LinkedIn , or Twitter to comment on, share, or like a post. Right-click and copy a URL to share a post from this website.

Featured

• We Speak CVE Podcast: Managing Modernization and Automation Changes in the CVE Program

Recent

• Our CVE Story: Leading the Way for Vulnerability Disclosures in Physical Security Systems (guest author)
• CVE Program Report for Q2 Calendar Year 2021
• We Speak CVE Podcast: How the New CVE Record Format Is a Game Changer
• Our CVE Story: JPCERT/CC (guest author)
• CVE Program Expands Partnership with Spanish National Cybersecurity Institute (INCIBE)
• We Speak CVE Podcast: Engaging with CVE’s Automated CNA Services
• Our CVE Story: From Robot Security Research to Managing Robot Vulnerabilities (guest author)
• “ CVE Global Summit – Spring 2021 ”
• Chandan Nandakumaraiah of Palo Alto Networks Joins CVE Board
• We Speak CVE Podcast: Interview with Larry Cashdollar A Researcher’s Perspective
• CVE Program Report for Q1 Calendar Year 2021
• Our CVE Story: An Open-Source, Community-Based Example (guest author)
• We Speak CVE Podcast: Partnering with the CVE Program
• My CVE Story: How I Became the CVE Program’s First Vulnerability Researcher CNA (guest author)
• We Speak CVE Podcast - How MongoDB Manages Its CVEs
• Ken Munro of Pen Test Partners Joins CVE Board
• Our CVE Story: Learning to Embrace Recognition and Mitigations of Vulnerabilities as a Strength (guest author)
• Introducing the “We Speak CVE” Podcast! – Episode 1: How CVE, CISA, and NIST work together to manage vulnerabilities
• CVE Program Report for Q4 Calendar Year 2020
• 2020
• Our CVE Story: Using the CVE Program to Provide Reliable Vulnerability Information (guest author)
• CVE Program Terminology Updated: “CVE Record,” “Top-Level Root,” & More
• Our CVE Story: The Gift of CVE (guest author)
• Our CVE Story: CVE IDs for Simplifying Vulnerability Communications (guest author)
• CVE Program Report for Calendar Year Q3-2020
• Our CVE Story: Ancient History of the CVE Program – Did the Microsoft Security Response Center have Precognition (guest author)
• CVE Program Partners with Cybersecurity & Infrastructure Security Agency to Protect Industrial Control Systems and Medical Devices
• Our CVE Story: Rapid7 (guest author)
• Process for Assigning CVE IDs to End-of-Life (EOL) Products
• CVE Program Report for Calendar Year Q2-2020
• Our CVE Story: Bringing Our ZDI Community to the CVE Community (guest author)
• CVE Program Report for Calendar Year Q1-2020
• CNA Rules, Version 3.0 Now in Effect
• CVE Program Report for Calendar Year Q4-2019
• CNA Rules, Version 3.0 Coming Soon
• 2019
• CVE Program Report for Calendar Year Q3-2019
• Become a CNA to Assign Your Own CVE IDs
• CVE Working Groups Overview
• Refresher: When to Use the CVE Request Web Form
• 2018
• A Look at the CVE and CVSS Relationship
• Come Meet with CVE at Black Hat 2018 / DEF CON 26 on August 9
• CNA Processes Documentation Now on GitHub
• CNA Rules, Version 2.0 Now in Effect
• 2017
• CNA Rules, Version 2.0 to Take Effect on January 1st
• Become a CNA
• Come Meet with CVE at Black Hat 2017 on July 27 and DEF CON 25 on July 28
• Why is a CVE Entry marked as "RESERVED" when a CVE ID is being publicly used?
• Now you can easily comment on CVE Blog posts using our new "CVE-CWE-CAPEC" page on LinkedIn
• Summary of your feedback about updating info in CVE ID Descriptions
• 2016
• What's your opinion on updating CVE ID Descriptions?
• Summary of your feedback about how Descriptions are used in CVE IDs
• What's your opinion on how Descriptions are used in CVE IDs?
• Other
• FOCUS ON: Marking a CVE ID “REJECT” Is Not Permanent; It Can Be Updated and Added to the CVE List
• FOCUS ON: The Significance and Meaning of a CVE Identifier Marked as "RESERVED"
• FOCUS ON: The Significance and Meaning of the Year Portion of a CVE Identifier