fix: address fuzzing findings and other miscellaneous issues#1360
Merged
Conversation
5540268 to
50d34b3
Compare
stevebeattie
reviewed
Feb 5, 2026
511c5dc to
bedbd79
Compare
760624f to
6af6e80
Compare
Signed-off-by: egibs <20933572+egibs@users.noreply.github.com>
stevebeattie
approved these changes
Feb 6, 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.
This PR addresses the issues that came up in the first round of long-term fuzzing.
We needed additional checking for parent directory symlink traversals when extracting archives along with size limits for programkind checks and ignoring invalid Yara/YAML patterns to avoid crashing the fuzzers.
Additionally, this PR cleans up more potential FD leaks and adds validation around OCI image layer sizes and fixes the UPX binary we use, among other things.
make fuzzruns cleanly with these fixes.