Tf Psa Crypto

Vendor:

First CVE: Apr 1, 2026 · Active for under a year

2
Total CVEs
More Total CVEs than 53% of tracked products
2.0
Avg CVEs / Year
Higher CVE frequency than 63% of tracked products
7.1
Avg CVSS
Higher Avg CVSS than 45% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Tf Psa Crypto over time

Volume of CVEsAvg CVSS Base Score
First CVE
Apr 1, 2026
3 months ago
Most Recent CVE
Apr 1, 2026
117 days ago

CVE Severity & Scoring

Tf Psa Crypto2 CVEs
All CVEs352,785 CVEs
MediumCritical
Attack Vector
Local1 (50.0%)
Network1 (50.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (50.0%)
High1 (50.0%)
Unknown0 (0.0%)
User Interaction
None2 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None2 (100.0%)
Unknown0 (0.0%)

Top CVEs

Signals from CVEs in this product scope (2 CVEs).

2 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
CVE-2026-34872CRITICAL
An issue was discovered in Mbed TLS 3.5.x and 3.6.x through 3.6.5 and TF-PSA-Crypto 1.0. There is a lack of contributory behavior in FFDH due to improper input validation. Using fi
Apr 1, 20269.130NONO
CVE-2025-66442MEDIUM
In Mbed TLS through 4.0.0, there is a compiler-induced timing side channel (in RSA and CBC/ECB decryption) that only occurs with LLVM's select-optimize feature. TF-PSA-Crypto throu
Apr 1, 20265.118NONO
View all 2 CVEs →

Exploit Exposure

Signals from CVEs in this product scope (2 CVEs).

CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%

Social Chatter

Signals from CVEs in this product scope (2 CVEs).

Media Mentions

Signals from CVEs in this product scope (2 CVEs).

Top CNAs Publishing CVEs For Tf Psa Crypto

Top CWEs

Versions

VersionCVE CountAvg CVSSAvg EPSSKEVExploits
1.0.019.10.2%00