CVE-2026-59825: Mastodon LDAP Auth Bypass Vulnerability

CVE-2026-59825 Overview

CVE-2026-59825 is an improper certificate validation vulnerability [CWE-295] in Mastodon, an open-source ActivityPub-based social network server. The flaw resides in app/models/concerns/user/ldap_authenticable.rb, which mutates the shared OpenSSL::SSL::SSLContext::DEFAULT_PARAMS hash when LDAP authentication is configured with LDAP_TLS_NO_VERIFY=true. This mutation disables SSL and TLS certificate verification globally for all outbound requests made by Puma web processes. Sidekiq background jobs remain unaffected. The issue impacts versions prior to 4.4.19 and 4.5.0 through 4.5.11.

Critical Impact
Puma web workers accept invalid or attacker-controlled TLS certificates for outbound HTTPS requests, enabling machine-in-the-middle interception of federated ActivityPub traffic, third-party API calls, and sensitive credential exchanges.

Affected Products

Mastodon versions prior to 4.4.19
Mastodon versions 4.5.0 through 4.5.11
Mastodon deployments with LDAP authentication and LDAP_TLS_NO_VERIFY=true

Discovery Timeline

2026-08-18 - CVE-2026-59825 published to NVD
2026-08-18 - Last updated in NVD database

Technical Details for CVE-2026-59825

Vulnerability Analysis

The vulnerability stems from Ruby's mutable-by-reference semantics for hash objects. Mastodon's LDAP authentication module calls .tap directly on OpenSSL::SSL::SSLContext::DEFAULT_PARAMS. This modifies the shared default hash rather than a copy. When operators set LDAP_TLS_NO_VERIFY=true, the code sets verify_mode to OpenSSL::SSL::VERIFY_NONE on the process-wide default TLS context.

Every subsequent TLS connection initiated by the same Puma worker inherits VERIFY_NONE. This includes federation traffic to remote Fediverse instances, webhooks, object storage clients, and outbound HTTP requests. Sidekiq workers execute in separate processes and are not affected. The bug converts a per-feature configuration option into a global TLS trust bypass across the web tier.

Root Cause

The root cause is in-place mutation of a frozen-by-convention shared constant. OpenSSL::SSL::SSLContext::DEFAULT_PARAMS is used as a template for creating new SSL contexts throughout the Ruby OpenSSL binding. Mutating it propagates the change to every future TLS handshake in the process.

Attack Vector

An attacker with network position between a vulnerable Mastodon instance and any external HTTPS endpoint can present an invalid or self-signed certificate. The Puma worker accepts the certificate without validation. This allows interception and modification of federated content, OAuth tokens, and API responses. Exploitation requires a network-adjacent adversary and a Mastodon deployment configured with LDAP_TLS_NO_VERIFY=true.

ruby

// Patch: app/models/concerns/user/ldap_authenticable.rb
if [:simple_tls, :start_tls].include?(Devise.ldap_method)
  opts[:encryption] = {
    method: Devise.ldap_method,
-   tls_options: OpenSSL::SSL::SSLContext::DEFAULT_PARAMS.tap { |options| options[:verify_mode] = OpenSSL::SSL::VERIFY_NONE if Devise.ldap_tls_no_verify },
+   tls_options: OpenSSL::SSL::SSLContext::DEFAULT_PARAMS.dup.tap { |options| options[:verify_mode] = OpenSSL::SSL::VERIFY_NONE if Devise.ldap_tls_no_verify },
  }
end

Source: Mastodon Commit Fix. The fix calls .dup to duplicate the hash before mutation, isolating the VERIFY_NONE setting to the LDAP encryption options.

Detection Methods for CVE-2026-59825

Indicators of Compromise

Presence of LDAP_TLS_NO_VERIFY=true in Mastodon environment configuration on unpatched versions.
Puma worker processes establishing TLS connections without validating peer certificates.
Unexpected certificate chains observed in outbound federation or webhook traffic captured at network egress.

Detection Strategies

Inventory all Mastodon deployments and confirm running versions against 4.4.19 and 4.5.12 baselines using bundle info mastodon or release metadata.
Audit environment variables and container configuration for LDAP_TLS_NO_VERIFY=true combined with an unpatched Mastodon version.
Inspect outbound TLS sessions from Puma workers for anomalous certificate authorities or self-signed certificates using egress TLS logging.

Monitoring Recommendations

Log and alert on TLS handshake failures and certificate anomalies from Mastodon egress traffic.
Track federation requests to unexpected remote domains that may indicate redirection through a machine-in-the-middle proxy.
Correlate LDAP authentication events with subsequent outbound HTTPS traffic patterns from the same Puma workers.

How to Mitigate CVE-2026-59825

Immediate Actions Required

Upgrade Mastodon to version 4.4.19 or 4.5.12 immediately.
If upgrade is not immediately possible, set LDAP_TLS_NO_VERIFY=false and provide a valid CA bundle for the LDAP server certificate.
Restart all Puma processes after applying configuration changes to clear any mutated default TLS parameters.

Patch Information

Mastodon released fixes in v4.4.19 and v4.5.12. The change is documented in pull request #39571 and detailed in the GHSA-3rhr-8phh-jm86 security advisory. The patch replaces the mutating .tap call with .dup.tap, scoping the VERIFY_NONE setting to the LDAP encryption context.

Workarounds

Disable LDAP_TLS_NO_VERIFY and issue a properly signed certificate to the LDAP server.
Restrict outbound HTTPS traffic from Puma workers to known federation and API endpoints using an egress proxy that enforces certificate pinning.
Isolate Mastodon web tier network paths to prevent adversary-in-the-middle positioning against upstream services.

bash

# Configuration example - disable insecure LDAP TLS bypass
LDAP_TLS_NO_VERIFY=false
LDAP_METHOD=simple_tls
LDAP_HOST=ldap.example.internal
LDAP_PORT=636
# Provide CA bundle for LDAP server certificate validation
SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt