Habr•November 15, 2026•🇷🇺Translated from Russian

Four Characters Bypass SSRF Filter: IPv6 Zone and netip.Prefix.Contains in Go

A newly disclosed vulnerability, CVE-2026-126799, impacts Gotenberg versions 8.31.0 to 8.37.0 and was fixed in 8.38.0. The issue lets attackers bypass server-side request forgery (SSRF) filters by appending an IPv6 zone identifier, such as %25 followed by any interface name, to otherwise blocked addresses.

The root cause is not poor coding inside Gotenberg itself but documented behavior in Go’s net/netip package. Typical SSRF checks use netip.Prefix.Contains and methods like IsUnspecified to classify addresses. When an address carries a zone, Prefix.Contains always returns false and IsUnspecified fails to recognize ::%1 as the unspecified address, allowing requests to reach localhost or internal IPv6 ranges.

IPv6 zones and their effect on filtering

IPv6 link-local addresses require a zone identifier to specify the network interface. In URLs the percent sign is percent-encoded, producing addresses such as http://[::%251]:9999/. Go’s url.Parse, netip.ParseAddr, and net.Dial all accept these zoned addresses, yet many security checks do not normalize the zone before evaluation.

Testing showed that fec0:1234::3 is correctly blocked by a fec0::/10 prefix, while fec0:1234::3%1 passes the same check. Similarly, :: is recognized as unspecified, but ::%1 is not. Methods such as IsLoopback and IsPrivate ignore the zone and therefore remain effective, creating an inconsistent security surface.

Reproduction and impact

Researchers built an internal service listening on 127.0.0.1:9999 and [::1]:9999 that returns a secret token. An external preview service using the vulnerable check allowed http://[::%251]:9999/ and http://[::%25zzz]:9999/ to reach the internal endpoint, even when no interface named “zzz” existed. The same bypass worked for fec0::/10, 64:ff9b::/96 (NAT64), and 2002::/16 (6to4) ranges when zones were present.

Recommended fixes

  • Call addr.WithZone("") before any classification to remove the zone component.
  • Reject any URL containing an IPv6 zone identifier before classification, since zones are unnecessary for public addresses.
  • Perform a second check inside net.Dialer.Control using the actual dial address, ensuring redirects and DNS responses are also validated.

A test case was provided that confirms the fixed function blocks all previously leaking addresses while still allowing legitimate external hosts. The same defensive pattern should be applied in any Go project performing URL allow-listing or proxying.

Related articles

Habr•Vulnerabilities & Exploits

Researchers Disclose Full Remote Vehicle Takeover Chain in Major Automaker Connected Platform

Security researchers Shubs and Sam Curry discovered a complete attack chain allowing remote control of any connected vehicle from a major undisclosed automaker across Australia and other large markets. The chain began with decompiled Android APK analysis that revealed hardcoded API endpoints under redacted-telematics.com.au and exposed administrative interfaces. Weak access controls in an OpenIDM instance permitted unauthenticated enumeration of user accounts via email, GUID, and phone number lookups. Path traversal bypasses combined with leaked staging credentials granted administrative access to ForgeRock OpenIDM, enabling password resets and full account takeover. Researchers further bypassed MFA using Resource Owner Password Credentials flows and obtained valid mobile application tokens. With these tokens they could issue arbitrary remote commands including unlock, lock, horn activation, and engine start to any vehicle by VIN or license plate.

Habr•Vulnerabilities & Exploits

Nightmare Eclipse Publishes SignDrop Zero-Day in Windows CLFS Driver

Security researcher Abdelhamid Naseri, known as Nightmare Eclipse, has disclosed a new zero-day vulnerability named SignDrop affecting the Common Log File System (CLFS) driver in Windows. The flaw allows attackers to bypass authentication protections introduced by Microsoft in October 2025 and escalate privileges on affected systems. SignDrop exploits the way CLFS handles .cnpf authentication file creation when a new log file is generated, enabling a privileged process to open the file later and create it with SYSTEM rights. The technique can also be abused against any antivirus or EDR engine to disable self-protection mechanisms by making file creation requests appear to originate from the legitimate security process itself. Nightmare Eclipse confirmed the issue works on Windows 11 26H2, Windows 11 26H2 Experimental, and Windows Server 2025 Experimental, impacting an estimated 80 percent of Windows installations. No workaround exists other than waiting for a Microsoft patch, as disabling CLFS protections would reintroduce memory corruption risks. The researcher previously released multiple other zero-days, including BigDiskBuster and RoguePlanet targeting Microsoft Defender.

Habr•Vulnerabilities & Exploits

Telegram Patches RCE Vulnerabilities in HTML Widgets After Researcher Demonstrates Calculator Exploit

Telegram introduced HTML widgets for bots in early November, allowing JavaScript execution inside messages via the QuickJS engine. Security researcher V12 quickly demonstrated remote code execution by launching the system calculator on Android. Pavel Durov responded that no vulnerability existed because the user had to first start the bot, yet server-side fixes were deployed anyway. Multiple use-after-free and use-after-return bugs were identified in QuickJS and QuickJS-ng, some discovered with AI assistance from Claude Fable 5.1 and Mythos 5.2. Telegram isolated the widget engine into a separate process on Android, added syscall filtering, and limited nested graphical effects to prevent crashes. Desktop clients received the fixes across versions 7.4.2 and 7.4.3, while widgets were temporarily restricted server-side. Users are advised to update to Android 13.2.2 or Desktop 7.4.3 and avoid unknown bots.

AntiMalware•Vulnerabilities & Exploits

Telegram Patches Critical QuickJS Sandbox Escape Vulnerability in Android Update 13.2.2

Telegram has released version 13.2.2 for Android to address a high-severity vulnerability in its HTML widgets for bots. The flaw resided in the QuickJS JavaScript engine within Telegram's QuickJS-ng fork and allowed scripts in ordinary messages to break out of the sandbox and execute native code on the device. The root cause was improper handling of the await using construct inside non-async functions, which triggered a use-after-return condition by freeing local variable references while nested functions still accessed the stack. The vulnerable code entered the QuickJS-ng main branch on May 16 as part of explicit resource management support. Security researcher Andreas Rösler discovered the issue during an AI-assisted audit with Anthropic's Claude model that identified 27 findings total. The patch enforces a syntax error on the invalid construct and was merged on November 10, the same day the Android release became available. Although reported against Android 13.2.1, the bug affected every platform using the affected engine fork.