Loading story…
CISA, the NSA, and international partners published joint guidance urging software manufacturers and online service providers to formalize coordinated vulnerability disclosure (CVD) programs for working with external security researchers. The guidance calls for organizations to publish a clear vulnerability disclosure policy, define internal processes for receiving, triaging, remediating, and disclosing reported flaws, and assign CVE identifiers where appropriate to improve tracking and transparency.
The document also recommends using third-party coordinators such as CISA or national CSIRTs when organizations need support handling disclosures, and it highlights safe harbor language to protect good-faith researchers from legal action. CISA said the practices can help vendors strengthen product security and give customers and critical infrastructure operators a way to assess a supplier’s maturity in handling vulnerability reports and remediation.
See the reporting duties and controls this puts on the clock.
1 event from the most recent confirmed update back to the earliest known activity.
CISA, the NSA, and international partners published joint guidance on establishing coordinated vulnerability disclosure programs for software manufacturers and online service providers. The guidance recommends a public vulnerability disclosure policy, triage and remediation processes, CVE assignment, use of third-party coordinators, and safe harbor language for good-faith researchers.
See what this changes for your reporting obligations and which controls it puts on the clock.
2 references tracked. Mallory keeps watching after this page renders.
waterisac.org
Open sourcecisa.gov
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
CISA said the **Common Vulnerabilities and Exposures (CVE) Program** should be placed on firmer legal footing, but warned Congress not to impose overly prescriptive rules that could limit the program’s ability to adapt. The debate follows a 2025 funding scare tied to MITRE’s contract, which exposed the risk of relying on a single U.S. federal agreement to support a vulnerability identification system used globally. Agency officials said CVE governance must stay flexible as **artificial intelligence** accelerates vulnerability discovery and as the ecosystem becomes more internationally distributed. CISA pointed to proposals that would authorize CVE within the Department of Homeland Security, formalize CISA’s role, require a modernization plan with **NIST**, and establish a 15-member governing board, while also noting **ENISA’s** expanding role as both a CVE Numbering Authority and a CVE Root as evidence that the program is moving toward a more federated global model.
Aug 7, 2026
Vulnerability management and responsible disclosure remain central challenges for cybersecurity professionals, with ongoing debates about best practices and the impact of industry processes. One perspective emphasizes the complexity of establishing effective vulnerability management programs, highlighting the need for clear requirements, scoping, target setting, and continuous improvement. Organizations are encouraged to define what they aim to achieve with vulnerability management, set measurable targets, and establish metrics and reporting mechanisms to track progress. The process also involves determining necessary roles, responsibilities, and tools, as well as implementing training and awareness programs to ensure all stakeholders are prepared to respond to vulnerabilities. Continuous improvement is stressed as essential, with organizations advised to start with pragmatic steps and evolve their programs over time. On the disclosure side, the industry recently faced a potential crisis when MITRE, the steward of the CVE catalog, nearly lost U.S. government funding, which could have disrupted the assignment of new vulnerability IDs and slowed global coordination. The last-minute extension of MITRE’s contract by CISA averted this disruption, underscoring the critical role of coordinated vulnerability disclosure. The debate over how vulnerabilities should be disclosed remains contentious, with some advocating for immediate public disclosure to force vendor action, while others warn that this can expose customers to risk before patches are available. The PrintNightmare incident is cited as an example where early disclosure led to widespread emergency mitigations. The lack of global laws governing responsible disclosure means that ethics, customer safety, and reputational risk drive industry behavior. Organizations must balance transparency with the need to protect users from exploitation, and the methods chosen for disclosure can have significant financial, operational, and reputational consequences. Both the management of vulnerabilities within organizations and the broader ecosystem of disclosure practices are evolving, with ongoing discussions about how to best protect customers and maintain trust. The interplay between internal vulnerability management processes and external disclosure frameworks highlights the complexity of the cybersecurity landscape. As new threats emerge and the industry adapts, organizations must remain vigilant in both managing vulnerabilities and participating in responsible disclosure. The recent funding scare with MITRE serves as a reminder of the fragility of the systems that underpin global vulnerability coordination. Ultimately, effective vulnerability management and responsible disclosure are interdependent, requiring collaboration, clear processes, and a commitment to continuous improvement.
Jun 30, 2026
The CVE Program approved updated **CVE Numbering Authority (CNA) Rules** that broaden how vulnerabilities can be assigned identifiers and clarify which CNA should handle a report. The revised framework introduces a **right-of-first-refusal** model that favors the CNA with the most appropriate scope, adopts more **technology-neutral** criteria for deciding whether an issue merits a `CVE`, and adds clearer guidance on what types of findings do and do not qualify for assignment. The changes are expected to affect vulnerability management by increasing flexibility for CNAs and potentially expanding coverage to issues that previously sat in gray areas, including some **cloud misconfigurations** and certain **supply-chain compromises**. The updated guidance still leaves open questions around shared code, protocols, specifications, and upstream dependencies, with examples such as **HTTP/2 CONTINUATION Flood** and **HTTP/2 Rapid Reset** illustrating the continuing ambiguity over how broadly CVEs should be assigned.
Jul 24, 2026