VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

document-merge-service: vulnerability history, versions and safety

document-merge-service is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 32 releases, from Jun 2024 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 10 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all document-merge-service vulnerabilities

Vulert verdict on document-merge-service 9.0.0 i

Updated on 23 Oct 2026

Action needed: 9.0.0 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 57/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 9.0.0 — affected i
  • Vulnerabilities on record 4 over 2 years · 3 in the last year i
  • Latest disclosure 10 Sep 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Stars 16 i
  • Last release 9 months ago i
  • Licence GPL-3.0-or-later i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for document-merge-service, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
9.0.0 19 Jan 2026 H1 U1 GPL-3.0-or-later Yes Details →
8.1.0 22 Oct 2025 H1 U1 GPL-3.0-or-later Yes Details →
8.0.3 29 Sep 2025 H1 U1 GPL-3.0-or-later Yes Details →
8.0.2 08 Aug 2025 H1 U1 GPL-3.0-or-later Yes Details →
8.0.0 16 May 2025 H1 U1 GPL-3.0-or-later Yes Details →
7.1.0 21 Aug 2024 H1 U1 GPL-3.0-or-later Yes Details →
7.0.2 09 Aug 2024 H1 U1 GPL-3.0-or-later Yes Details →
7.0.1 19 Jul 2024 H1 U1 GPL-3.0-or-later Yes Details →
7.0.0 17 Jul 2024 H1 U1 GPL-3.0-or-later Yes Details →
6.6.1 01 Jul 2024 H1 U1 GPL-3.0-or-later Yes Details →
6.6.0 18 Jun 2024 H1 U1 GPL-3.0-or-later Yes Details →
6.4.6 12 Jun 2024 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.5.2 12 Jun 2024 H1 U1 GPL-3.0-or-later Yes Details →
6.5.1 03 Jun 2024 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.5.0 30 May 2024 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.4.5 25 Apr 2024 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.4.4 24 Jan 2024 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.4.3 23 Oct 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.4.2 25 Sep 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.4.1 09 Aug 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.4.0 03 Aug 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.3.1 31 Jul 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.3.0 25 Jul 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.2.2 24 Jul 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.2.1 19 Jul 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.2.0 11 Jul 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.1.2 10 May 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.1.1 04 May 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.1.0 27 Jan 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
6.0.0 12 Jan 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
5.2.1 12 Jan 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →
5.2.0 12 Jan 2023 C1 H1 U2 GPL-3.0-or-later Yes Details →

All 32 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for document-merge-service

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-37301: document-merge-service vulnerable to Remote Code Execution via Server-Side Template Injection 9.1 critical 6.5.2 11 Jun 2024
CVE-2024-37301: document-merge-service Remote Code Execution via Server-Side Template Injection 7.2 high 6.5.2 07 Jul 2026
CVE-2026-53964: Document Merge Service Remote Code Execution via SSTI in XLSX Templates 7.2 high 9.1.0 19 Aug 2026
CVE-2026-53964: Document Merge Service Remote Code Execution via SSTI in XLSX Templates 7.2 high 9.1.0 10 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About document-merge-service

Is document-merge-service safe to use?

Vulert records 4 vulnerabilities for document-merge-service in PyPI: 1 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is document-merge-service's Vulert package health score?

Vulert scores document-merge-service 57/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of document-merge-service affected?

Yes. 9.0.0, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of document-merge-service should I use?

9.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does document-merge-service have?

4 vulnerabilities are recorded for document-merge-service in the PyPI ecosystem: 1 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new document-merge-service vulnerabilities disclosed?

3 vulnerabilities were recorded for document-merge-service in the last 12 months, and the oldest entry in this database dates to 11 Jun 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of document-merge-service are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor document-merge-service for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the document-merge-service version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.