<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploit Intel — cve-2025-58159</title><link>https://exploit-intel.com/blog/tags/cve-2025-58159/</link><description>EIP research articles tagged cve-2025-58159.</description><language>en-us</language><atom:link href="https://exploit-intel.com/blog/tags/cve-2025-58159/index.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Fri, 27 Feb 2026 12:00:00 -0400</lastBuildDate><item><title>CVE-2025-60355 (OneBlog): CVEForge Finds 3 Bypass/Incomplete Fixes in 5 CVE Runs</title><link>https://exploit-intel.com/blog/posts/five-cves-three-bypasses-java-case-study/</link><guid isPermaLink="true">https://exploit-intel.com/blog/posts/five-cves-three-bypasses-java-case-study/</guid><description>In this CVEForge patch-validation run, we analyze CVE-2025-60355 in OneBlog (Java/FreeMarker) and compare outcomes across five CVEs. Three of five runs ended in confirmed bypass or incomplete-fix results.</description><pubDate>Fri, 27 Feb 2026 12:00:00 -0400</pubDate></item><item><title>Zero to RCE: Autonomous Exploit Development Across Three Vulnerability Classes</title><link>https://exploit-intel.com/blog/posts/zero-to-rce-autonomous-exploit-development/</link><guid isPermaLink="true">https://exploit-intel.com/blog/posts/zero-to-rce-autonomous-exploit-development/</guid><description>After CVEForge's first successful run, we needed to know if it was luck or a pattern. Two more CVEs, zero hand-holding, and an AI agent that found a fix bypass the developers missed.</description><pubDate>Thu, 26 Feb 2026 12:00:00 -0400</pubDate></item></channel></rss>
