<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>NVD on After the Code</title><link>https://windshock.github.io/en/tags/nvd/</link><description>Recent content in NVD on After the Code</description><generator>Hugo -- 0.145.0</generator><language>en-US</language><lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://windshock.github.io/en/tags/nvd/index.xml" rel="self" type="application/rss+xml"/><item><title>Beyond CVE Response: AI-Era Vulnerabilities Move Before They Get Numbers</title><link>https://windshock.github.io/en/post/2026-04-29-after-cve-response-ai-vulnerability/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/en/post/2026-04-29-after-cve-response-ai-vulnerability/</guid><description>AI-era vulnerability response cannot wait for a CVE number. Pre-CVE signals such as issues, commits, PoCs, write-ups, and patch traces now have to be mapped against internal exposure earlier.</description></item></channel></rss>