Skip to main content
Mallory
MediumVulnerability

CVE-2026-25834: Mbed TLS Signature Algorithm Injection / Algorithm Downgrade

Published Apr 1, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS0.14%3rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
ARM HoldingsTrustedfirmware
IdentifiersCVE-2026-25834CWE-757

CVE-2026-25834 is an algorithm-downgrade vulnerability in Mbed TLS versions 3.3.0 through 3.6.5 and version 4.0.0. The issue is characterized as signature-algorithm injection, allowing manipulation of signature-algorithm selection during the relevant cryptographic protocol processing.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A successful exploit can cause use of a weaker or unintended signature algorithm, undermining the security guarantees expected from cryptographic negotiation and potentially enabling authentication or integrity protections to be weakened.

Mitigation

If you can’t patch tonight, do this now.

Where immediate upgrade is not possible, limit exposure to untrusted peers and enforce strong, explicitly configured signature-algorithm policies where the application or TLS integration supports them. Monitor for anomalous TLS handshake failures or unexpected negotiated signature algorithms.

Remediation

Patch, then assume compromise.

Update Mbed TLS 3.x installations to version 3.6.6 or a later vendor-supported release containing the fix. The available information identifies version 4.0.0 as affected but does not specify the corresponding fixed 4.x release; consult the Mbed TLS vendor advisory and apply its designated patched version.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ARM HoldingsMbed Tlsapplication
TrustedfirmwareMbed Tlsapplication
FAQ

Frequently asked questions

Is CVE-2026-25834 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-25834 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-25834?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-25834.
Is there a patch for CVE-2026-25834?
Update Mbed TLS 3.x installations to version 3.6.6 or a later vendor-supported release containing the fix. The available information identifies version 4.0.0 as affected but does not specify the corresponding fixed 4.x release; consult the Mbed TLS vendor advisory and apply its designated patched version.
What products are affected by CVE-2026-25834?
ARM Holdings Mbed Tls and Trustedfirmware Mbed Tls.
How severe is CVE-2026-25834?
CVE-2026-25834 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.14% (3rd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.