{"id":58509,"date":"2025-04-16T19:34:39","date_gmt":"2025-04-16T19:34:39","guid":{"rendered":"http:\/\/9bd2a0d0-e02d-4511-81af-3017658aa2cd"},"modified":"2025-04-16T19:34:39","modified_gmt":"2025-04-16T19:34:39","slug":"why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/","title":{"rendered":"Why the CVE database for tracking security flaws nearly went dark &#8211; and what happens next"},"content":{"rendered":"<figure class=\"c-shortcodeImage u-clearfix c-shortcodeImage-large\">\n<div class=\"c-shortcodeImage_imageContainer\">\n<div class=\"c-shortcodeImage_image\"><picture class=\"c-cmsImage c-cmsImage_loaded\"><source media=\"(max-width: 767px)\" srcset=\"https:\/\/www.zdnet.com\/a\/img\/resize\/5e42b61bb422a812a0b0dd00c73cb74ac147a830\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=768\" alt=\"globedark5gettyimages-2071084265\"><source media=\"(max-width: 1023px)\" srcset=\"https:\/\/www.zdnet.com\/a\/img\/resize\/bc1a20ab932e5198074c7493d82e831c887bfaf4\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1024\" alt=\"globedark5gettyimages-2071084265\"><source media=\"(max-width: 1440px)\" srcset=\"https:\/\/www.zdnet.com\/a\/img\/resize\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280\" alt=\"globedark5gettyimages-2071084265\"><img decoding=\"async\" src=\"https:\/\/www.zdnet.com\/a\/img\/resize\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280\" alt=\"globedark5gettyimages-2071084265\" width=\"1280\" height=\"720.1039411000432\" fetchpriority=\"low\"><\/picture><\/div>\n<p> <!----><\/div><figcaption> <span class=\"c-shortcodeImage_credit g-outer-spacing-top-xsmall u-block\">fotograzia\/Getty Images<\/span><\/figcaption><\/figure>\n<p>Over the weekend, security experts were beginning to panic.&nbsp;<a href=\"https:\/\/www.mitre.org\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">MITRE<\/a>&nbsp;announced that the US government had not renewed funding for the <a href=\"https:\/\/www.cve.org\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">Common Vulnerabilities and Exposures (CVE) <\/a>database.&nbsp;<\/p>\n<p>MITRE VP Yosry Barsoum warned that the government contract support enabling MITRE &#8220;<a href=\"https:\/\/bsky.app\/profile\/tib3rius.bsky.social\/post\/3lmulrbygoe2g\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">to develop, operate, and modernize CVE<\/a>&#8221; would expire on April 16. That would mean, Barsoum continued, &#8220;multiple impacts to CVE, including deterioration of national vulnerability databases and advisories, tool vendors, incident response operations, and all manner of critical infrastructure.&#8221;<\/p>\n<p><strong>Also: <a href=\"https:\/\/www.zdnet.com\/article\/navigating-ai-powered-cyber-threats-in-2025-4-expert-security-tips-for-businesses\/\">Navigating AI-powered cyber threats: 4 expert security tips for businesses<\/a><\/strong><\/p>\n<p>All computer security depends upon CVE, which is the standard for tracking what is (and is not) a significant security hole. Fortunately, with no time left on the clock, MITRE, the non-profit that oversees the CVE database, announced&nbsp;<a href=\"https:\/\/www.reuters.com\/world\/us\/us-agency-extends-support-last-minute-cyber-vulnerability-database-2025-04-16\/#link={%22role%22:%22standard%22,%22href%22:%22https:\/\/www.reuters.com\/world\/us\/us-agency-extends-support-last-minute-cyber-vulnerability-database-2025-04-16\/%22,%22target%22:%22_blank%22,%22absolute%22:%22%22,%22linkText%22:%22it would get funding after all for another eleven months.%22}\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">it would get funding&nbsp;<\/a><a href=\"https:\/\/www.reuters.com\/world\/us\/us-agency-extends-support-last-minute-cyber-vulnerability-database-2025-04-16\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">for another 11 months.<\/a>&nbsp; <\/p>\n<p>The CVE program, which has cataloged more than 274,000 publicly disclosed security flaws since its inception in 1999, is relied upon by governments, private industry, and open-source communities &#8212; in short, <em>everyone<\/em> &#8212; to track and coordinate responses to software holes. For example,&nbsp;<a href=\"https:\/\/learn.microsoft.com\/en-us\/windows\/deployment\/update\/release-cycle#link={%22role%22:%22standard%22,%22href%22:%22https:\/\/learn.microsoft.com\/en-us\/windows\/deployment\/update\/release-cycle%22,%22target%22:%22_blank%22,%22absolute%22:%22%22,%22linkText%22:%22Microsoft with Patch Tuesday%22}\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">Microsoft, with its Patch Tuesday,<\/a>&nbsp;and&nbsp;<a href=\"https:\/\/www.zdnet.com\/article\/the-linux-security-team-issues-60-cves-a-week-but-dont-stress-do-this-instead\/#link={%22linkText%22:%22Linux kernel developers%22,%22target%22:%22_blank%22,%22href%22:%22https:\/\/www.zdnet.com\/article\/the-linux-security-team-issues-60-cves-a-week-but-dont-stress-do-this-instead\/%22,%22role%22:%22standard%22,%22absolute%22:%22%22}\">Linux kernel developers<\/a>&nbsp;both use CVEs to track security problems.<\/p>\n<p>Everyone relies on CVEs because, while far from perfect, they&#8217;re the universally agreed-upon standard for tracking security problems. As Jen Easterly, former director of the&nbsp;<a href=\"https:\/\/www.cisa.gov\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">Cybersecurity and Infrastructure Security Agency (CISA)<\/a>, explained on LinkedIn: <\/p>\n<blockquote readability=\"8.84\">\n<p>Think of the <a href=\"https:\/\/www.linkedin.com\/feed\/update\/urn:li:activity:7318021583191617538\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">CVE system like the Dewey Decimal System for cybersecurity<\/a>. It&#8217;s the global catalog that helps everyone &#8212; security teams, software vendors, researchers, governments &#8212; organize and talk about vulnerabilities using the same reference system. Without it:<\/p>\n<ul>\n<li>Everyone is using a different catalog or no catalog at all;<\/li>\n<li>No one knows if they&#8217;re talking about the same problem;<\/li>\n<li>Defenders waste precious time figuring out what&#8217;s wrong;<\/li>\n<li>And worst of all, threat actors take advantage of the confusion.<\/li>\n<\/ul>\n<\/blockquote>\n<p>Moreover, as Ariadne Conill, co-founder and distinguished engineer at the tech security company <a href=\"https:\/\/edera.dev\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">Edera<\/a>, told me in an interview. &#8220;The CVE database is crucial to international security. Although third-party databases exist, the world has standardized on CVE identifiers to act as pointers to vulnerability data. Loss of CVE services will be catastrophic. Every vulnerability management strategy around the world today is heavily dependent on and structured around the CVE system and its identifiers.&#8221;<\/p>\n<p><!----><\/p>\n<p>Looking ahead, Conill continued, &#8220;vulnerability databases should embrace linked data to reference the same vulnerability in external databases rather than depending on CVE identifiers. Vulnerability data enrichment can be done using linked data technologies such as <a href=\"https:\/\/json-ld.org\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">JSON-LD<\/a>, which has already been leveraged by <a href=\"https:\/\/spdx.github.io\/spdx-spec\/v3.0.1\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">SPDX 3<\/a> and <a href=\"https:\/\/github.com\/openvex\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">OpenVEX<\/a>. As a result, the National Vulnerability Database will no longer be necessary, and developers won&#8217;t be beholden to decisions like these.&#8221;&nbsp;<\/p>\n<p>Until that happens, however, CVE will remain critical to all technology security.&nbsp; <\/p>\n<p><strong>Also: <a href=\"https:\/\/www.zdnet.com\/article\/best-free-vpn\/\">The best free VPNs of 2025: Expert tested<\/a><\/strong><\/p>\n<p>How did CVE come so close to shutting down? It&#8217;s about federal contracts and the current confusion over US government finances. MITRE has operated the CVE program for 25 years, under sponsorship from the US Department of Homeland Security (DHS) and the CISA. MITRE acts as the CVE Editor and Primary CVE Numbering Authority (CNA), overseeing the assignment of unique CVE identifiers that serve as a global reference standard for vulnerabilities.&nbsp;<\/p>\n<p>MITRE also manages related programs such as the <a href=\"https:\/\/cwe.mitre.org\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">Common Weakness Enumeration (CWE)<\/a>, which classifies software and hardware weaknesses.&nbsp; <\/p>\n<p>We don&#8217;t know why the contract wasn&#8217;t renewed until the last possible moment. We do know, however, that &#8212; under DOGE &#8212; CISA employees were given until midnight Monday to choose between <a href=\"https:\/\/www.govinfosecurity.com\/cisa-braces-for-major-workforce-cuts-amid-security-fears-a-27996\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">staying on the job or resigning<\/a>. Those who remained would face the possibility of being laid off as the agency faces cuts of up to one-third of its workforce..&nbsp;<\/p>\n<p>Late on Tuesday, April 15, CISA executed the option period on the contract to ensure there will be no lapse in critical CVE services. This option only lasts for 11 months and then must be renewed &#8212; or we&#8217;ll be back in the same boat.&nbsp;<\/p>\n<p><strong>Also: <a href=\"https:\/\/www.zdnet.com\/article\/windows-warning-dont-delete-that-weird-inetpub-folder-already-did-heres-your-fix\/\">Windows warning: Don&#8217;t delete that weird &#8216;inetpub&#8217; folder. Already did? Here&#8217;s your fix<\/a><\/strong><\/p>\n<p>While the immediate risk of disruption has been averted, the episode highlighted longstanding concerns about the sustainability and neutrality of the CVE program, which is relied upon worldwide yet dependent on US government funding. This is also not the first time a lack of cash has threatened CVEs. Last summer, <a href=\"https:\/\/securityboulevard.com\/2024\/06\/the-nist-finally-hires-a-contractor-to-manage-cves\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">insufficient funds kept anyone from managing the eternal flood of new CVEs<\/a><\/p>\n<p>CVE board members have launched the <a href=\"https:\/\/www.thecvefoundation.org\/\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">CVE Foundation<\/a>, a nonprofit organization to maintain the program&#8217;s future stability and independence. Kent Landfield, one of CVE&#8217;s founders and a CVE Foundation officer, noted that &#8220;CVE, as a cornerstone of the global cybersecurity ecosystem, is too important to be vulnerable itself. Cybersecurity professionals around the globe rely on CVE identifiers and data as part of their daily work, from security tools and advisories to threat intelligence and response. Without CVE, defenders are at a massive disadvantage against global cyber threats.&#8221;<\/p>\n<p>The CVE Foundation&#8217;s goal is to eliminate this single point of failure in the vulnerability management ecosystem and ensure the CVE Program remains a globally trusted, community-driven initiative. <\/p>\n<p><strong>Also: <a href=\"https:\/\/www.zdnet.com\/article\/the-head-of-us-ai-safety-has-stepped-down-what-now\/\">The head of US AI safety has stepped down. What now?<\/a><\/strong><\/p>\n<p>Each security alert in the CVE list contains a unique identifier called a CVE ID, a description of the vulnerability, and information references. The system allows organizations, security professionals, and vendors to communicate clearly and consistently about specific security flaws. This, in turn, helps facilitate tracking, assessment, and remediation efforts. Most CVEs are assigned a <a href=\"https:\/\/nvd.nist.gov\/vuln-metrics\/cvss\" target=\"_blank\" rel=\"noopener nofollow\" class=\"c-regularLink\">Common Vulnerability Scoring System (CVSS)<\/a> score. This is a numerical rating, ranging from 0 to 10, where the higher the score, the more dangerous the security hole. CVSS scores are commonly used to decide how quickly a problem needs to be fixed.<\/p>\n<p><em>Stay ahead of security news with <\/em><a href=\"https:\/\/www.zdnet.com\/newsletters\/\"><strong><em>Tech Today<\/em><\/strong><\/a><em>, delivered to your inbox every morning.<\/em><\/p>\n<p>READ MORE <a href=\"https:\/\/www.zdnet.com\/article\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/\">HERE<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Expired US government funding nearly disrupted this global security system. How can we prevent this from happening again in 11 months?READ MORE HERE&#8230;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"colormag_page_layout":"default_layout","footnotes":""},"categories":[62],"tags":[],"class_list":["post-58509","post","type-post","status-publish","format-standard","hentry","category-zdnet-security"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Why the CVE database for tracking security flaws nearly went dark - and what happens next 2026 | ThreatsHub Cybersecurity News<\/title>\n<meta name=\"description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security &amp; Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why the CVE database for tracking security flaws nearly went dark - and what happens next 2026 | ThreatsHub Cybersecurity News\" \/>\n<meta property=\"og:description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security &amp; Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/\" \/>\n<meta property=\"og:site_name\" content=\"ThreatsHub Cybersecurity News\" \/>\n<meta property=\"article:published_time\" content=\"2025-04-16T19:34:39+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.zdnet.com\/a\/img\/resize\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280\" \/>\n<meta name=\"author\" content=\"TH Author\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@threatshub\" \/>\n<meta name=\"twitter:site\" content=\"@threatshub\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"TH Author\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/\"},\"author\":{\"name\":\"TH Author\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\"},\"headline\":\"Why the CVE database for tracking security flaws nearly went dark &#8211; and what happens next\",\"datePublished\":\"2025-04-16T19:34:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/\"},\"wordCount\":1019,\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.zdnet.com\\\/a\\\/img\\\/resize\\\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\\\/2025\\\/04\\\/16\\\/05768c21-437b-4c9e-a116-3f901a377eb6\\\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280\",\"articleSection\":[\"ZDNet | Security\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/\",\"name\":\"Why the CVE database for tracking security flaws nearly went dark - and what happens next 2026 | ThreatsHub Cybersecurity News\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.zdnet.com\\\/a\\\/img\\\/resize\\\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\\\/2025\\\/04\\\/16\\\/05768c21-437b-4c9e-a116-3f901a377eb6\\\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280\",\"datePublished\":\"2025-04-16T19:34:39+00:00\",\"description\":\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.zdnet.com\\\/a\\\/img\\\/resize\\\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\\\/2025\\\/04\\\/16\\\/05768c21-437b-4c9e-a116-3f901a377eb6\\\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280\",\"contentUrl\":\"https:\\\/\\\/www.zdnet.com\\\/a\\\/img\\\/resize\\\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\\\/2025\\\/04\\\/16\\\/05768c21-437b-4c9e-a116-3f901a377eb6\\\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why the CVE database for tracking security flaws nearly went dark &#8211; and what happens next\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"name\":\"ThreatsHub Cybersecurity News\",\"description\":\"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"alternateName\":\"Threatshub.org\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\",\"name\":\"ThreatsHub.org\",\"alternateName\":\"Threatshub.org\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"width\":432,\"height\":435,\"caption\":\"ThreatsHub.org\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/threatshub\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\",\"name\":\"TH Author\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"caption\":\"TH Author\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Why the CVE database for tracking security flaws nearly went dark - and what happens next 2026 | ThreatsHub Cybersecurity News","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/","og_locale":"en_US","og_type":"article","og_title":"Why the CVE database for tracking security flaws nearly went dark - and what happens next 2026 | ThreatsHub Cybersecurity News","og_description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","og_url":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/","og_site_name":"ThreatsHub Cybersecurity News","article_published_time":"2025-04-16T19:34:39+00:00","og_image":[{"url":"https:\/\/www.zdnet.com\/a\/img\/resize\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280","type":"","width":"","height":""}],"author":"TH Author","twitter_card":"summary_large_image","twitter_creator":"@threatshub","twitter_site":"@threatshub","twitter_misc":{"Written by":"TH Author","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/#article","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/"},"author":{"name":"TH Author","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476"},"headline":"Why the CVE database for tracking security flaws nearly went dark &#8211; and what happens next","datePublished":"2025-04-16T19:34:39+00:00","mainEntityOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/"},"wordCount":1019,"publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/#primaryimage"},"thumbnailUrl":"https:\/\/www.zdnet.com\/a\/img\/resize\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280","articleSection":["ZDNet | Security"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/","url":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/","name":"Why the CVE database for tracking security flaws nearly went dark - and what happens next 2026 | ThreatsHub Cybersecurity News","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/#primaryimage"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/#primaryimage"},"thumbnailUrl":"https:\/\/www.zdnet.com\/a\/img\/resize\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280","datePublished":"2025-04-16T19:34:39+00:00","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","breadcrumb":{"@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/#primaryimage","url":"https:\/\/www.zdnet.com\/a\/img\/resize\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280","contentUrl":"https:\/\/www.zdnet.com\/a\/img\/resize\/4d666f6b55fb791b96f5d11735e2d3d11b50c46b\/2025\/04\/16\/05768c21-437b-4c9e-a116-3f901a377eb6\/globedark5gettyimages-2071084265.jpg?auto=webp&amp;width=1280"},{"@type":"BreadcrumbList","@id":"https:\/\/www.threatshub.org\/blog\/why-the-cve-database-for-tracking-security-flaws-nearly-went-dark-and-what-happens-next\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.threatshub.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Why the CVE database for tracking security flaws nearly went dark &#8211; and what happens next"}]},{"@type":"WebSite","@id":"https:\/\/www.threatshub.org\/blog\/#website","url":"https:\/\/www.threatshub.org\/blog\/","name":"ThreatsHub Cybersecurity News","description":"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform","publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"alternateName":"Threatshub.org","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.threatshub.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.threatshub.org\/blog\/#organization","name":"ThreatsHub.org","alternateName":"Threatshub.org","url":"https:\/\/www.threatshub.org\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","width":432,"height":435,"caption":"ThreatsHub.org"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/threatshub"]},{"@type":"Person","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476","name":"TH Author","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","caption":"TH Author"}}]}},"_links":{"self":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/58509","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/comments?post=58509"}],"version-history":[{"count":0,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/58509\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media?parent=58509"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/categories?post=58509"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/tags?post=58509"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}