CISA ADP Vulnrichment

Answer in brief

CVE-2026-73064 records a Low severity (CVSS 2.9) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps trustedfirmware/Mbed TLS (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 2.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 2.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps trustedfirmware/Mbed TLS (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
trustedfirmware/Mbed TLSgeneric	>=3.2.0 <3.6.7 \|\| >=4.0.0 <4.1.1	3.6.7, 4.1.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for trustedfirmware/Mbed TLS.
Review the reported fix. Update trustedfirmware/Mbed TLS to 3.6.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

In Mbed TLS 3.2.0 though 3.6.6 and 4.0.0 through 4.1.0, an attacker who can cause an entropy source to fail can remove or inject bytes into the start of the TLS stream. This only affects TLS 1.3 servers.

Quoted source text, attributed separately from HOL analysis.