All releases

Version 48c61e6878: Security Update

Sorry for another update email so soon after the last one. AI tools are now helping people find security vulnerabilities much faster than before, in Ruby and in the libraries we build on, so when a fix for a critical vulnerability comes out, we release an update with it as soon as we can. This is one of those releases: it updates Ruby to 4.0.10, which fixes seven vulnerabilities in Ruby’s regular expression engine and in changing the case of strings.

Our regular releases still come about once a quarter. Security releases like this one are marked as security updates, and you can choose which releases you get emails about: every release, only security updates, or none. Use the email preferences link at the bottom of this email, or ask for a link at https://app.docspring.com/email/preferences.

New features and improvements

  • Signature requests for every template type: HTML templates, Word templates and page designs can now go to signers, not only PDF templates. The document is made before anyone signs, signers fill in its form fields ({% form_field %} tags or page design form fields), and their values go on that same document (how it works). A template can also name its signers and say who fills in each field (Signer roles).
  • sync_fields in API v2: saving an HTML template adds a field for each new value its code reads, and its submissions check their data against those fields. Send sync_fields: false to manage the fields yourself. API v1 doesn’t add fields to HTML templates.
  • Signature request emails put the template’s name in quotation marks (Acme sent you “Rental Agreement” to sign), and call a template without a name “a document” instead of showing its ID. The notices that tell the sender someone signed, declined or didn’t get their email have a View submission button.

Bug fixes

  • Archiving or restoring a user or a signature request through the Admin API no longer returns a 500 error after the change has been made. A JSON request now gets a 204, or a 422 with the reason when the record can’t be archived or restored (an account’s owner, for example). In the admin pages, Archive no longer says it worked when it didn’t.
  • With DOCSPRING_ACCOUNT_DELETION_NOTICES_ENABLED on and DOCSPRING_ACCOUNT_PURGES_ENABLED off, the nightly task emailed users that their account’s data would be permanently deleted, though nothing would delete it. It now sends no notice until both are on, and its report says how many accounts are waiting.
  • Dates and times on PDFs print in the account’s time zone: @@date, @@datetime, the signature request dates and date values sent with a UTC offset. They used to print in the server’s (DOCSPRING_TIMEZONE) whatever the account’s was. Signing pages and visual forms show the same date as the PDF, not the date on the signer’s own clock. Templates that existed before you installed the November 15, 2026 release, and accounts without a time zone, keep the server’s.
  • The built-in format for date fields with Include time no longer prints seconds: %m/%d/%Y %H:%M, where it was %m/%d/%Y %H:%M:%S. Only accounts created after this upgrade get it. The upgrade writes the old format into the defaults of every existing account and template that had none, so their PDFs don’t change. To move an existing account or template to the new format, choose it in its Field defaults.
  • @@datetime and the signature request dates (@@signature_requests/0/completed_at, viewed_at) print the date and the time on PDFs, as the docs and the signing page said: 11/16/2026 09:25. They used to print only the date unless the field had its own format. A field with its own format doesn’t change.
  • On installs that keep uploads in Google Cloud Storage (DOCSPRING_GCS_UPLOADS_BUCKET), the company logo and page images now load: links to the bucket were http://, and the app’s Content-Security-Policy didn’t allow the bucket. Download links also keep the expiry you set (DOCSPRING_PDF_URL_EXPIRATION_TIME) instead of one hour.
  • S3 installs without DOCSPRING_AWS_UPLOADS_S3_REGION now allow the bucket in the Content-Security-Policy, using the region the AWS SDK picks, so page images and previews load.

Security and updates

  • Ruby 4.0.10, which fixes seven vulnerabilities in Ruby’s regular expression engine and in changing the case of strings, some of which can lead to remote code execution (Ruby’s advisory).

Upgrade to this version

Pull its image from AWS ECR or Docker Hub (multi-arch manifests for amd64 and arm64):

691950705664.dkr.ecr.us-east-1.amazonaws.com/docspring/enterprise:48c61e6878
docspringcom/docspring-enterprise:48c61e6878

If its database version is newer than the one in your admin pages' footer, run rake db:migrate when you upgrade. Upgrading from an older version? Read the notes of every release in between.

Product news by email

New features and changes, once a month.