-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Issues: google/oss-fuzz
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
No coverage generated due to corpus format in Golang Native Fuzzing
#13285
opened May 6, 2025 by
sudiptob2
nginx: Fuzz Introspector report and "Functions of interest to fuzz" show incorrect data
#13267
opened Apr 30, 2025 by
dimakuv
No Email Notifications Received despite crashes being reported in OSS-Fuzz
#13236
opened Apr 18, 2025 by
sudiptob2
helper: build_image on ARM does not add the --platform=linux/amd64 flag by default
#13208
opened Apr 10, 2025 by
marcellomaugeri
jq:jq_fuzz_execute: Heap-buffer-overflow in jv_string_vfmt: reopening
#13193
opened Apr 2, 2025 by
johnleslie
Failed to get component revisions - is this an intented behaviour?
#13145
opened Mar 18, 2025 by
Jarvx
Standalone Python Module for Querying OSS-Fuzz Project Details & Historical Results
#13139
opened Mar 17, 2025 by
1himan
Issues not reported - Minimized Testcase: Pending - even though it finished.
#13116
opened Mar 6, 2025 by
kasper93
QEMU: Some corpus backups being generated. No coverage reports generated at all
#13115
opened Mar 5, 2025 by
a1xndr
Previous Next
ProTip!
Follow long discussions with comments:>50.