<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploitation Speed on Juan Carlos Munera</title><link>https://cybersecpro.me/tags/exploitation-speed/</link><description>Recent content in Exploitation Speed on Juan Carlos Munera</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Juan Carlos Munera</copyright><lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cybersecpro.me/tags/exploitation-speed/index.xml" rel="self" type="application/rss+xml"/><item><title>When a Public Exploit Lands in Two Days, Severity Ratings Aren't Enough</title><link>https://cybersecpro.me/posts/public-exploit-window-patch-priority/</link><pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate><guid>https://cybersecpro.me/posts/public-exploit-window-patch-priority/</guid><description>A threat-hunting report puts the gap between a public proof-of-concept and active exploitation at about 48 hours. Here is what that does to patch scheduling, why severity scores are the wrong primary signal, and a few adjustments worth making.</description></item></channel></rss>