Skip to content
Back to search

cve.now

A free, public vulnerability feed: CVE, GHSA, OSV, CISA KEV and EPSS merged into one entry per vulnerability. RSS, JSON API and MCP. Docs and issues only.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sazabi--cve-now/badge.svg)](/listings/sazabi--cve-now)

HTML

<a href="/listings/sazabi--cve-now"><img src="/api/listings/sazabi--cve-now/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 137 lines
  1. # cve.now
  2. **A free, public vulnerability feed.** [cve.now](https://cve.now) merges the CVE List, the GitHub Advisory Database, OSV, NVD, ENISA's European Vulnerability Database (EUVD), CISA's Known Exploited Vulnerabilities catalog (KEV), FIRST EPSS scores and Exploit-DB into one deduplicated entry per vulnerability, and publishes it as RSS, Atom, JSON Feed, a JSON API and an MCP server. No account, no API key.
  3. This repository is cve.now's home on GitHub: what it is, how to use it, and where to report problems. The service is built and run by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=github&utm_content=readme-intro); its source code is not public.
  4. ## Feeds
  5. One endpoint, `https://cve.now/feed`, narrowed with filters that combine freely. RSS by default; add `format=atom` or `format=json`.
  6. | Feed | URL |
  7. | --------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
  8. | Critical: in CISA KEV, CVSS 9+ in a listed technology, or CVSS 7+ with an EPSS score of 0.1 or more | `https://cve.now/feed?filter=critical` |
  9. | New CISA Known Exploited Vulnerabilities | `https://cve.now/feed?filter=kev` |
  10. | Every entry | `https://cve.now/feed` |
  11. | One technology | `https://cve.now/feed?tech=nextjs` |
  12. | One package ecosystem | `https://cve.now/feed?ecosystem=npm` |
  13. | Combined | `https://cve.now/feed?filter=critical&tech=nextjs&format=json` |
  14. | Several values | `https://cve.now/feed?tech=nextjs,react&ecosystem=npm,pypi` |
  15. `filter`, `tech` and `ecosystem` each take one value or several, as a comma list or repeated. An entry must match any listed value of a field and every field given. A feed combines at most 16 combinations of values (for example 4 technologies x 4 ecosystems). `list_feed` in the MCP server takes the same three fields as lists.
  16. Ecosystems: `npm`, `pypi`, `go`, `maven`, `crates.io`, `packagist`, `rubygems`, `hex`, `nuget`.
  17. Technologies: `nextjs`, `react`, `node`, `express`, `django`, `flask`, `rails`, `spring`, `log4j`, `kubernetes`, `docker`, `nginx`, `apache-httpd`, `openssl`, `postgresql`, `mysql`, `redis`, `microsoft-sql-server`, `oracle-database`, `mariadb`, `ibm-db2`, `mongodb`, `sap-ase`, `php`, `wordpress`, `jenkins`, `gitlab`, `fortinet`, `citrix`, `ivanti`, `cisco-ios`, `palo-alto-panos`, `vmware`, `microsoft-exchange`, `chrome`, `linux-kernel`. Missing one? [Request it](https://github.com/sazabi/cve.now/issues/new?template=technology-request.yml).
  18. In Slack, run `/feed subscribe https://cve.now/feed?filter=critical` in any channel.
  19. ## Check your stack
  20. Upload a lockfile at [cve.now](https://cve.now) to get a shareable report and an RSS feed of only the entries that affect your exact package versions. Supported: `package-lock.json`, `bun.lock`, `pnpm-lock.yaml`, `yarn.lock`, `requirements.txt`, `poetry.lock`, `uv.lock`, `Cargo.lock`, `go.sum`, `Gemfile.lock`, `mix.lock`, `composer.lock`, `Pipfile.lock`, `packages.lock.json` (NuGet), `gradle.lockfile`, `flake.lock` (checked by the git commit each input pins, through OSV; nixpkgs package CVEs are not checked).
  21. For a short package list, build the feed URL yourself:
  22. ```
  23. https://cve.now/stack?p=npm:lodash@4.17.20,pypi:django@4.2.0
  24. ```
  25. ## MCP server
  26. A remote Streamable HTTP MCP server at `https://mcp.cve.now/mcp`, no authentication. Two tools that never change: `search` finds an operation and `execute` runs it. Operations: `cve.get`, `feed.read`, `stack.check`, `entities.search`, `leaderboard.get`, `feedback.send` and the `.get` and `.list` of every entity type (cve, early-warning, breach, vendor, package, tech). `entities.search` takes a query (`q`) and structured parameters (`severity`, `kev`, `exploited`, `tech`, `ecosystem`, `vendor`, `package`, `published`, `type`), says why each result matched, and suggests broader queries when nothing matches. The old tools (`get_vulnerability`, `list_feed`, `check_stack` and the rest) are deprecated since 2026-11-11 and still answer.
  27. **Claude Code**
  28. ```sh
  29. claude mcp add --transport http cve-now https://mcp.cve.now/mcp
  30. ```
  31. **Codex**
  32. ```sh
  33. codex mcp add cve-now --url https://mcp.cve.now/mcp
  34. ```
  35. **OpenCode** (`opencode.json`)
  36. ```json
  37. {
  38. "$schema": "https://opencode.ai/config.json",
  39. "mcp": {
  40. "cve-now": {
  41. "type": "remote",
  42. "url": "https://mcp.cve.now/mcp",
  43. "enabled": true
  44. }
  45. }
  46. }
  47. ```
  48. **Cursor** (`.cursor/mcp.json`)
  49. ```json
  50. {
  51. "mcpServers": {
  52. "cve-now": { "url": "https://mcp.cve.now/mcp" }
  53. }
  54. }
  55. ```
  56. Then ask your agent to run the `stack.check` operation on your project's lockfile.
  57. The [`plugin/`](plugin) folder packages the same server as a plugin for Cursor and ChatGPT.
  58. To have your agent check dependencies on its own, add this to your project's `AGENTS.md` or `CLAUDE.md`:
  59. ```md
  60. ## Dependency vulnerabilities
  61. Use the cve.now MCP server (https://mcp.cve.now/mcp, no API key) for vulnerability checks:
  62. - Before adding or upgrading a dependency, and when asked whether this project is affected by a CVE, run the `stack.check` operation with the lockfile's contents (or the packages and exact versions).
  63. - For any CVE, GHSA or OSV id, run `cve.get` to see whether it is in CISA KEV, whether its EPSS score has reached 10% (and when), and the fixed versions.
  64. - No matches means cve.now found none, not that the packages are safe.
  65. ```
  66. ## API
  67. | Endpoint | Returns |
  68. | ------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
  69. | `https://cve.now/<id>` | Page for a CVE, GHSA or OSV id |
  70. | `https://cve.now/api/v1/entries/<id>` | The same entry as JSON; a recently synced entry can redirect to a static copy, so follow redirects (`curl -L`) |
  71. | `https://cve.now/api/v1/entries` | All published entries, newest first, paginated with `next_cursor` |
  72. | `https://cve.now/api/v1/search` | Search by `q` and the MCP `search` parameters, with match reasons, facet counts and broader queries (llms.txt) |
  73. | `https://cve.now/api/v1/status` | Source polling health and catalog coverage |
  74. | `https://cve.now/llms.txt` | A plain-text guide for LLMs and agents |
  75. `/feed` and `/api/v1/*` send `Access-Control-Allow-Origin: *`.
  76. ## Issues
  77. [Open an issue](https://github.com/sazabi/cve.now/issues/new/choose) to report:
  78. - a wrong or missing entry
  79. - two entries that should be merged, or one that merged things it shouldn't
  80. - a technology or package ecosystem you want covered
  81. - a disclosure source we should watch
  82. - a bug in a feed, page, the API or the MCP server
  83. For an error in an upstream record (for example a wrong CVE description), we'll point you to the CNA or advisory database that owns it.
  84. **Don't post unpatched vulnerabilities here.** Issues are public. Report a vulnerability in someone else's product to its vendor. Report a vulnerability in cve.now itself to [security@sazabi.ai](mailto:security@sazabi.ai) (see [SECURITY.md](SECURITY.md)).
  85. This repository doesn't accept pull requests: its files are synced from Sazabi's private monorepo, so a direct change would be overwritten. Open an issue instead.
  86. ## Sources and licensing
  87. Data: the [CVE List](https://www.cve.org), the [GitHub Advisory Database](https://github.com/advisories), [OSV](https://osv.dev), the [NVD](https://nvd.nist.gov), [ENISA EUVD](https://euvd.enisa.europa.eu), the [CISA KEV catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog), [FIRST EPSS](https://www.first.org/epss/) and [Exploit-DB](https://www.exploit-db.com). Each entry links to its sources.
  88. Entry summaries are written by a model and labeled as such; they're published under [CC-BY 4.0](https://creativecommons.org/licenses/by/4.0/). Upstream data keeps its own license and attribution.
  89. This product uses data from the NVD API but is not endorsed or certified by the NVD.
  90. The text in this repository is licensed under [Apache 2.0](LICENSE).
  91. ---
  92. Want to know which of these affect your systems? [Sazabi can tell you](https://www.sazabi.com/?utm_source=cve-now&utm_medium=github&utm_content=readme-footer).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.