@dok2001@Cloudflare what happened to your ctf? still no reply on hackerone. you silently removed the scope and gave no updates what so ever.
really curious about that ๐
@0jayden_@verialabs congrats, does it work on GHES only or github wep app as well?
curious because I also been working on similar finding in the past days.
It seems that the @Cloudflare CTF was a sham. Several people have contacted also that they resolved it, got the flag, submitted results and were ghosted on H1. There was either a dup response, or no response at all. If anyone else had different experience feel free to comment.
@thsottiaux please remove region based restrictions, I live in Tรผrkiye and because of that I cannot get daybreak access even though I am a security researcher, have CVE on my name, public H1 and Bugcrowd profiles etc.
make sure that access to these models is based on the skill, not race.
@LiveOverflow@S1r1u5_@Cloudflare are they even replying to the reports? i have captured a flag on the very first day of the CTF. after that they shipped probably 4 updates to strengthen the WAF, and my bypass works for every one of them so I submitted 3-4 more flags to the same report.
no reply still.
@Bartonaut55@ycombinator congrats on the launch!
where can I access the list of 500+ CVEs you found? curious to read some of them to learn what your harness can find because I am also buidling such systems and was able to find a plenty of RCEs on C/C++ native code.
got dup to a ROOT RCE on a public program.
interesting thing is that it has been almost 1.5 months and the program still hasn't looked at it.
more interestingly, this is a 0-day, and most of the world is affected by it.
original reporter, if you see this post, can u DM me?
CVE-2026-116366
first CVE on my name just dropped. unauthenticated RCE on any @ClickHouseDB instance using just the public service hostname.
special thanks to San and the ClickHouse security team. the report was accepted within 20 minutes on Bugcrowd.
P.S. Clickhouse Security Team emailed me 1 hour before I reported the vulnerability stating that they "detected attempts of unauthenticated RCE on my instance" which shows how seriously they approach the security of their service in general.