@mana_z @bagder Bounties are only expected for vulnerabilities that are practically exploitable. Initially, I thought this particular issue had potential to be exploitable, but it remained unclear until the potential attack vectors were identified. These vectors involved using SSL library functions that, when called with bogus SSL pointers, could lead to code execution. However, none of these vectors could be argued to be found in real-world applications.
Therefore, no bounty.
P.S. In theory, the quality of the report doesn't matter, but the technical facts. However, I consider it professional courtesy to always try to make the report as good quality as possible. I know @bagder and the people in the #curl project well, and I know the pain they're suffering when dealing with the AI slop reports. So, even though I'm reporting a potentially nasty vulnerability, at least they don't have to suffer the slop that language models generate.