CVE-2026-42596 Details.
Gotenberg < 8.31.0 - Server-Side Request Forgery
Atlas does not check this one. Needs requests that change data.
To test for this one, the check would have to send requests that could change data on the site. Atlas only ever reads public pages, so it does not run this check.
About CVE-2026-42596. What It Means.
Gotenberg before 8.31.0 is vulnerable to server-side request forgery (SSRF) due to insufficient validation of URLs in the downloadFrom API. An unauthenticated attacker can exploit the flaw by providing specially crafted IPv4-mapped IPv6 addresses (such as http://[::ffff:127.0.0.1]) that bypass the deny-list and allow access to internal resources. Fixed versions properly recognize these addresses and prevent such requests.
Affected Product. What Is Hit.
The record for CVE-2026-42596 does not name a vendor or product yet.
FAQ
Common Questions.
Gotenberg < 8.31.0 - Server-Side Request Forgery. Gotenberg before 8.31.0 is vulnerable to server-side request forgery (SSRF) due to insufficient validation of URLs in the downloadFrom API. An unauthenticated attacker can exploit the flaw by providing specially crafted IPv4-mapped IPv6 addresses (such as http://[::ffff:127.0.0.1]) that bypass the deny-list and allow access to internal resources. Fixed versions properly recognize these addresses and prevent such requests.
No. To test for this one, the check would have to send requests that could change data on the site. Atlas only ever reads public pages, so it does not run this check. The facts about CVE-2026-42596 are on this page, and you can request a demo to see how Brandefense watches your whole external attack surface.
CVE-2026-42596 is not on the CISA Known Exploited Vulnerabilities list at the time of writing, but it is still worth fixing.
Update the affected software to the latest version from the vendor, or follow the vendor's advice to switch off the affected feature. Vendor links are listed on this page when they are known.
This page lists the public facts about CVE-2026-42596. Atlas does not run a check for it, so nothing here says whether a particular site is affected.