Skip to main content
Menu

Changelog

What changed in cve.now's feed, REST API, MCP server and pages, newest first. Dates are UTC. The same list is JSON at /changelog.json and an RSS feed at /changelog.xml.

AddedAPI · MCP · Web · CLI

Malicious packages are advisories, and check fails on them

OSV's MAL- reports and GitHub's malware advisories are now advisories on cve.now. /api/v1/check, the MCP check_stack tool and cve.now check report an installed malicious release as a critical finding with malicious: true, and the CLI exits non-zero on it.

  • /api/v1/advisories?malicious=true and /feed?type=advisory&malicious=true list them. A malicious advisory's page is noindex and is not in the sitemaps.
  • debug@4.4.2 and chalk@5.6.1 are findings; chalk@5.6.0 is not.
  • CLI 0.4.0 carries the malware handling; the GitHub Action defaults to it.
ChangedMCP

The MCP server returns an Mcp-Session-Id

initialize now answers with an Mcp-Session-Id header, a signed token that holds only the client's name and version. Sending it back changes nothing, and no client needs to.

ChangedWeb

Sign in in a new tab with visible progress

Continue with Sazabi opens sign-in in a new tab while the original page shows progress, offers Cancel and continues automatically after sign-in. If the browser blocks the new tab, sign-in continues in the current tab.

FixedWeb

Sign in with a Sazabi account that has no display name

Signing in with a verified Sazabi account that has no display name now completes. Your verified email is used as the display name until Sazabi supplies one.

ChangedAPI · MCP · Web

Search reads a misspelled word as a vendor, technology or package

GET /api/v1/search, entities.search and /search now read each word of 5 or more characters against vendor, technology and package names, so githb returns GitHub and axiom suggests axios. The page says when it also searched a corrected word.

  • resolved.words lists { word, outcome, source, as } for each such word: exact, corrected (also searched as the name in as), nearby (a real word beside a name) or none. A quoted word is never corrected.
  • items puts an exact or corrected name first, then entries that name the word in a title or entity field, then nearby names, then the other matches.
  • Vendor, technology and package rows in items carry match as { name, kind } and entries, the advisories naming the entity (0 when none).
  • suggestions carries reason: spelling is the query with a misspelled word written as the name it is near, and now comes with results; broader is still sent only when nothing matched.
  • note is sent only when items is empty, and says what was searched and what was not. type:package axios no longer carries it beside the package row.
  • /search shows "Also showing results for" a corrected word, with a link that searches only the typed word, and "Did you mean" for a nearby one. The search box suggests the same names as you type, so githb suggests GitHub.
  • Nothing is renamed or removed; total and entries keep their meaning.
AddedAPI · MCP · Web

Package answers carry an advisory state

Package pages, GET /api/v1/packages/<ecosystem>/<name>, get_package and each /api/v1/check row now carry advisoryState, reasons, asOf and validUntil. A package the registry lists with no advisory answers no_known_advisories, not a 404, as each ecosystem rolls out.

  • advisoryState is has_advisories, no_known_advisories, unconfirmed or not_indexed. no_known_advisories means no advisory cve.now reads names the package as of asOf, never that it is safe.
  • unconfirmed is never a 2xx and has no advisories key: 503 or 429 with Retry-After, or 409 for case_variant. reasons says why, such as source_stale, recently_published or lookup_limited.
  • not_indexed is the 404 for a name the registry does not know, an invalid name or an unsupported ecosystem, and nothing is stored for it.
  • /api/v1/check adds complete, counts per state and packages, a row per version. A row may carry recentRelease for a version under 30 days old; it changes neither the state nor complete.
  • A package with advisories stays has_advisories with the fields it had. A daily comparison with osv.dev holds an ecosystem as unconfirmed (source_stale) while it lacks a listed record.
AddedAPI · Feed

Follow what changed with since, ids and ETag

GET /api/v1/entries and /api/v1/cves take since (what changed after a time, up to 7 days back, with no 400-result cap) and ids (up to 25 entries in one request). Every GET under /api/v1 and every feed now sends an ETag and answers If-None-Match with 304 and no body.

  • ?since=2026-11-08T00:00:00Z lists the entries written after that time, oldest change first, as { items, next_cursor, next_since, has_more }. Page with next_cursor while has_more is true, then keep next_since.
  • An entry withdrawn or merged away is a tombstone with status and updatedAt. A since older than 7 days answers 400 since_too_old with max_since.
  • ?ids=CVE-2024-3094,CVE-2023-4863 returns those entries in { items, missing, next_cursor }, at most 25 ids (400 too_many_ids over that). With since it returns only the ones that changed.
  • A single entry read is now cached for 15 minutes instead of 5, so a client that re-reads one id every few minutes mostly gets a cached answer. Use since when you need changes sooner.
  • The polling loop is at https://cve.now/llms.txt and https://cve.now/agents#polling. Every existing request and response is unchanged; the 401 depth_limit message now also points at since.
