Draft Reseau security advisories - #612
Merged
mbauman merged 1 commit intoJul 28, 2026
Merged
Conversation
Member
|
CI should pass starting tomorrow once Reseau's registration propagates. I'm on board with publishing mostly bugs, but I think we should work to get severity assessments in to help folks triage the reports they may see. |
Member
Author
|
Well, it's a non-deterministic memory corruption. Exploitation is probably not that easy, but we do have magic exploitation machines now, so, .... |
quinnj
approved these changes
Jul 25, 2026
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
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.
These security advisories were generated from the upstream reports. I think there is a bit of a question where the line between a bug and a security issue is, but I figure if they come in as security reports, might as well go out as them. Let me know if opinions differ. cc @quinnj