Read the docs

FINISH transcript in libspdm omits new OpaqueData fields

Priority LOW 26CWE-325Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · High · None
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

libspdm, the DMTF sample implementation of the SPDM specifications, is affected in version 1.4.0. Version 1.4.0 added OpaqueDataLength and OpaqueData to the FINISH and FINISH_RSP messages, but the transcripts covered by the FINISH signature and HMACs were not updated to include them (CWE-325). An active attacker can modify the opaque data in transit without invalidating the FINISH signature or HMAC.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

libspdm is a sample implementation that follows the DMTF SPDM specifications. In version 1.4.0, both the FINISH request (Table 80) and the FINISH_RSP response (Table 81) gained two new fields, OpaqueDataLength and OpaqueData, placed before the trailing signed/authenticated field. The transcript definitions used to compute and verify the FINISH signature, the FINISH HMAC (RequesterVerifyData), and the FINISH_RSP HMAC (ResponderVerifyData) were not updated and still terminate with a step of the form. Per DSP0274, the "SPDM Header Fields" are only the four header bytes (SPDMVersion, RequestResponseCode, Param1, Param2). A literal reading therefore excludes OpaqueDataLength and OpaqueData, even though those fields are transmitted before the trailing signature/HMAC field. Because the signature/HMAC must cover every field transmitted before it to "protect the entire handshake against manipulation by an active attacker," an active attacker could otherwise modify the opaque data in flight without invalidating the signature or HMAC. This issue has been patched in version 1.4.1.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00138 3rd percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
DMTFlibspdm= 1.4.0—No fix listedCNA
  • libspdm VendorDMTF Affected = 1.4.0 Fixed in — No fix listed CNA

Remediation

Upgrade libspdm to version 1.4.1, which patches this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Timeline

  1. 2026-11-11 Threatist record created from CVE-2026-61810
  2. 2026-11-12 Priority changed: MEDIUM → LOW
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2023-14837 DMTF-2023-0001: SPDM mutual authentication bypass CVSS 3.1CRITICAL 9.1
  • TI-2023-15966 Responder can Invoke Undefined Behavior in libspdm Requester CVSS 3.1HIGH 7.5
  • TI-2026-92241 libspdm: libspdm_x509_verify_cert_chain() does not verify CA nameConstraints / pathLenConstraint CVSS 3.1MEDIUM 4.4

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences