CVE-2026-34778Network attack vector

Security-decision bypass via spoofed IPC replies

Published Apr 3, 2026 · Updated Apr 3, 2026

IPC reply spoofing in affected Electron releases allows remote authenticated users to control results returned to the main process. The internal IPC path accepts a service worker's forged reply and resolves webContents.executeJavaScript() or webFrameMain.executeJavaScript() with data whose origin was not verified. Exposure requires a registered service worker and a security-sensitive decision based on that returned data.

CVSS severity5.9
Medium
EPSS probability0.12%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

IPC reply spoofing in affected Electron releases allows remote authenticated users to control results returned to the main process. The internal IPC path accepts a service worker's forged reply and resolves webContents.executeJavaScript() or webFrameMain.executeJavaScript() with data whose origin was not verified. Exposure requires a registered service worker and a security-sensitive decision based on that returned data.

The record

CVE
CVE-2026-34778
Published
Apr 3, 2026
Updated
Apr 3, 2026
Vendor
Electron
Product
Electron
Classifications
CWE-345, CWE-290
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 3, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 3, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 38.8.6
  2. Affected versionversion=>= 39.0.0-alpha.1, < 39.8.1
  3. Affected versionversion=>= 40.0.0-alpha.1, < 40.8.1
  4. Affected versionversion=>= 41.0.0-alpha.1, < 41.0.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Electron · Electronversion=< 38.8.6; version=>= 39.0.0-alpha.1, < 39.8.1; version=>= 40.0.0-alpha.1, < 40.8.1; version=>= 41.0.0-alpha.1, < 41.0.0

Published CVSS scores

6.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
5.9GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-345Insufficient Verification of Data Authenticity
CWE-290Authentication Bypass by Spoofing

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo