Compliance research

FIRST CVSS v4.0 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 13-142 to 13-140 and state declaration-acceptance date(s) for the replaced recognition: recognition 13-142: 2028-07-02. Compare the exact edition and recognition limitations with your reports before agreeing the submission evidence or further work.

Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.

Exact FDA recognition records

Compare the edition and the recognized portion

Read these columns together. A complete recognition is not a device-specific testing instruction. The limitations are the FDA’s public metadata; the licensed standard itself is not reproduced.

Recognition / editionPublic recognition limitationsDeclaration transition context
FDA 13-142
FIRST CVSS v3.1

Common Vulnerability Scoring System version 3.1

Complete

Complete standard

[4] [5]
Exported transition expiration: 07/02/2028
FDA 13-140
FIRST CVSS v4.0

Common Vulnerability Scoring System version 4.0

Complete

Complete standard

[2] [3]
No expiration date is stated in this acquired export row. That is not a guarantee of indefinite recognition.

What FDA’s transition statement says

Recognition 13-142 → 13-140

FDA recognition of FIRST CVSS v3.1 [Rec# 13-142] will be superseded by recognition of FIRST CVSS v4.0 [Rec# 13-140]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 13-142] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 13-142] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [1] [6]

FDA public recognition metadata describes use of declarations of conformity in support of premarket submissions. A recognition transition is not a universal retesting deadline, a product ban, or proof that this standard applies to your device. The technical differences between licensed editions, adequacy of existing reports, buyer-specific route and final test scope remain incomplete. The comparison below does not reproduce the standard or establish FDA approval.

Method: Exact directed old-to-new statements are reconciled across both acquired sheets and the old export date. No name-similarity mapping or technical-clause inference.

Build your edition-to-report handoff matrix

Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.

  1. Which edition is actually in your evidence?

    Reconcile each report and declaration against FIRST CVSS v4.0 and the replaced designation(s) FIRST CVSS v3.1. Record amendments and the exact report/device revision. A similar standard number is not an edition match.

    Useful evidence: Report cover, method/edition references, amendments, declarations and device/configuration revision.

  2. Does the declaration cover the recognized portion?

    Use the complete FDA public limitation text in the comparison table. Map each listed exclusion, where present, to the relevant report sections and obtain a reasoned evidence assessment. Complete recognition still does not determine device applicability.

    Useful evidence: Recognition-to-report coverage matrix, excluded-clause assessment and the licensed edition used by your specialist.

  3. How does the recorded transition affect your submission plan?

    Record planned declaration/submission dates against the FDA sheet’s acceptance date(s): recognition 13-142: 2028-07-02. This concerns declarations supporting premarket submissions to the replaced recognition; do not treat it as a blanket deadline to retest or stop selling.

    Useful evidence: Submission plan, intended declaration references, dated recognition-sheet check and rationale for the chosen evidence route.

  4. What changed beyond the designation?

    Ask the specialist to assess the actual licensed edition/amendment differences for your design, materials, software and use environment. Separate a documented evidence gap from a changed title. This metadata comparison does not establish which tests changed or must be repeated.

    Useful evidence: Edition gap assessment tied to the device and existing evidence, with a bridging rationale and unresolved inputs.

  5. What should the quote include?

    Request a report/recognition reconciliation and a justified gap assessment first. Separate any proposed additional evaluation or testing, samples, methods, deliverables and exclusions; agree them only after applicability and existing evidence are assessed.

    Useful evidence: A scoped evidence-assessment quote; separately identified conditional work and report ownership.

Work packages and dependencies

Questions for providers

Sources and data dates

Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.

FDA — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot b027589c9df8f688a4cf3d0a394f396ecd5c7864b873851d7219837d8083ec5c

  • [1] HTML tr 22 / Transition Period / nested table · record 07207f3a64b0123c7dbb0595a91275353c81aa4e32d9c836178f185a43fd826e
  • [4] HTML tr 18 / Extent of Recognition / nested table · record 5887a0932ef5915bb3afaf46dccef1d49f05ce54b57277a048e9a43079ba14d4

FDA — recognition metadata exported through the official search form ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 94ccf56dc846c7f6d78d6ad77dc6e87d1803ac3612af01d6894949e34c4a78d8

  • [2] CSV row 73 · record 1e10bd8ef1bd5a7c403709dbcb8e9252d446d3adcda4a58e8a5c38db3dd1babf
  • [5] CSV row 271 · record 58e1b82f0146315b281636e1987fefdc1fd6b9667dd0d934e8a42ca4d4e44cb0

FDA — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot dc6ada64c455d9520db7693e3d88132bafc0a17464c3f9c2345c5c7e389b8312

  • [3] HTML tr 18 / Extent of Recognition / nested table · record 2108dee0c75402500cba2fa1ff611e977397b0919c65d9be5e7e9afee994a8c5
  • [6] HTML tr 22 / Transition Period / nested table · record 8045081e322094bcb26c94c744996de273448e054945d10a1d27c96adbe86521

Prepare an editable project brief

Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.

Choose work packages to discuss

Compare FDA 510(k) Submission Services