<?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>流程 on BvBeJ的小站</title><link>https://www.bvbej.com/tags/%E6%B5%81%E7%A8%8B/</link><description>Recent content in 流程 on BvBeJ的小站</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sat, 30 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.bvbej.com/tags/%E6%B5%81%E7%A8%8B/feed.xml" rel="self" type="application/rss+xml"/><item><title>Docker 漏洞处置流程：CVE 分级与修复窗口</title><link>https://www.bvbej.com/posts/docker-cve-triage-workflow/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/docker-cve-triage-workflow/</guid><description>不是所有漏洞都要立刻升级，先做风险分级更务实</description></item></channel></rss>