# CVE-2026-34586: PdfDing: Shared PDF Expiration, Max Views, and Deletion Bypass via Serve/Download Endpoints

> Attackers can access expired, view-limited, or deleted shared PDFs because the application fails to validate these states during download requests.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-vfqx-2464-38wf

## What is CVE-2026-34586?

CVE-2026-34586 is a medium-severity missing authorization vulnerability in mrmn2 PdfDing, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PdfDing is a selfhosted PDF manager, viewer and editor offering a seamless user experience on multiple devices. Prior to version 1.7.1, check_shared_access_allowed() validates only session existence — it does not check SharedPdf.inactive (expiration / max views) or SharedPdf.deleted. The Serve and Download endpoints rely solely on this function, allowing previously-authorized users to access shared PDF content after expiration, view limit, or soft-deletion. This issue has been patched in version 1.7.1.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Pdfding Pdfding.

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

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

## Is CVE-2026-34586 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34586 exists.

## Other vulnerabilities in mrmn2 PdfDing

- [CVE-2026-34376](https://insights.sbomify.com/CVE-2026-34376/): PdfDing: Password-protected share bypass via direct serve endpoint (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34586 is a medium-severity missing authorization vulnerability in mrmn2 PdfDing, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34586 exists.

Affected product: mrmn2 PdfDing. 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-34586/ (Markdown: https://insights.sbomify.com/CVE-2026-34586/index.md)
```

## Sources

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

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