feat(generate-cve-json): emit related references for sibling CVEs#384
Merged
potiuk merged 1 commit intoMay 30, 2026
Merged
Conversation
Per Arnout Engelen's 2026-05-29 review comment on CVE-2026-49298 — when a CVE is an incomplete-fix follow-up to a prior CVE (or otherwise relates to one), the JSON should carry a structured references[] entry of type "related" pointing at the prior CVE record. Implementation: - Extend classify_reference to tag cve.org/CVERecord?id=... and nvd.nist.gov/vuln/detail/... URLs as ["related"]. - Add extract_related_cve_ids(text, current_cve_id) — finds distinct CVE-YYYY-NNNNN tokens in arbitrary text with word-boundary matching, excludes the current record's own ID, preserves first-appearance order for deterministic emission. - Add related_cve_url(cve_id) — emits the canonical https://www.cve.org/CVERecord?id=<id> URL. - build_cna_container now accepts current_cve_id, extracts related IDs from the description, and appends cve.org URLs to the references list. Tests: 20 new cases. Full suite 264/264. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per Arnout Engelen's 2026-05-29 review comment on CVE-2026-49298 — when a CVE is an incomplete-fix follow-up to a prior CVE (or otherwise relates to one), the JSON should carry a structured `references[]` entry of type `related` pointing at the prior CVE record so ASF Security's downstream tooling can navigate the cross-CVE relationship.
Implementation
Gate #3 (incomplete-fix cross-CVE clause, PR #372) already pushes prior CVE IDs into the summary text — so this lands automatically the next time the body is regenerated for any incomplete-fix tracker.
Test plan
🤖 Generated with Claude Code