{"answers":{"affected":"1 open source package ship an affected version, including mastodon.","exploited":"There is no known exploitation of CVE-2026-59825 in the wild and no public exploit code.","fix":"Upgrade mastodon to a fixed version for your release line: 4.4.19 or 4.5.12.","what":"CVE-2026-59825 is a high-severity vulnerability in mastodon, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-59825 and fix it if it is affected.\n\nWhat it is: CVE-2026-59825 is a high-severity vulnerability in mastodon, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-59825 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mastodon (Bitnami): affected all versions; fixed in 4.4.19, 4.5.12\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59825/ (Markdown: https://insights.sbomify.com/CVE-2026-59825/index.md)","id":"CVE-2026-59825","markdown":"https://insights.sbomify.com/CVE-2026-59825/index.md","name":"CVE-2026-59825","record":{"aliases":["BIT-mastodon-2026-59825","GHSA-3rhr-8phh-jm86"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Mastodon social network","requires_auth":"none","summary":"Attackers can bypass SSL/TLS certificate verification in Mastodon when LDAP authentication is configured with verification disabled, potentially enabling man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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/ldap_authenticable.rb mutates OpenSSL::SSL::SSLContext::DEFAULT_PARAMS when LDAP authentication uses LDAP_TLS_NO_VERIFY=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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Mastodon: Unwanted deactivation of SSL/TLS certificate verification","id":"CVE-2026-59825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":1,"n_references":7,"next":{"headline":"Metabase: Arbitrary Code Execution via Database Connection Detail Bypass","id":"CVE-2026-59826"},"packages":[{"ecosystem":"Bitnami","fixed":["4.4.19","4.5.12"],"introduced":["0","4.5.0"],"last_affected":[],"package":"mastodon","purl":"pkg:bitnami/mastodon","source":"BIT-mastodon-2026-59825"}],"prev":{"headline":"LiteLLM: Server-side request forgery via the `user_config` request parameter in LiteLLM Proxy","id":"CVE-2026-59823"},"products":["mastodon"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["mastodon"]},"summary":"Attackers can bypass SSL/TLS certificate verification in Mastodon when LDAP authentication is configured with verification disabled, potentially enabling man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2026-59825/"}