<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Curl on CuraSec</title><link>https://curasec.metacog.co.kr/tags/curl/</link><description>Recent content in Curl on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Jul 2026 12:18:39 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/curl/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Tool Mythos Discovers Vulnerability in curl</title><link>https://curasec.metacog.co.kr/insights/2026-07-16-mythos-finds-a-curl-vulnerability/</link><pubDate>Thu, 16 Jul 2026 12:18:39 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-16-mythos-finds-a-curl-vulnerability/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> curl (and libcurl) is present in virtually every Linux system, container image, and language runtime, making any disclosed vulnerability worth tracking; review your deployed curl versions and schedule a patch once the fix is available, but no exploitation signals exist to force emergency action.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, no exploitation, and no detection surface are present in this disclosure; the more notable angle is that an AI-assisted analysis tool surfaced a real bug in a ubiquitous open-source library, which is worth tracking as a signal of where automated vuln discovery is heading.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>