Skip to content

CVE: mention the affected branches better - #635

Closed
bagder wants to merge 1 commit into
masterfrom
bagder/CVE-mention-branch
Closed

bagder wants to merge 1 commit into
masterfrom
bagder/CVE-mention-branch

Conversation

@bagder

@bagder bagder commented Oct 8, 2026

Copy link
Copy Markdown
Member

To help clarify for users about the not affected versions when they are not in the linear master branch but instead refer to Rock-solid curl branches.

To help clarify for users about the not affected versions when they are
not in the linear master branch but instead refer to Rock-solid curl
branches.
@bagder

bagder commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

@dfandrich: thoughts?

@bagder
bagder marked this pull request as ready for review October 8, 2026 15:03
@dfandrich

Copy link
Copy Markdown
Collaborator

This is clear to me now. Thanks!

Are these advisories 100% generated by hand or are the skeletons created from the CVE JSON?

@bagder

bagder commented Oct 8, 2026 •

Copy link
Copy Markdown
Member Author

It's the other way around: the markdown files are written by hand, and all the JSON is entirely generated from the vuln.pm file and the content of the markdowns.

@bagder bagder closed this in 2190aa5 Oct 9, 2026
@bagder
bagder deleted the bagder/CVE-mention-branch branch October 9, 2026 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants