<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dependency-Risk on CuraSec</title><link>https://curasec.metacog.co.kr/tags/dependency-risk/</link><description>Recent content in Dependency-Risk on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 12 Oct 2026 20:16:55 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/dependency-risk/index.xml" rel="self" type="application/rss+xml"/><item><title>Curl pauses vulnerability reports during July 2026 maintainer break</title><link>https://curasec.metacog.co.kr/insights/2026-10-12-curl-will-not-accept-vulnerability-reports-during-july-2026/</link><pubDate>Mon, 12 Oct 2026 20:16:55 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-12-curl-will-not-accept-vulnerability-reports-during-july-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> A reminder that widely-used open-source dependencies can have disclosure blackout windows; factor planned maintainer absences into your supply-chain risk posture when assessing how quickly critical fixes would arrive. The July window has passed, so no immediate action.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Illustrates a governance gap in open-source dependency risk: key maintainer unavailability can delay patch availability for critical libraries; worth noting when reviewing third-party software risk policy for OSS dependencies.&lt;/li>
&lt;/ul></description></item></channel></rss>