RIA libdigidocpp integrity loss from improper signature validation
- Exploited
- No known exploitation
- Fix
- Fixed in libdigidocpp 4.5.2 · DigiDoc4 4.11.2 · DigiDoc 3.2.0
- Who is exposed
- Not reported
Summary
Improper certificate and signature validation flaws affect libdigidocpp, DigiDoc4, and DigiDoc from Estonian Information System Authority (RIA), including DigiDoc on Android and iOS. A remote attacker, without logging in, can exploit them if a user takes an action, such as opening a crafted file, which can lead to high integrity impact on the affected software.
Written by a model
Original description
Improper certificate validation vulnerability in Estonian Information System Authority (RIA) libdigidocpp, Estonian Information System Authority (RIA) DigiDoc4, and Estonian Information System Authority (RIA) DigiDoc on Android and iOS.
This issue affects libdigidocpp: from 3.13.0 before 4.5.2; DigiDoc4: from 4.0.0 before 4.11.2; DigiDoc: from 3.0.0 before 3.2.0.
What to do
Upgrade to a fixed version: libdigidocpp 4.5.2 · DigiDoc4 4.11.2 · DigiDoc 3.2.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128978 (Improper Verification of Cryptographic Signatures in libdigidocpp), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128978 (entry last updated 2026-11-19):
Affected:
- Estonian Information System Authority (RIA) libdigidocpp: from 3.13.0, fixed in 4.5.2
- Estonian Information System Authority (RIA) DigiDoc4: from 4.0.0, fixed in 4.11.2
- Estonian Information System Authority (RIA) DigiDoc: from 3.0.0, fixed in 3.2.0
Fixed versions: 4.5.2, 4.11.2, 3.2.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128978 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128978 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/open-eid/libdigidocpp/security/advisories/GHSA-q2rc-qw4c-8gv5
- https://www.id.ee/artikkel/uus-id-tarkvara-versioon-parandab-kaks-olulist-turvanrkust/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128978
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128978"}.Affected versions
- Estonian Information System Authority (RIA) libdigidocppFrom 3.13.0 · fixed in 4.5.2
- Estonian Information System Authority (RIA) DigiDoc4From 4.0.0 · fixed in 4.11.2
- Estonian Information System Authority (RIA) DigiDocFrom 3.0.0 · fixed in 3.2.0
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6/10CVSS 6.0
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · open-eid/libdigidocpp · Advisory GHSA-q2rc-qw4c-8gv5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128978 |
| Record | NVD · CVE-2026-128978 |
| Other links 1 | |
| Link | id.ee · artikkel/uus-id-tarkvara-versioon-parandab-kaks-olulist-turvanrkust |
Questions about CVE-2026-128978
Is CVE-2026-128978 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-128978?
libdigidocpp: from 3.13.0 before 4.5.2. DigiDoc4: from 4.0.0 before 4.11.2. DigiDoc: from 3.0.0 before 3.2.0.
Source: cve.now feed data
How do I fix CVE-2026-128978?
Upgrade to a fixed version: libdigidocpp 4.5.2 · DigiDoc4 4.11.2 · DigiDoc 3.2.0.
Source: cve.now feed data
Related
- CVE-2026-70383Arbitrary file overwrite vulnerability in DigiDoc4 client
- CVE-2026-59112Signature validation vulnerability affecting DigiDoc applications
- CVE-2026-75521Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access
- CVE-2026-130756pnpm exe before 10.34.8 Trusts Compromised eMudhra Intermediate Certificates
- CVE-2026-132807A malicious actor with access to the network and under certain conditions could exploit an Improper Certificate Validation vulnerability…
- CVE-2026-117659Dorsett Controls InfoScan Improper Certificate Validation
No corrections so far. Something wrong on this page? Report an error.