CVE-2026-59825: Mastodon: Unwanted deactivation of SSL/TLS certificate verification

Published Aug 18, 2026
·
Updated

Mastodon is a free, open-source social network server based on ActivityPub. Prior to 4.4.19 and from 4.5.0 until 4.5.12, Mastodon's app/models/concerns/user/ldapauthenticable.rb mutates OpenSSL::SSL::SSLContext::DEFAULTPARAMS when LDAP authentication uses LDAPTLSNOVERIFY=true, disabling SSL and TLS certificate verification globally for requests made by puma web processes while sidekiq background jobs remain unaffected. This issue is fixed in versions 4.4.19 and 4.5.12.

Affected Software

1 affected component
Mastodon<4.4.19, >=4.5.0<4.5.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Mastodon to a version that resolves this vulnerability.

    Fixed in 4.4.19
  2. Upgrade

    Upgrade Mastodon to a version that resolves this vulnerability.

    Fixed in 4.5.12

Event History

Aug 18, 2026
CVE Published
via MITRE·03:07 PM
Data Sourced
via MITRE·03:07 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments and processes are affected?

Mastodon deployments using LDAP authentication with LDAP_TLS_NO_VERIFY=true are exposed. The global change affects outbound requests made by Puma web processes; Sidekiq background jobs remain unaffected.

2

What would an attacker need to exploit this issue?

An attacker would need to exploit the absence of TLS certificate verification on requests made by affected Puma processes, such as by presenting an untrusted or forged certificate to an outbound connection. The issue is remotely reachable, requires no privileges or user interaction, but has high attack complexity.

3

What mitigation is available if patching cannot happen immediately?

Upgrade to Mastodon 4.4.19 or 4.5.12. If upgrading is not immediately possible, avoid configuring LDAP_TLS_NO_VERIFY=true, because that setting triggers the global disabling of certificate verification in affected versions.

4

How can I determine whether my instance is affected?

Review the LDAP authentication configuration for LDAP_TLS_NO_VERIFY=true and check whether the instance runs a version prior to 4.4.19 or a version from 4.5.0 through 4.5.11. If both conditions apply, Puma web processes may have certificate verification globally disabled.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203