[WITHDRAWN] HedgeDoc 1.12.2
Released onThis is the latest release
Click here to read the release notes
[!CAUTION] DO NOT UPDATE TO THIS RELEASE, IT MIGHT BREAK YOUR INSTANCE
Bugfixes
- Fixed the profile provider migration failing on PostgreSQL
[!CAUTION] DO NOT UPDATE TO THIS RELEASE, IT MIGHT BREAK YOUR INSTANCE
[!CAUTION] Due to some bugs with usage on PostgreSQL, we had to pull back this release.
CMD_OAUTH2_USER_PROFILE_PHOTO_ATTR to let OAuth2/OIDC providers supply a profile photo URL, instead of always falling back to a generated avatar<br> HTML tag$$ math blocks⚠️ HedgeDoc 1.12.0 and onwards will require Node 20.17 or later in order to run. Since Node 18 security support was stopped over one year ago, we don’t maintain backwards-compatability for that anymore.
Some syntax highlighting languages have been removed and/or changed. You can find more information in the highlight.js docs.
externalLinkWarning in config.json or CMD_EXTERNAL_LINK_WARNING) to disable the external link warning page entirelyexternalLinkWhitelist in config.json or CMD_EXTERNAL_LINK_WHITELIST) to skip warning page for certain domainsimgur, since that does not support these)allowOrigin (environment variable CMD_ALLOW_ORIGIN) config option.This release contains four security fixes:
Thanks to Chandler Johnson, taylorodell and alanturing881 for reporting!
rateLimitUsingCloudflare in the config.json or CMD_RATE_LIMIT_USING_CLOUDFLARE as environment variable to true.bin/setuphex2rgb to prevent crashes from non-hex color valuesThis release contains two medium severity security fixes:
Thanks to @HUSEYNKHANLI and @drkim-dev for reporting!
This release is just a fix for the docker container. It does not contain any changes to HedgeDoc itself.
This release contains two low severity security fixes:
state parameter is not used and checked.enableUploads (CMD_ENABLE_UPLOADS) config option to restrict uploads to registered users, all users or
none to completely disable uploads.credentialless and sandbox attributes[time=...], [name=...] and [color=...] shortcodes in listsstate parameter for OAuth2 flows and PKCE where applicableThis release fixes a security issue of a possible XSS exploit which can be planted via a malicous SVG file upload.
See CVE-2025-32391 for more details
CMD_SAML_WANT_ASSERTIONS_SIGNED and CMD_SAML_WANT_AUTHN_RESPONSE_SIGNED for SAML auth, since
some instances didn’t comply with the new defaults of @node-saml/passport-samlPLEASE CHECK THIS IF YOU USE SAML AUTHENTICATION:
This release had to set default values for the username and email address attribute mapping for SAML authentication for
security reasons.
If you use SAML authentication, please make sure to update your SAML configuration accordingly.
See: https://docs.hedgedoc.org/configuration/#saml-login CMD_SAML_ATTRIBUTE_USERNAME or CMD_SAML_ATTRIBUTE_EMAIL
This release fixes a security issue where brute-forcing local email/passwords is possible because of missing rate-limits. We recommend upgrading as soon as possible, if you use local logins.
See also https://github.com/hedgedoc/hedgedoc/security/advisories/GHSA-6w39-x2c6-6mpf
This release changes the default configuration of the HSTS preload attribute to false for compliance with the
HSTS preload list requirements. This shouldn’t impact any instance. However, if you intend to use HSTS preloading
you should enable the config setting hsts.preload to true or set environment variable CMD_HSTS_PRELOAD=true.
This release deprecates support for Node 18. As the LTS support for 18 runs out in April 2025, the next release will only work with Node 20 and upwards. Consider this your early warning to upgrade any running instances to at least Node 20.
This release fixes a security issue when using MySQL/MariaDB. We recommend upgrading as soon as possible, when you use this database.
Please note: This release dropped support for Node 16, which is end-of-life since September 2023. You now need at least Node 18 to run HedgeDoc. We recommend to use the latest LTS release of Node.js.
⚠️ Node 22.7.0 has a regression that breaks UTF-8 encoding. Do not use that version to run HedgeDoc. ⚠️
disableNoteCreation config option for read-only instancesmeta-marked package is now published to NPM, fixing some installation issuesHedgeDoc has a new slogan! See our announcement for the details.
This release fixes a security issue. We recommend upgrading as soon as possible.
Please note: This release dropped support for Node 14, which is end-of-life since May 2023. You now need at least Node 16 to run HedgeDoc. We recommend to use the latest LTS release of Node.js.
This release switches to Yarn 3 for dependency management, as Yarn 1 has bugs preventing us from upgrading some dependencies.
If you install HedgeDoc manually, run bin/setup again for instructions. Other installation methods should not require
special actions.
documentMaxLength via CMD_DOCUMENT_MAX_LENGTH environment variable (contributed by @jmallach)/status and /metrics endpointsbin/setup script🚨 This release has a bug that leads to data-loss when using SQLite. We advise users of SQLite databases to skip this release and use 1.9.6. 🚨
breaks option not being respected in the publish-viewPlease note: This release dropped support for Node 12, which is end-of-life since April 2022. You now need at least Node 14.13.1 or Node 16 to run HedgeDoc. We don’t support more recent versions of Node.
This release fixes a security issue. We recommend upgrading as soon as possible.
⚠️ Warning: If you deploy HedgeDoc and MariaDB with docker-compose using a checkout of our container repo, you will need to manually convert the character set of the database to utf8mb4 when updating. See the corresponding PR for more information.
git binary is not foundbin/manage_users not accepting numeric passwords (thanks to @carr0t2 for reporting)/metrics or /statusThis release increases the minimum required Node versions to 12.20.0, 14.13.1 and 16.
In general, only the latest releases of Node 12, 14 and 16 are officially supported by us, older minor versions can be dropped at any time.
We recommend you run HedgeDoc with the latest release of Node 16.
csp.allowFraming config option, which controls whether embedding a HedgeDoc instance in other webpages is allowed.
We strongly recommend disabling this option to reduce the risk of XSS attackscsp.allowPDFEmbed config option, which controls whether embedding PDFs inside HedgeDoc notes is allowed. We recommend disabling this option if you don’t use the feature, to reduce the attack surface of XSS attacksfilesystem upload methodsecure flag, if HedgeDoc is loaded via HTTPS/metrics and /statusThis release fixes two security issues. We recommend upgrading as soon as possible.
yarn install in production mode (as performed by bin/setup) by marking frontend-only dependencies as dev-dependencies.
This also reduces the size of the docker containeresbuild instead of terser to minify JavaScriptuseSSL or csp.upgradeInsecureRequests is enabled (thanks to @mdegat01 for reporting)protocolUseSSL when useSSL is also enabled