Qoder 0.4.11 ships Electron 43.1.1, which still trusts the revoked eMudhra intermediate CAs

Qoder 0.4.11 (latest, Oct 23) is built on Electron 43.1.1 / Chromium 150.0.7871.114. The eMudhra intermediate CA compromise disclosed on Oct 20 is fixed in Electron 42.11.16, 43.8.1 and 44.9.1; 43.1.1 predates all of them.

Steps to reproduce (macOS, Qoder 0.4.11)

  1. Open in the side browser and click “Run check”.
  2. The page reports: “Your browser trusted 7 of 14 compromised certificate chains” — all seven emSign-rooted chains, including the non-CT one (dv-g3b-noct-emudhra.we-have-a-problem.com).
  3. Opening https://dv-g3b-aaa-emudhra.we-have-a-problem.com/ directly fails with ERR_CERT_AUTHORITY_INVALID, so the remaining :white_check_mark: rows are genuine certificate rejections, not network failures.

Why it matters: the private keys in this incident can be recovered from the public certificates, so anyone with an on-path position can forge a certificate for any hostname and the embedded browser will accept it silently. Accepting the non-CT chain means such forgeries never appear in Certificate Transparency logs. Electron does not receive Chromium’s component/CRLSet updates, so this can only be fixed by shipping a new build.

Request: please rebuild on Electron ≥ 43.8.1 (or move to 44.9.1+). VS Code 1.143.1, Obsidian 1.14.5 and Claude Code 2.1.303 have already shipped their fixes.

Note: the bundled Node runtime in the same app rejects these chains with CERT_REVOKED; the problem is specific to the embedded browser.

UA: QoderApp/0.4.11 Chrome/150.0.7871.114 Electron/43.1.1