#55126: fix: apply the certificate SPKI blocklist to Node and add entries
Merged
Created: Oct 19, 2026, 7:15:13 PM
Merged: Oct 19, 2026, 7:48:07 PM
5 comments
Target: main
Description of Change
- Node: apply the SPKI blocklist to every
SecureContextso a chain containing a listed key reportsCERT_REVOKED, matching what the Chromium stack already does. - Chromium: add entries to the compiled-in SPKI blocklist that Chrome ships via CRLSet, which Electron does not consume.
- Spec covering the Node path via testing-binding hooks.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
-
npm testpasses - tests are changed or added
Release Notes
Notes: none
Backports
42-x-y
MergedPR Number
#55128Merged At
Oct 19, 2026, 7:47:59 PM
Released In
v42.11.16Release Date
Oct 19, 2026, 7:49:20 PM
43-x-y
MergedPR Number
#55130Merged At
Oct 19, 2026, 7:47:50 PM
Released In
v43.8.1Release Date
Oct 19, 2026, 7:49:10 PM
44-x-y
MergedPR Number
#55127Merged At
Oct 19, 2026, 7:48:03 PM
Released In
v44.9.1Release Date
Oct 19, 2026, 7:48:55 PM
45-x-y
MergedPR Number
#55129Merged At
Oct 19, 2026, 7:47:53 PM
Released In
v45.0.0-beta.6Release Date
Oct 19, 2026, 8:59:55 PM
Semver Impact
Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron