Know which of your projects and environments are still exposed to which CVE, who owns the fix, and what happened so far
# cvewatch
**Know which of your projects and environments are still exposed to which known vulnerability, who owns the fix, and what has happened so far.**
[](https://github.com/b070nd/cvewatch/actions/workflows/ci.yml)
[](https://m8ven.ai/mcp/b070nd-cvewatch-wot564?s=readme)
[](https://hub.xerj.org/contributors/b070nd)
Security feeds tell you *that* something is vulnerable. Scanners tell you *where* a version is bad at one moment. Neither answers the question a lead actually asks on Monday morning: **"Is it still open in prod, and who is on it?"** cvewatch watches the feeds that matter to your stack, matches them to what every environment really runs, and keeps the open, fixed and ignored status per project and environment, with the evidence, on your own machine.
```text
$ cvewatch update -env prod -min high
Open findings: 3
CRITICAL (2)
NEW CVE-2026-109618 shop: prod [affected] (+1 ids)
PHP Group PHP: PHP Memory Corruption Vulnerability
published 6d 9h ago · 2 articles · KEV, CISA due 2026-10-29 · EPSS 100% · official fix: action
NEW CVE-2026-103515 shop: prod [affected]
GitLab has remediated an issue in GitLab EE affecting all versions from 19.2…
published 6d 22h ago · 1 article · official fix: advisory
HIGH (1)
CVE-2026-108082 middleware: prod [unchecked]
Symfony: ReDoS in HeaderUtils::split() reachable through the Cache-Control request header
published 3h ago · 0 articles · official fix: 6.4.46
```
*Illustrative output built from real feed data. Tracking is per environment, so the same CVE can be open in prod and fixed in staging.*
> **What's new in 2.0**
> - Each project has [its own update schedule](docs/overview.md#update-schedule-per-projec