
🔓 One crafted SVG can make Apache Batik skip same-origin checks and call your internal network. 📌 What happened: CVE-2026-49236 is an SSRF (CWE-918) in Apache XML Graphics Batik 1.19. A malicious xml:base URL in an SVG makes Batik request attacker-chosen URLs without authentication. 🔑 Key facts: ▪️ Vendor severity: Moderate; NVD CVSS score pending ▪️ Affected: Batik 1.19 | Fixed: Batik 1.20 (BATIK-1394) ▪️ Attacker can probe internal services reachable from the host ▪️ No known exploitation, no public PoC, not in CISA KEV ⚠️ Why it matters: Any app that renders untrusted SVG through Batik 1.19 can be used to reach internal services without authentication. 🛡️ Do this now: 1⃣ Upgrade to Batik 1.20 (no vendor workaround) 2⃣ Test the upgrade in staging before production 3⃣ Alert on Batik HTTP requests with unusual xml:base values 4⃣ Watch threat feeds for new Batik SSRF exploits 🔗 Full analysis: https://badgersignal.com/articles/cve-2026-49236-apache-xml-graphics-batik-ssrf---bypasses-same-origin-checks 📊 Infographic attached for the breakdown at a glance. 💬 Do you know which of your Java services render user-supplied SVG with Batik? #CyberSecurity #ThreatIntelligence #InfoSec #BadgerSignal #ApacheBatik #SSRF #AppSec
Post summary
The post discloses CVE-2026-49236, an SSRF (CWE-918) in Apache Batik 1.19, and its primary takeaway is remediation: upgrade to fixed version Batik 1.20. It explicitly notes no known exploitation, no public PoC, and not in CISA KEV.

