Dart and Flutter SDKs Patch Critical TLS Flaw Tied to Compromised eMudhra Certificates
Dart and Flutter teams have issued updates that close a critical TLS vulnerability involving compromised intermediate certificates from the eMudhra certificate authority. Developers maintaining production applications on Android, Windows, or Linux are advised to perform an unplanned release cycle.
The affected stable versions are Dart 3.13.7 and Flutter 3.47.8. Beta channels received Dart 3.14.0-315.3.beta and Flutter 3.50.0-0.2.pre. Updating the SDK on developer machines is not sufficient; applications and binaries must be rebuilt and delivered to end users or deployed on servers.
What Happened with eMudhra
In October 2026 researchers disclosed that private keys for eight eMudhra intermediate certificates had been recovered due to insufficient entropy during key generation. An attacker in possession of such a key can issue fraudulent certificates for arbitrary domains, allowing interception of HTTPS traffic when the client still trusts the compromised chain.
The attack requires a position on the network path between the application and its server. The adversary presents a forged certificate signed by the compromised intermediate, and the vulnerable client accepts it, establishing a connection to a malicious endpoint. Tokens, credentials, and request/response data become exposed.
Why System Updates Do Not Protect Flutter Apps
dart:io validates certificate chains using its bundled BoringSSL library and does not consult operating-system revocation lists. Tests on Android 15 devices showed that the system HttpsURLConnection rejected connections to blocklisted test endpoints while Flutter 3.47.0 accepted them. The same behavior was reproduced on Windows with updated system trust stores.
Changes Introduced in the SDK
The patched BoringSSL now contains hardcoded blocks for the eight compromised eMudhra intermediates. On Android 14 and newer, dart:io additionally loads root certificates from the updatable Conscrypt APEX module, allowing future root-store changes delivered through Google Play to take effect.
Recommended Actions for Developers
- Run flutter upgrade and verify the resulting Dart and Flutter versions.
- Update any pinned SDK versions in CI pipelines.
- Rebuild and redistribute Android APKs or App Bundles, Windows, and Linux binaries.
- On Linux containers, ensure both the build-time Dart version and the runtime ca-certificates package are current.
Simply running pub upgrade does not address the issue, as the fix resides inside the SDK itself.
Related articles
Vulnerability Management Evolution: From Manual Scans to Continuous Threat Exposure Management
This final installment of the Vulnerability Management for Beginners series examines how the discipline has transformed over recent years into an essential component of organizational risk management. The article highlights the dramatic increase in disclosed vulnerabilities, now approaching 48,000 per year, and stresses that fewer than one percent pose real-world risk. It details the shift toward automated asset inventory integrated with SIEM, EDR, and CMDB systems, alongside multi-factor prioritization combining CVSS, EPSS, KEV lists, and FSTEC methodologies. New practices such as EASM, automated penetration testing, BAS, and CTEM are presented as extensions of a mature foundational process rather than replacements. The piece also covers regulatory tightening in Russia through FSTEC Order No. 117, mandatory remediation timelines, and the impact of AI on both defense and attack surfaces. It concludes with a practical Monday-morning action list focused on asset counting, threat feed integration, SLA definition, and cross-team coordination between IT and security.
Fortinet Discloses Eight FortiOS Vulnerabilities Including Three Critical Flaws
Fortinet has published security advisories detailing eight vulnerabilities affecting its FortiOS operating system used in UTM appliances. Three of the issues received the highest severity rating of Critical. CVE-2026-126259 allows unauthenticated command execution with super-admin privileges in FGSP combined with configuration synchronization or auto-scale setups via crafted HA packets. CVE-2026-126254 stems from integer truncation in the BGP daemon and can propagate malicious attributes from configured iBGP peers. CVE-2026-126253 enables authentication bypass in the OSPF daemon, permitting unauthenticated LSA injection. The remaining five vulnerabilities were assigned lower severity ratings. Administrators are urged to apply the available patches promptly.
Microsoft Patches Over 1,000 Vulnerabilities in November 2026 Patch Tuesday Release
Microsoft has issued its November 2026 monthly security updates, addressing a total of 1,093 vulnerabilities across Windows, Office, Azure, SQL Server, SharePoint Server, Exchange Server, and Developer Tools. The update also covers a vulnerability in the third-party Tencent RapidJSON library identified as CVE-2026-124586. Among the fixes, 63 vulnerabilities received the highest severity rating of Critical, while 1,029 were rated Important. Privilege escalation issues accounted for the largest share with 535 cases, followed by 296 remote code execution flaws. Several vulnerabilities have already been confirmed as exploited in the wild. The release follows the standard Patch Tuesday schedule on the second Tuesday of the month.
What Every Programmer Should Know About Stack Buffer Overflows on Windows
The article provides a practical, step-by-step guide to understanding stack buffer overflow attacks under Windows, using the unsafe scanf function as the primary example. It explains how unlimited input can overwrite adjacent memory structures, including return addresses stored on the stack. Detailed coverage of process memory layout, assembly instructions, the RIP register, stack frames, and calling conventions shows exactly how control flow can be hijacked. The tutorial demonstrates live debugging with WinDbg, showing how input can corrupt the return address and trigger crashes. It also covers modern compiler protections such as MSVC stack canaries that detect overwrites before they allow exploitation. The piece emphasizes why developers must validate buffer sizes and how these classic vulnerabilities remain relevant despite defensive mechanisms.