How severe is CVE-2026-3910?

CVE-2026-3910 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-3910?

Affected package information for CVE-2026-3910 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-3910?

No fixed version has been published for CVE-2026-3910 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2026-3910 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-3910 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-3910?

CVE-2026-3910 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2026-3910 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-3910 (Google Chromium V8 Improper Restriction of Operations Within the Bounds of a Memory Buffer Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-03-13. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-03-27. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-3910?

CVE-2026-3910 is classified as Code Injection (CWE-94), Buffer Overflow (CWE-119). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-3910 published, and has it been updated?

CVE-2026-3910 was published on March 13, 2026 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2026-3910: Remote Code Execution (High 8.8)

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk87th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Inappropriate implementation in V8 in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Frequently Asked Questions

Inappropriate implementation in V8 in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

O3 Security · Impact-Aware SCA

Is CVE-2026-3910 in your stack?

O3 detects CVE-2026-3910 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works