<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cve-Process on CuraSec</title><link>https://curasec.metacog.co.kr/tags/cve-process/</link><description>Recent content in Cve-Process on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 15:05:08 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/cve-process/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE Dispute: Maintainer Challenges Vulnerability Classification</title><link>https://curasec.metacog.co.kr/insights/2026-09-02-a-cve-dispute/</link><pubDate>Wed, 02 Sep 2026 15:05:08 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-02-a-cve-dispute/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> CVE disputes from prominent open-source maintainers illuminate how vulnerability severity gets contested and miscalibrated; worth reading to sharpen how you evaluate and prioritize CVE reports in your own dependency triage.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> CVE scoring disputes highlight systemic unreliability in the NVD/CVE pipeline that can distort risk register inputs; useful context when explaining to the board why CVSS scores alone are insufficient for prioritization.&lt;/li>
&lt;/ul></description></item></channel></rss>