Skip to content

Lifecycle and firmware currency

POST /api/v1/assets/correlate-cves adds three blocks to each result, after vulnerability matching:

Block Per device Per call (summary) What it answers
lifecycle results[].lifecycle summary.lifecycle Is this product past the vendor's end of sale / end of support?
firmware_currency results[].firmware_currency summary.firmware_currency Is this device on the vendor's latest listed firmware, and how far behind is it?
unsupported_when_assigned results[].cves[].unsupported_when_assigned summary.unsupported_when_assigned Does a CVE record say the product was already unsupported when the CVE was assigned?

These blocks are additive. They never change cves, fix_groups, resolution or result_hash, so existing integrations keep working unchanged.

Who receives them: client plans (Standard, Professional, Enterprise, MSSP) and partner keys (since 2026-10-26). Trial, partner-trial and demo keys receive none of the three blocks. A device whose vendor has no published lifecycle or firmware data gets no block, rather than an empty one.

Rules behind every answer

  • Vendor statements only. Every date and status comes from a vendor publication (product page, lifecycle notice, release history, security advisory), or from a CVE record or CISA advisory restating the vendor. Each fact links its source. Where a fact comes from a community aggregator (endoflife.date: Windows, and software release lines such as Debian, Red Hat Enterprise Linux, VMware ESXi, PostgreSQL, Oracle Java, Apache and Veeam), the answer says so and links both the aggregator and the vendor page it cites.
  • Never "supported" by default. End of support: No is returned only when the vendor states a future end date or lists the product as active. No notice found is never read as supported.
  • Zero CVEs is not "secure". An unsupported product with no known vulnerabilities still says that future vulnerabilities will not be fixed.
  • Versions matter. A statement about some versions only (e.g. "versions 4.0 and prior") applies to a device only when its version falls inside them. Supply version (or firmware_version) to get version-scoped answers.

lifecycle (per device)

"lifecycle": {
  "end_of_support": {
    "answer": "no",
    "date": "2029-01-09",
    "source_url": "https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019",
    "text": "End of support: No. The vendor states support ends 2029-01-09."
  },
  "support_status": "supported",
  "facts": { "end_of_sale": {...}, "end_of_support": {...}, "end_of_life": {...}, "security_support_end": {...} },
  "as_of": "2026-10-20",
  "notice": "Lifecycle information reflects manufacturer publications as of the retrieval date shown. Confirm critical decisions with the manufacturer."
}
Field Meaning
end_of_support.answer yes, no or unknown
end_of_support.date The stated date, when there is one
end_of_support.reason Why the answer is unknown (table below)
end_of_support.text The customer-facing sentence; show it as is
end_of_support.source_url The vendor page, notice or record the answer comes from
end_of_support.listed_by Present only when the answer comes from an aggregator: name, url, cites_url, attribution
support_status supported, security_support_ending_within_12_months, paid_program_only, unsupported or unknown
support_text Plain-language consequence, present for unsupported and paid_program_only
facts Each lifecycle column with its status (ENDED, SCHEDULED_END, STATED_WITHOUT_DATE, NOT_PUBLISHED_BY_VENDOR), date, the vendor's own term (native_term) and source
facts.version_scoped[] Statements about some versions only, with applies_to_versions and version_matched (true / false / "unknown")
editions[] Per-edition facts (e.g. Windows Home and Pro / Enterprise and Education), with applies_to_every_edition when they agree
matched_catalog_item Present when the device matched a vendor part number or model in the lifecycle catalog. match_method is submitted_part_number when your part_number matched it exactly (tried first)

end_of_support.reason (when answer is unknown)

Reason Meaning
not_yet_checked No publication for this product has been read yet
not_publicly_available The vendor's page was read and states no lifecycle date. Contact the vendor
end_of_sale_no_support_date The vendor dates the end of sale (in its own term, e.g. "Discontinued Date", "Last Time Buy") but states no end of support
end_of_life_no_support_date The vendor lists the product as end of life (phased out) but gives no end-of-support date
under_review A lifecycle notice was found but is still being checked
varies_by_edition Editions have different dates; see editions[]
version_needed The vendor's statement covers specific versions; supply the device version
version_not_listed The statements cover other versions, not this one
not_stated_for_version The statements for this version give no end of support
version_scope_unreadable The statement covers some versions only, in wording that can't be compared
conflict Two vendor sources disagree; both are shown

firmware_currency (per device)

"firmware_currency": {
  "status": "behind",
  "line": "Firmware for EDS-518A Series",
  "latest_version": "v3.14",
  "latest_release_date": "2026-03-31",
  "release_notes_url": "https://…/EDS-518A Series_…_Software Release History.pdf",
  "releases_behind": 8,
  "security_notes": [
    {"quote": "Cross-site scripting vulnerability.", "version": "v3.8", "release_date": "2017-05-03", "cve_ids": [], "url": "https://…"}
  ]
}
Field Meaning
status current, behind or unknown
releases_behind Listed releases newer than the device's version
security_notes[] Security-relevant lines quoted from the release notes of the releases the device is missing
reason Why status is unknown: no_version, not_yet_checked, not_publicly_available, series_unknown, series_not_listed, branch_unknown, branch_not_listed, ambiguous_line, order_unresolved, newer_than_listed, version_less_precise
listed_by Only on a software release line listed by endoflife.date: {name, url, attribution}; see below

No version supplied (reason no_version): the latest listed release is still returned (latest_version, latest_release_date, release_notes_url, cited), never compared. When that release is past the device's fix_plan.to_clear_all_fixable.target, latest_clears (cves, known_exploited, target, derived) and latest_clears_text say that the CVEs with a version fix no longer apply at that release by their published version ranges. CVEs with no version fix are never counted as cleared.

Software release lines (endoflife.date, 2026-10-29). For PostgreSQL, Debian, Red Hat, Oracle (Java and Linux), Apache (HTTP Server and Tomcat), OpenSSL and Veeam, a device matched to a release line ("PostgreSQL 16") is compared with the latest release endoflife.date lists for that line, and listed_by names endoflife.date. Only the latest release is known, so releases_behind is null, and only lines whose release notes link is on the vendor's own domain are used. A reported version with fewer parts than the latest (25.0.5 against 25.0.5.0.3) is not compared (version_less_precise). A vendor's own firmware data, where it is served, always takes precedence.

summary.firmware_currency counts devices by status and ranks them (ranked[]), putting first the devices that are behind with security notes, vendor support ended, or known-exploited CVEs.

unsupported_when_assigned (per CVE)

"unsupported_when_assigned": {
  "assigner": "VulDB",
  "text": "The CVE record's assigner (VulDB) marks this vulnerability as affecting a product that was no longer supported when the CVE was assigned. Do not expect a fix.",
  "source_url": "https://www.cve.org/CVERecord?id=CVE-…"
}

This is a statement about the CVE record, attributed to whoever set the tag (often a third party). It changes the device's lifecycle answer only when the tag was set by the vendor's own CVE assigner or by CISA ICS-CERT, and only for the CVE's affected versions.

Coverage

Coverage is per vendor and grows weekly. Products from vendors without published lifecycle data return not_yet_checked or no block. See Lifecycle coverage for the current list of vendors and sources.