Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-103902 Overview
CVE-2026-103902 is an improper verification of cryptographic signature vulnerability [CWE-347] affecting multiple DigiDoc products from the Estonian e-ID software suite. The flaw allows an attacker to craft forged digital signatures that affected DigiDoc software renders as valid. Because DigiDoc is widely used for legally binding electronic signatures, successful exploitation undermines the integrity guarantees of signed documents. The vulnerability affects libdigidocpp from 4.0.0 before 4.5.0, DigiDoc4 from 4.6.0 before 4.11.0, DigiDoc Android from 2.7.0 before 3.1.0, and DigiDoc iOS from 2.7.0 before 3.1.0. The issue is reachable over the network and requires no authentication or user interaction.
Critical Impact
Attackers can produce forged digital signatures that affected DigiDoc software accepts as valid, enabling repudiation attacks and document integrity compromise.
Affected Products
- DigiDoc libdigidocpp from 4.0.0 before 4.5.0
- DigiDoc DigiDoc4 from 4.6.0 before 4.11.0
- DigiDoc DigiDoc Android from 2.7.0 before 3.1.0 and DigiDoc iOS from 2.7.0 before 3.1.0
Discovery Timeline
- 2026-10-12 - CVE-2026-103902 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-103902
Vulnerability Analysis
The vulnerability resides in the signature verification logic shared across the DigiDoc product family. Affected versions fail to correctly validate cryptographic signatures on signed containers, which lets a crafted container pass verification even when the signature is forged or does not match the signed content. This breaks the core trust model of the DigiDoc format, which is used for legally binding Estonian e-ID signatures. Downstream applications and relying parties that trust DigiDoc's verification result may accept fraudulent documents as authentic.
Root Cause
The root cause is improper verification of a cryptographic signature [CWE-347] within the DigiDoc signature validation path. The verification routine does not sufficiently bind the signature to the signed data or to the signer's certificate, allowing an attacker to construct containers that pass validation despite not being authentically signed. The upstream fix is tracked in the libdigidocpp project. See the libdigidocpp pull request 735 for the code-level change.
Attack Vector
An attacker crafts a malicious DigiDoc container that embeds a forged signature structure. The attacker then delivers the container to a victim over any network channel such as email, web download, or a document portal. When the victim opens the container in a vulnerable version of libdigidocpp, DigiDoc4, DigiDoc Android, or DigiDoc iOS, the application reports the signature as valid. The attack requires no privileges and no user interaction beyond opening or processing the document.
No verified public proof-of-concept code is available. See the vendor references for technical details.
Detection Methods for CVE-2026-103902
Indicators of Compromise
- DigiDoc containers (.asice, .bdoc, .ddoc) received from untrusted sources that validate as signed by unexpected or implausible signers.
- Signed documents whose signer certificate chain, timestamp, or OCSP response does not independently verify against the Estonian trust list.
- Workstations or mobile devices running libdigidocpp versions below 4.5.0, DigiDoc4 below 4.11.0, or DigiDoc mobile apps below 3.1.0.
Detection Strategies
- Inventory endpoints and mobile devices for installed DigiDoc components and flag versions below the fixed releases.
- Perform out-of-band signature validation of high-value signed documents using an updated reference implementation before accepting them as valid.
- Compare the signer identity reported by DigiDoc against expected business counterparties and escalate mismatches.
Monitoring Recommendations
- Log and alert on DigiDoc client version strings during document ingestion workflows.
- Monitor email and file-sharing gateways for inbound .asice and .bdoc attachments and correlate with sender reputation.
- Track verification failures and anomalies reported by updated DigiDoc clients across the environment.
How to Mitigate CVE-2026-103902
Immediate Actions Required
- Upgrade libdigidocpp to 4.5.0 or later on all systems that embed the library.
- Upgrade DigiDoc4 desktop clients to 4.11.0 or later.
- Upgrade DigiDoc Android and DigiDoc iOS mobile applications to 3.1.0 or later.
- Re-validate recently received high-value signed documents using a patched client before relying on them.
Patch Information
Fixed versions are libdigidocpp 4.5.0, DigiDoc4 4.11.0, DigiDoc Android 3.1.0, and DigiDoc iOS 3.1.0. The upstream code change is tracked in the libdigidocpp pull request 735. Release coordination is described in the ID.ee software release announcement.
Workarounds
- Restrict acceptance of DigiDoc containers to workflows where every signature is independently verified by a patched client.
- Require secondary verification such as a trusted timestamp authority check or counter-signature review for high-value transactions.
- Block or quarantine .asice, .bdoc, and .ddoc attachments at the mail gateway until all endpoints are upgraded.
# Configuration example
# Verify installed libdigidocpp version on Linux endpoints
dpkg -l | grep -i libdigidocpp
# Expected: version >= 4.5.0
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

