<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: goobreee</title><link>https://news.ycombinator.com/user?id=goobreee</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 07 Sep 2026 18:25:46 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=goobreee" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by goobreee in "Six curl CVEs after OpenAI and Anthropic came back with zero"]]></title><description><![CDATA[
<p>i think a key missing part is that an LLM on its own can't find vulnerabilities, so it's <i>always</i> an AI + harness. even mythos, when used for finding zero-days, is using an actually surprisingly heavy handed and expensive scaffold. they literally make it run in parallel on ±all files and ask "what's wrong with this?". here from the mythos technical blog post [1]:<p>> To increase efficiency, instead of processing literally every file for each software project that we evaluate, we first ask Claude to rank how likely each file in the project is to have interesting bugs on a scale of 1 to 5. A file ranked “1” has nothing at all that could contain a vulnerability (for instance, it might just define some constants). Conversely, a file ranked “5” might take raw data from the Internet and parse it, or it might handle user authentication. We start Claude on the files most likely to have bugs and go down the list in order of priority.<p>So they process it in parallel, but AI-rank them based on vuln-likelihood first = exhaustive search with a heuristic filtering first<p>[1] <a href="https://www.anthropic.com/research/mythos-preview" rel="nofollow">https://www.anthropic.com/research/mythos-preview</a></p>
]]></description><pubDate>Wed, 02 Sep 2026 18:37:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=49540478</link><dc:creator>goobreee</dc:creator><comments>https://news.ycombinator.com/item?id=49540478</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49540478</guid></item><item><title><![CDATA[New comment by goobreee in "Six curl CVEs after OpenAI and Anthropic came back with zero"]]></title><description><![CDATA[
<p>i don't think this is correct. if you look at this article by the curl founder daniel stenberg (<a href="https://daniel.haxx.se/blog/2026/05/11/mythos-finds-a-curl-vulnerability/" rel="nofollow">https://daniel.haxx.se/blog/2026/05/11/mythos-finds-a-curl-v...</a>), he talks about how he previously ran Mythos on curl and that it found 5 issues: 1 turned out to be a low severity CVE, 3 were false positives, and 1 just a bug. So a) Mythos detects low severity CVEs too, and b) it is fairly noisy</p>
]]></description><pubDate>Wed, 02 Sep 2026 15:09:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=49537500</link><dc:creator>goobreee</dc:creator><comments>https://news.ycombinator.com/item?id=49537500</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49537500</guid></item><item><title><![CDATA[New comment by goobreee in "Six curl CVEs after OpenAI and Anthropic came back with zero"]]></title><description><![CDATA[
<p>i don't think this is doable fairly. as they say in the blog post, the only fair way to is to look for new, previously undiscovered zero-days, otherwise you always risk the model has in some way been trained on the vulnerabilities. looking for legit new stuff is the only way to prevent leakage (even accidental one)</p>
]]></description><pubDate>Wed, 02 Sep 2026 15:07:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=49537471</link><dc:creator>goobreee</dc:creator><comments>https://news.ycombinator.com/item?id=49537471</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49537471</guid></item><item><title><![CDATA[New comment by goobreee in "Six curl CVEs after OpenAI and Anthropic came back with zero"]]></title><description><![CDATA[
<p>I think you might be misunderstanding this? This is, from my understanding, what went down:<p>1. curl was scanned by many different things, including AISLE, and many bugs were fixed <- all this was in the past
2. curl a week ago was scanned again my Mythos and Codex Security, and both of them said: 0 issues found
3. the same curl was scanned by AISLE a day later, resulting in ~29 reports (based on the blog post and mastodon posts from Daniel Stenberg)
4. of these 29, 6 cleared the bar and got CVEs in curl
5. these 6 CVEs were just announced as fixed in curl 8.22.0 today, together with 4 more CVEs that were detected by other people prior to point 2. of this list<p>so imho it was head-to-head, the very same codebase => it's a legit comparison</p>
]]></description><pubDate>Wed, 02 Sep 2026 15:06:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=49537454</link><dc:creator>goobreee</dc:creator><comments>https://news.ycombinator.com/item?id=49537454</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49537454</guid></item><item><title><![CDATA[Six curl CVEs after OpenAI and Anthropic came back with zero]]></title><description><![CDATA[
<p>Article URL: <a href="https://aisle.com/blog/aisle-discovered-six-curl-cves-after-openai-and-anthropic-found-zero">https://aisle.com/blog/aisle-discovered-six-curl-cves-after-openai-and-anthropic-found-zero</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49536114">https://news.ycombinator.com/item?id=49536114</a></p>
<p>Points: 182</p>
<p># Comments: 66</p>
]]></description><pubDate>Wed, 02 Sep 2026 13:43:14 +0000</pubDate><link>https://aisle.com/blog/aisle-discovered-six-curl-cves-after-openai-and-anthropic-found-zero</link><dc:creator>goobreee</dc:creator><comments>https://news.ycombinator.com/item?id=49536114</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49536114</guid></item><item><title><![CDATA["Mythos" at Home, and It's Called Aisle]]></title><description><![CDATA[
<p>Article URL: <a href="https://stanislavfort.substack.com/p/mythos-at-home-and-its-called-aisle">https://stanislavfort.substack.com/p/mythos-at-home-and-its-called-aisle</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48571884">https://news.ycombinator.com/item?id=48571884</a></p>
<p>Points: 7</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 17 Jun 2026 15:31:00 +0000</pubDate><link>https://stanislavfort.substack.com/p/mythos-at-home-and-its-called-aisle</link><dc:creator>goobreee</dc:creator><comments>https://news.ycombinator.com/item?id=48571884</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48571884</guid></item></channel></rss>