# CVE-2026-70383: Arbitrary file overwrite vulnerability in DigiDoc4 client

> An attacker can overwrite arbitrary files on the system via path traversal in the DigiDoc4 client, requiring an upgrade to mitigate.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-48r4-r7pv-pj69

## What is CVE-2026-70383?

CVE-2026-70383 is a high-severity path traversal vulnerability in Estonian Information System Authority (RIA) DigiDoc4, published on 20 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Estonian Information System Authority (RIA) DigiDoc4 client.

This issue affects DigiDoc4: from 4.0.0 before 4.11.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-70383?


## How do I fix CVE-2026-70383?

No fix has been published for CVE-2026-70383 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70383 being exploited?

There is no known exploitation of CVE-2026-70383 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70383 and fix it if it is affected.

What it is: CVE-2026-70383 is a high-severity path traversal vulnerability in Estonian Information System Authority (RIA) DigiDoc4, published on 20 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-70383 in the wild and no public exploit code.

Affected product: Estonian Information System Authority (RIA) DigiDoc4. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-70383/ (Markdown: https://insights.sbomify.com/CVE-2026-70383/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70383
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70383
- OSV: https://osv.dev/vulnerability/CVE-2026-70383

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-70383/
Summaries are generated and may contain mistakes; the official description above is the record.