AddedAPI · MCP

Check findings name the CVE and advisories they group

Each finding from /api/v1/check and the MCP check_stack tool now carries cves, advisories, matchedBy and malicious: the CVE and advisory ids that describe the same vulnerability, which advisories matched, and whether the package is malware.

  • id is the group's id: its smallest CVE, else its first-seen advisory. A finding with one id lists it in cves or advisories.
  • The fields are additive; nothing an existing client reads changes.
DeprecatedWeb · API · MCP · Feed

kind=ransomware and kind=breach on breaches are replaced

A breach no longer has a kind. kind=ransomware still answers as ransomware=true, kind=breach as type=breach, and vector=malware_ransomware as vector=malware, until the sunset.

`kind=ransomware` and `kind=breach` on breaches are replaced: old names
BeforeNow
kind=ransomwareransomware=trueOn breaches. ransomware=false lists the breaches no report ties to ransomware.
kind=breachtype=breachEvery breach, as before.
vector=malware_ransomwarevector=malwareA breach that began with malware. Ransomware is the ransomware fact now, not a way in.

Sunset

  • /api/v1/breaches (kind still on each row, derived from ransomware), /api/v1/search, /feed, /search and the MCP tools take the old values the same way.
  • A breach is ransomware: true only when a press, vendor or official report says ransomware was deployed or systems were encrypted, with that sentence quoted. A group's name alone does not count.
AddedWeb · API · MCP · Feed

Breaches carry ransomware, a quoted fact

Each breach page, .md copy and /api/v1/breaches row says whether a report ties the incident to ransomware. The Ransomware tab on /breaches lists them.

  • ransomware is true or false in /api/v1/breaches, a filter beside data, vector and size, and a search key (ransomware:true).
  • A breach page shows the report's sentence when the answer is yes.
ChangedAPI · MCP

Without a key, lists and searches reach the newest 400 results

/api/v1/entries, /api/v1/cves, /api/v1/search and the MCP list and search operations serve the newest 400 results to a caller with no key; a page past that answers 401 depth_limit, and deeper access will require a free API key, which is coming soon.

  • Paging with next_cursor works as before for the first 400 results, two pages of 200; the page after them is refused.
  • Limits are per caller across every server: 30 searches a minute, 120 entry reads a minute, 100 MCP tool calls in 10 minutes. Over one, a request answers 429 with Retry-After.
  • The limits are written down at https://cve.now/agents#limits.

AddedCLI

The CLI checks only what a pull request adds

cve.now check --base <ref> lists and fails on only the findings that are new since a commit or branch. --ignore-dev keeps development-only packages from failing the run, and --format github adds GitHub Actions annotations and a job summary.

  • An entry already on a package at <ref>, at any version, is counted and not listed.
  • Base lockfiles are read with your local git; only package names, versions and ecosystems are sent, as before.
FixedWeb · API · MCP · Feed

Entries load faster when many requests ask at once

Requests that name several entries now share one lookup, and one slow lookup no longer sends the next seconds of requests down the slower path. /api/v1/entries/<id>, feeds, pages and the MCP server answer faster under load.

  • A request that loads many entries starts with one, then two, four and eight at a time, so one slow entry holds up a few reads, not the whole list.
  • Lists (/api/v1/entries, feeds) keep their shape and order.
  • Nothing changes while entries load normally.
ChangedWeb · API · MCP · Feed

Every CVE has one headline on every surface

An entry's title is the same headline on the page, the feed, REST, MCP and the .md copy. sourceTitle carries the CNA's own title and titleTags lists what the headline dropped.

  • Titles that were cut at 140 characters are re-derived from the whole CNA title.
  • A CVE that affects several products is named by its vendor instead of the first product listed.

AddedWeb · API · Feed

The changelog has its own page, JSON and feed

/changelog lists every change as one entry with its date, kind and surfaces. /changelog.json and /changelog.xml (RSS, or ?format=atom and ?format=json) carry the same list.

  • /agents shows the latest five entries and links to the full list.
  • A response that carries a renamed name now sends a Link header to /changelog instead of /agents#changelog.
FixedWeb · API · Feed

After one slow entry load, the rest of a request fails fast

Once one entry is slow to load, the rest of that request does not wait for more: /api/v1/entries/<id>, packages and stacks answer 503 with Retry-After: 5 at once, not after another 20 seconds.

  • Lists (/api/v1/entries, feeds) keep their shape and order, and an item that could not be checked stays as the last sync wrote it.
  • A page or route serves the last good copy of an entry when it has one.
  • From 2026-11-13 this also holds when a request loads several entries at once, not only after the first slow one.
  • Nothing changes while entries load normally.
ChangedAPI

Search returns facets only with facets=true

