Monitor CVE adoption of SSVC json data structures #681

Activity

1. ahouseholder

   added this to the 1Q25 milestone on Feb 11, 2025
2. ahouseholder

   assigned

   sei-vsarvepalli

   on Feb 11, 2025
3. ahouseholder

   modified the milestones: 2025-03, 2025-06 on Mar 31, 2025
4. ahouseholder

   added

   integration/blockerSomething that is blocking integration with another framework or systemSomething that is blocking integration with another framework or system

   tech/dataData implementation (content of /data, data object instances, etc.)Data implementation (content of /data, data object instances, etc.)

   on Jul 1, 2025
5. ahouseholder

   modified the milestones: 2025-06, 2025-09 on Jul 1, 2025
6. ahouseholder

   removed this from the 2025-09 milestone on Sep 9, 2025
7. sei-vsarvepalli commented on Dec 15, 2025

   

   sei-vsarvepalli

   on Dec 15, 2025

   Contributor

   More actions

   Note that the PR CVEProject/cve-schema#460 has been updated with a new script that is an node npm script at https://github.com/sei-vsarvepalli/cve-schema/blob/35c1d9ddb59e8446b2ed3251e14561da4f8dacb9/tools/ssvc_cve_schema.js
   designed to modify the Schema with specific options to allow for CVE Program usage with their restrictions. Once it is adopted by the CVE Program, we will have to write a new schema that is specific to SSVC v2.0.0 for CVE program with these restrictions.

   1. No target-ids in the SSVC v2.0.0 record
   2. Namespace for SSVCv2.0.0 record restricted to enum("cisa", "cvss", "ssvc", "aivss")
   3. No duplicate schemaVersion field in the SSVC v2.0.0 record
8. ahouseholder

   added a sub-issue on Jan 5, 2026

   • Create custom SSVC schema for CVE integration #1050
9. ahouseholder

   added

   EpicLarge-scale issues that represent multi-step implementations, used to thematically link other issuesLarge-scale issues that represent multi-step implementations, used to thematically link other issues

   on Jan 7, 2026