CVE-2025-67903
Description
Northern.tech Mender Client 5 before 5.0.4 allows a Cryptographic signature verification bypass.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Mender Client 5.0.0-5.0.3 (and earlier) allows bypass of cryptographic signature verification on artifacts, enabling malicious file injection.
Vulnerability
The Mender Client versions 5.0.0 through 5.0.3 contain a cryptographic signature verification bypass vulnerability. The bug allows an attacker to add additional files to a Mender Artifact without causing the signature or checksum verification to fail. The additional file is not listed in the update manifest, so it bypasses verification. Only custom update modules that install or run such files can be exploited; default update modules (single file, directory, rootfs) are not affected. [1]
Exploitation
An attacker must deliver a malformed artifact to the target device, either via Mender Client in standalone mode or through a custom update server, as the Mender Server rejects these artifacts. The attacker needs a custom update module that will write or execute the injected file. No authentication is required if the attacker can control the update delivery. [1]
Impact
Successful exploitation allows the attacker to inject a malicious file that, when installed or executed by the custom update module, can lead to full device compromise, including arbitrary code execution and potential device takeover. [1]
Mitigation
The vulnerability is fixed in Mender Client version 5.0.4. Users are advised to upgrade. Affected versions include 5.0.0 to 5.0.3, and likely earlier unsupported versions. No workarounds are provided. [1]
AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2- Range: <5.0.4
- Range: <5.0.4
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.