13 advisories, 0 reporting triggers: severity is not exploitation under the EU CRA
说明与用途
团队常误将所有扫描器发现的高危 CVE 视为 EU CRA 报告触发点。实际上,只有 KEV 列表中的漏洞才需要通报。使用 cra‑watch 将 advisories 与 KEV 交叉,并定期运行,可快速识别真正的报告列表,避免过度报告。
问题
Teams misinterpret vulnerability scanner output as the trigger for EU Cyber Resilience Act (CRA) reporting, leading to over‑reporting and wasted effort.
结果
By intersecting advisories with KEV and scheduling the check, teams can focus on a short list of true reporting triggers, avoid over‑reporting, and comply with CRA requirements efficiently.
工作流
- Run a dependency scan to list all components with advisories.
- Intersect the advisory list with the KEV catalogue to identify actively exploited vulnerabilities.
- Schedule the intersection run regularly (e.g., CI pipeline) rather than on push.
- Define a clear decision owner for reporting before the 24‑hour clock starts.
- Document the decision and its timing for audit purposes.
证据
Thirteen components with published advisories. Zero on the known‑exploited list.
One component. Two known‑exploited CVEs. That's the one that deserves a human in the room.
- 记录日期: 2026-09-19T23:45:45.013Z