Edition of Wednesday 11 November 2026

Electron, We Have a Problem

Comments on “Electron, We Have a Problem”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Security researcher Pascal Schärli reports that many Electron desktop apps still trust two eMudhra intermediate CAs said to use easily recovered keys, and that many also auto-update without signature checks. An attacker on the network could then push malware through the updater. Electron fixed this by hardcoding distrust, so each app needs a new release. Schärli's LLM-compiled snapshot of about 35 apps, including Internxt, Filen and Notesnook, is unverified in places. If you ship Electron, verify update signatures and ship the patched Electron build.

Read the original at schaerli.org. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 2 of 143 with a score of 0.76. The panel rated it highest on practical relevance (0.90) and reader interest (0.85), lowest on audience breadth (0.67).

AI judgeJudge 2claude-haiku-5-5
Detailed, well-evidenced security research on Electron auto-update signature gaps and eMudhra CA trust, with a per-app scan and actionable mitigation advice; strongly relevant to builders shipping desktop apps.
AI judgeJudge 3gpt-5.6-luna
A timely security investigation combines certificate-compromise analysis with a broad Electron-app scan and actionable remediation. Evidence is useful but partly LLM-compiled, self-reported, and not fully reproducible, limiting substantiation and significance.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.76total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.70
  • Reader interest0.85
  • Audience breadth0.67
  • Practical relevance0.90
  • Substantiated0.78
  • Technical depth0.80
  • New information0.84
  • Counts against: Promotional0.04
  • Counts against: Overclaim0.22

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.680.700.720.700.04+0.24+0.168
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.810.850.900.850.09+0.26+0.222
Audience breadthHow many people who build technology does it concern?0.620.720.660.670.10+0.13+0.087
Practical relevanceHow useful is it to someone who builds software or tech products?0.950.900.840.900.11+0.22+0.197
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.800.850.700.780.15+0.05+0.039
Technical depthHow technically substantive is it?0.850.850.700.800.15+0.05+0.040
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.780.800.950.840.17+0.05+0.042
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.060.030.020.040.04−0.19−0.007
OverclaimDo the headline or conclusions claim more than the body supports?0.330.200.120.220.21−0.11−0.024
Sum of contributions+0.765
Claim-check penalty0.000
Total, as published0.765

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #2 on Rubric, 11 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-11/2/"><img src="https://rubric.hrih.si/badge/2026-11-11/2.svg" alt="Ranked #2 on Rubric, 11 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: 2 matches source · 2 no source given · 4 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkDate

    In October 2026, emudhra.we-have-a-problem.com showed that a couple of eMudhra intermediate CAs, trusted to sign certificates for any website, used tiny private keys that are trivial to recover.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Then in October 2026, emudhra.we-have-a-problem.com showed that a couple eMudhra intermediate CAs, trusted to sign certificates for any website, used tiny private keys that are trivial to recover”

    The source says

    No passage could be compared.

    Source cited by the article: emudhra.we-have-a-problem.com

  2. No source givenCausal conclusion

    Browsers fixed the eMudhra problem quickly by shipping revocation lists within hours, without requiring a browser update.

    The article gives no link or citation for it.

    The article says

    “Browsers fixed it quickly, shipping revocation lists within hours, it didn't even require a browser update”

    The source says

    No source to compare with.

  3. Couldn’t checkCausal conclusion

    Electron does not have Chromium's component updater, which delivers revocation lists, so there was no easy remediation.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “But Electron does not have Chromium's component updater, which is what delivers those lists, so there was no easy remediation”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/electron/electron/pull/7252

  4. Matches sourceCausal conclusion

    Electron fixed the eMudhra issue by hardcoding distrust of the specific eMudhra certificates, which requires users to install a full new version of any Electron application.

    The cited source says the same thing.

    The article says

    “Electron fixed it by hardcoding distrust of these specific eMudhra certs (GHSA), which requires users to install a full new version of any electron application before the patch lands”

    The source says

    “There are no app side workarounds, you must update to a patched version of Electron”

    Source cited by the article: github.com/electron/electron/security/advisories/GHSA-jr5w-w6x2-84p9

  5. Couldn’t checkGeneralization

    Mainstream Electron update libraries only have partial or no signature support, which leads some vendors to skip it and rely on TLS alone.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Electron's update ecosystem is messy and the mainstream libraries only have partial or no signature support, which leads some vendors to skip it and rely on TLS alone to protect…”

    The source says

    No passage could be compared.

    Source cited by the article: blog.doyensec.com/2026/02/16/electron-safe-updater.html

  6. No source givenGeneralization

    Many Electron apps auto-update without verifying signatures and still trust the compromised eMudhra certificates, letting an attacker on the network install malware.

    The article gives no link or citation for it.

    The article says

    “Many Electron apps auto-update without verifying signatures. Many also still trust the compromised eMudhra certificates. Together, that lets an attacker on your network install malware on your machine”

    The source says

    No source to compare with.

  7. Matches sourceDate

    Microsoft disallowed the compromised eMudhra keys in the Windows certificate store in October.

    The cited source says the same thing.

    The article says

    “Microsoft disallowed the compromised keys in the Windows store in October”

    The source says

    “On October 20, Microsoft published an update to the Windows Disallowed Certificate Trust List to block the affected certificate authorities”

    Source cited by the article: microsoft.com/en-us/msrc/blog/2026/10/microsoft-response-to-compromised-emudhra-certificate-authority-keys

  8. Couldn’t checkCausal conclusion

    The Proton Mail desktop app fetches its entire UI from mail.proton.me, so the server operator could serve a backdoored UI to selected users on any launch.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “how the Proton Mail desktop app fetches its entire UI from mail.proton.me”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/ProtonMail/WebClients/blob/proton-inbox-desktop@1.16.1/applications/inbox-desktop/src/utils/view/viewManagement.ts

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 11 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Electron, We Have a Problem”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.