{"answers":{"affected":"1 open source package ship an affected version, including mastodon.","exploited":"There is no known exploitation of CVE-2026-72916 in the wild and no public exploit code.","fix":"Upgrade mastodon to a fixed version for your release line: 4.4.21, 4.5.14 or 4.6.4.","what":"CVE-2026-72916 is a medium-severity server-side request forgery vulnerability in mastodon, published on 10 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-72916 and fix it if it is affected.\n\nWhat it is: CVE-2026-72916 is a medium-severity server-side request forgery vulnerability in mastodon, published on 10 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-72916 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mastodon (Bitnami): affected all versions; fixed in 4.4.21, 4.5.14, 4.6.4\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-72916/ (Markdown: https://insights.sbomify.com/CVE-2026-72916/index.md)","id":"CVE-2026-72916","markdown":"https://insights.sbomify.com/CVE-2026-72916/index.md","name":"CVE-2026-72916","record":{"aliases":["BIT-mastodon-2026-72916","GHSA-vwhj-3g83-v276"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Mastodon social network","requires_auth":"none","summary":"Attackers can bypass SSRF protections using IPv4-compatible IPv6 addresses to access private resources on loopback interfaces.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-1286","name":"Improper Validation of Syntactic Correctness of Input"}],"description":"Mastodon is a free, open-source social network server based on ActivityPub. Prior to 4.4.21, 4.5.14, 4.6.4, and 4.7.0-beta.1, PrivateAddressCheck.private_address? in app/lib/private_address_check.rb normalized IPv4-mapped IPv6 addresses but did not recognize IPv4-compatible IPv6 addresses with IPAddr#ipv4_compat?. An attacker could supply an address in the omitted range to bypass the ALLOWED_PRIVATE_ADDRESSES protection and make Mastodon send HTTP requests to loopback interfaces, potentially accessing private resources and services. Exploitation requires a system that supports the obsolete IPv4-compatible IPv6 mechanism. This issue is fixed in versions 4.4.21, 4.5.14, 4.6.4, and 4.7.0-beta.1.","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: SSRF Protection Bypass via IPv4-compatible IPv6 Addresses","id":"CVE-2026-72916","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":1,"n_references":9,"next":{"headline":"AnythingLLM: Password recovery accepts one recovery code twice after whitespace normalization","id":"CVE-2026-72917"},"packages":[{"ecosystem":"Bitnami","fixed":["4.4.21","4.5.14","4.6.4"],"introduced":["0","4.5.0","4.6.0"],"last_affected":[],"package":"mastodon","purl":"pkg:bitnami/mastodon","source":"BIT-mastodon-2026-72916"}],"prev":{"headline":"Mastodon: Personally-identifying information disclosure due to incorrect access control validation","id":"CVE-2026-72915"},"products":["mastodon"],"published":"2026-08-10","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":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["mastodon"]},"summary":"Attackers can bypass SSRF protections using IPv4-compatible IPv6 addresses to access private resources on loopback interfaces.","url":"https://insights.sbomify.com/CVE-2026-72916/"}