CVE-2026-13281

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Integer overflow in Mojo in Google Chrome prior to 149.0.7827.201 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)

CVSS v3
8.3
EG Score
8.3(high)
EPSS
7.5%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 27, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/513138301
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01245939337.html

Vendor Advisories for CVE-2026-13281(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 35× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 19:03 UTCEG score recompute
  2. 2026-07-06 19:03 UTCGHSA enrichment
  3. 2026-07-06 07:14 UTCEG score recompute
  4. 2026-07-06 07:14 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 19:26 UTCEG score recompute
  7. 2026-07-05 19:26 UTCGHSA enrichment
  8. 2026-07-05 07:39 UTCEG score recompute
  9. 2026-07-05 07:38 UTCGHSA enrichment
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-04 19:49 UTCEG score recompute
  13. 2026-07-04 19:49 UTCGHSA enrichment
  14. 2026-07-04 08:01 UTCEG score recompute
  15. 2026-07-04 08:01 UTCGHSA enrichment
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 20:13 UTCEG score recompute
  18. 2026-07-03 20:13 UTCGHSA enrichment
  19. 2026-07-03 08:26 UTCEG score recompute
  20. 2026-07-03 08:25 UTCGHSA enrichment
  21. 2026-07-02 20:38 UTCEG score recompute
  22. 2026-07-02 20:38 UTCGHSA enrichment
  23. 2026-07-02 08:48 UTCEG score recompute
  24. 2026-07-02 08:48 UTCGHSA enrichment
  25. 2026-07-01 20:57 UTCEG score recompute
Show 24 more
  1. 2026-07-01 20:57 UTCGHSA enrichment
  2. 2026-07-01 15:06 UTCEPSS rescore
  3. 2026-07-01 15:06 UTCEPSS rescore
  4. 2026-07-01 09:09 UTCEG score recompute
  5. 2026-07-01 09:09 UTCGHSA enrichment
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 21:22 UTCEG score recompute
  8. 2026-06-30 21:22 UTCGHSA enrichment
  9. 2026-06-30 09:33 UTCEG score recompute
  10. 2026-06-30 09:33 UTCGHSA enrichment
  11. 2026-06-29 21:45 UTCEG score recompute
  12. 2026-06-29 21:45 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 09:58 UTCEG score recompute
  15. 2026-06-29 09:58 UTCGHSA enrichment
  16. 2026-06-28 22:10 UTCEG score recompute▲ 8.30
  17. 2026-06-28 22:10 UTCGHSA enrichment
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 8.3 · severity → HIGH
  23. 2026-06-25 23:51 UTCEG score recompute
  24. 2026-06-25 23:50 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-13281?
CVE-2026-13281 is a high vulnerability published on June 25, 2026. Integer overflow in Mojo in Google Chrome prior to 149.0.7827.201 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)
When was CVE-2026-13281 disclosed?
CVE-2026-13281 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13281 actively exploited?
CVE-2026-13281 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13281?
CVE-2026-13281 has a CVSS v3.1 base score of 8.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-13281?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13281, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13281

Explore →

Is Your Infrastructure Affected by CVE-2026-13281?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs