{"items":[{"id":"NVI-00015272","kind":"vulnerability","title":"Electron: Custom protocol with supportFetchAPI but not corsEnabled allows cross-origin reads","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-v3j7-r9gq-3gjw","CVE-2026-70604"],"plain_summary":"GitHub lists this reviewed advisory for electron, electron, electron, electron. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0519ab42d273eeac1d8eecca6dfa16c3"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-05T15:59:46.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4ef072db82266914c811288d9f9c0572"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.354%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.29312. Missing scores are unknown.","source_id":"sr-0519ab42d273eeac1d8eecca6dfa16c3"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4ef072db82266914c811288d9f9c0572","url":"https://github.com/advisories/GHSA-v3j7-r9gq-3gjw","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-v3j7-r9gq-3gjw","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:58:09.980Z"},{"id":"sr-0519ab42d273eeac1d8eecca6dfa16c3","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-70604","publisher":"FIRST EPSS","observed_at":"2026-11-04T23:33:33.063Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"technology":"electron","known_exclusions":[],"conditions_summary":"### Impact\nA custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked.\n\nApps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected.\n\n### Workarounds\nSet `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.\n\n### Fixed Versions\n* `42.0.0`\n* `41.4.0`\n* `40.9.3`\n* `39.8.10`\n\n### For more information\nIf you have any questions or comments about this advisory, email Electron at security@electronjs.org","public_affected_ranges":[">= 42.0.0-alpha.1, < 42.0.0"]},{"certainty":"source_listed","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"technology":"electron","known_exclusions":[],"conditions_summary":"### Impact\nA custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked.\n\nApps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected.\n\n### Workarounds\nSet `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.\n\n### Fixed Versions\n* `42.0.0`\n* `41.4.0`\n* `40.9.3`\n* `39.8.10`\n\n### For more information\nIf you have any questions or comments about this advisory, email Electron at security@electronjs.org","public_affected_ranges":[">= 41.0.0-alpha.1, < 41.4.0"]},{"certainty":"source_listed","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"technology":"electron","known_exclusions":[],"conditions_summary":"### Impact\nA custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked.\n\nApps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected.\n\n### Workarounds\nSet `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.\n\n### Fixed Versions\n* `42.0.0`\n* `41.4.0`\n* `40.9.3`\n* `39.8.10`\n\n### For more information\nIf you have any questions or comments about this advisory, email Electron at security@electronjs.org","public_affected_ranges":[">= 40.0.0-alpha.1, < 40.9.3"]},{"certainty":"source_listed","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"technology":"electron","known_exclusions":[],"conditions_summary":"### Impact\nA custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked.\n\nApps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected.\n\n### Workarounds\nSet `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.\n\n### Fixed Versions\n* `42.0.0`\n* `41.4.0`\n* `40.9.3`\n* `39.8.10`\n\n### For more information\nIf you have any questions or comments about this advisory, email Electron at security@electronjs.org","public_affected_ranges":["< 39.8.10"]}],"null_published_at":"2026-11-06T07:24:11.255Z","source_updated_at":"2026-08-05T15:59:46.000Z","source_disclosed_at":"2026-08-05T15:59:45.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-03T09:58:09.980Z"},{"id":"NVI-00015272","kind":"vulnerability","title":"Electron: Custom protocol with supportFetchAPI but not corsEnabled allows cross-origin reads","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-v3j7-r9gq-3gjw","CVE-2026-70604"],"plain_summary":"GitHub lists this reviewed advisory for electron, electron, electron, electron. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-05T15:59:46.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4ef072db82266914c811288d9f9c0572"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4ef072db82266914c811288d9f9c0572","url":"https://github.com/advisories/GHSA-v3j7-r9gq-3gjw","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-v3j7-r9gq-3gjw","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:58:09.980Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"technology":"electron","known_exclusions":[],"conditions_summary":"### Impact\nA custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked.\n\nApps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected.\n\n### Workarounds\nSet `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.\n\n### Fixed Versions\n* `42.0.0`\n* `41.4.0`\n* `40.9.3`\n* `39.8.10`\n\n### For more information\nIf you have any questions or comments about this advisory, email Electron at security@electronjs.org","public_affected_ranges":[">= 42.0.0-alpha.1, < 42.0.0"]},{"certainty":"source_listed","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"technology":"electron","known_exclusions":[],"conditions_summary":"### Impact\nA custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked.\n\nApps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected.\n\n### Workarounds\nSet `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.\n\n### Fixed Versions\n* `42.0.0`\n* `41.4.0`\n* `40.9.3`\n* `39.8.10`\n\n### For more information\nIf you have any questions or comments about this advisory, email Electron at security@electronjs.org","public_affected_ranges":[">= 41.0.0-alpha.1, < 41.4.0"]},{"certainty":"source_listed","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"technology":"electron","known_exclusions":[],"conditions_summary":"### Impact\nA custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked.\n\nApps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected.\n\n### Workarounds\nSet `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.\n\n### Fixed Versions\n* `42.0.0`\n* `41.4.0`\n* `40.9.3`\n* `39.8.10`\n\n### For more information\nIf you have any questions or comments about this advisory, email Electron at security@electronjs.org","public_affected_ranges":[">= 40.0.0-alpha.1, < 40.9.3"]},{"certainty":"source_listed","source_ids":["sr-4ef072db82266914c811288d9f9c0572"],"technology":"electron","known_exclusions":[],"conditions_summary":"### Impact\nA custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked.\n\nApps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected.\n\n### Workarounds\nSet `corsEnabled: true` on schemes that must enforce CORS, and validate the request `Origin` in your protocol handler before returning sensitive data.\n\n### Fixed Versions\n* `42.0.0`\n* `41.4.0`\n* `40.9.3`\n* `39.8.10`\n\n### For more information\nIf you have any questions or comments about this advisory, email Electron at security@electronjs.org","public_affected_ranges":["< 39.8.10"]}],"null_published_at":"2026-11-03T10:03:26.566Z","source_updated_at":"2026-08-05T15:59:46.000Z","source_disclosed_at":"2026-08-05T15:59:45.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T09:58:09.980Z"}],"next_cursor":null,"snapshot_revision":"42594"}