/api/v1/search returns the facets object only with facets=true. It was on unless facets=false.

  • Most callers never read facets, and leaving them out makes a broad search much faster.
FixedWeb · API

A slow page answers with a recent copy, not a 503

A page that takes too long to update answers with a recent copy when cve.now has one. The copy carries an X-Cve-Now-Stale header holding its age in seconds.

AddedAPI

Status reports how fresh each source is

GET /api/v1/status carries a freshness block: how many sources cve.now follows, how many it fetched, which ones are failing and when the newest fetch happened.

  • The block has sources_total, sources_read, failed_sources and newest_read_at.
  • Each source that has not been fetched is listed with its pipeline, its error and unread_for_ms.

ChangedWeb · API · MCP · CLI

Every entity type is served the same way on both sites

Every entity type has a page, a REST list and get, rows in search results, the common MCP operations and the common CLI commands, on cve.now and on down.guide. After each deploy a live probe requests every one of them.

  • cve.now and down.guide use the same operation names, so a client written for one works on the other.
ChangedWeb

The developer page moved to /agents

/developers answers 308 to /agents, which holds the MCP setup, the REST reference, the feeds and the changelog.

DeprecatedMCP

The old MCP tools are no longer listed

The old tools (get_vulnerability, list_feed, check_stack and the rest) stay callable and answer as before, but tools/list no longer shows them. They leave these docs on 2027-01-10.

The old MCP tools are no longer listed: old names
BeforeNow
get_vulnerabilitycve.get
list_feedfeed.read
check_stackstack.check
get_leaderboardleaderboard.get
searchentities.searchThe search tool now finds an operation; entities.search searches the data.
get_packagepackage.get
send_feedbackfeedback.send

Sunset

ChangedMCP

The MCP server lists two tools that never change

search finds an operation and execute runs one. Every capability is an operation, so a new one never changes the tool list.

  • The operations are cve.get, feed.read, stack.check, entities.search, <type>.list and <type>.get, each with a REST twin.
ChangedWeb · API · MCP

Search is one search, the same on cve.now and down.guide

type: and the type parameter take entity types, date: is the shared name for published:, and filter:critical|kev|epss picks the priority slice.

  • Entity types are cve, early-warning, breach, vendor, package and tech. early_warning, early warnings and breaches together, and all still work.
  • items holds the matching entries and the vendors, technologies and packages the query names, each tagged with its type, an exact name match first.
  • entries holds the entries alone, as before.
  • facets gains type and confidence.
AddedAPI

Every entity type has a REST list and get in one shape

/api/v1/cves, /early-warnings, /breaches, /vendors, /packages and /tech answer { items, next_cursor, total? }. Each takes the type's own filters, q on a catalog type, limit (1 to 200, default 30) and cursor.

  • A parameter that is unknown or does not apply is a 400.
  • A missing id is a 404 with { error: "not_found", type, id }.
AddedAPI · MCP

type is on every object

type (cve, early-warning, breach or package) is on each entry, each row of /api/v1/entries, /api/v1/entries/<id> and get_package.

  • /api/v1/entries also reads type=cve|early-warning|breach, and serves its rows as items beside the old key entries, which stays.
  • A cached entry from before this change gains type and url as it is refreshed.

AddedAPI

Vulnerabilities name the products they affect

Every vulnerability entry names its affected products in vendors, products, packages and tech.

  • vendors is the slug of /vendors/<slug>.
  • tech is the slug of /feed?tech=<slug> and the rule it matched on.
DeprecatedAPI · MCP · Feed

Old search keys and result fields are renamed

category: and the old kind: values in search, and the result fields type and category, are replaced by kind.

Old search keys and result fields are renamed: old names
BeforeNow
category:kind:In search. Values are vulnerability, breach, ransomware, malicious-package or outage.
kind:cve, kind:ghsa, kind:malicious, kind:ecosystem and kind:osvkind:vulnerability, or the kind of early warningIn search. kind: now takes entry kinds.
typekindField of each result in entries. items[].type is the entity type.
categorykindField of each search result.

Sunset

  • A response that still carries an old name sends Deprecation and Sunset headers until 2027-01-09, then the old names stop.
AddedAPI · Feed

kind is on every entry

/api/v1/entries/<id>, each row of /api/v1/entries and each search result carry kind: vulnerability, breach, ransomware, malicious-package or outage.

  • In a search result kind used to name the advisory database (cve, ghsa, osv and so on) and now names the entry's kind.
AddedAPI · MCP

The entry schema is published

The schema of an entry is at /schemas/entry.json, the same one get_vulnerability declares as its outputSchema.

ChangedWeb · API

Confidence reads Confirmed, Corroborated or Unverified

Confidence is labeled the same way everywhere. The breaches tab that read Reported, not confirmed now reads Corroborated, and ?show=reported still selects it.