CVE-2026-13022

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

Inappropriate implementation in Autofill in Google Chrome prior to 149.0.7827.197 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 1, 2026

Advisory Details (2)

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

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

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

Vendor Advisories for CVE-2026-13022(2)

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 15× in last 7d / 79× 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-27 17:33 UTCEG score recompute
  2. 2026-07-27 17:33 UTCVendor advisory
  3. 2026-07-27 17:33 UTCGHSA enrichment
  4. 2026-07-27 14:13 UTCEPSS rescore
  5. 2026-07-26 15:24 UTCEG score recompute
  6. 2026-07-26 15:24 UTCVendor advisory
  7. 2026-07-26 15:24 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-25 14:17 UTCEPSS rescore
  11. 2026-07-24 14:17 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:05 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-21 15:24 UTCEPSS rescore
  16. 2026-07-20 17:08 UTCEPSS rescore
  17. 2026-07-19 14:30 UTCEPSS rescore
  18. 2026-07-19 02:28 UTCEPSS rescore
  19. 2026-07-17 05:16 UTCVendor advisory
  20. 2026-07-17 05:16 UTCGHSA enrichment
  21. 2026-07-16 17:02 UTCEPSS rescore
  22. 2026-07-16 06:56 UTCVendor advisory
  23. 2026-07-16 06:56 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 08:05 UTCVendor advisory
Show 64 more
  1. 2026-07-15 08:04 UTCGHSA enrichment
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 09:43 UTCVendor advisory
  4. 2026-07-14 09:43 UTCGHSA enrichment
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 11:04 UTCGHSA enrichment
  7. 2026-07-13 06:12 UTCEPSS rescore
  8. 2026-07-12 12:44 UTCVendor advisory
  9. 2026-07-12 12:44 UTCGHSA enrichment
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 14:23 UTCVendor advisory
  12. 2026-07-11 14:23 UTCGHSA enrichment
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-10 15:47 UTCVendor advisory
  15. 2026-07-10 15:47 UTCGHSA enrichment
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 16:58 UTCVendor advisory
  18. 2026-07-09 16:58 UTCGHSA enrichment
  19. 2026-07-08 18:37 UTCVendor advisory
  20. 2026-07-08 18:36 UTCGHSA enrichment
  21. 2026-07-08 15:15 UTCEPSS rescore
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-07 20:17 UTCVendor advisory
  24. 2026-07-07 20:17 UTCGHSA enrichment
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-06 21:57 UTCVendor advisory
  27. 2026-07-06 21:56 UTCGHSA enrichment
  28. 2026-07-06 16:27 UTCEPSS rescore
  29. 2026-07-05 23:36 UTCVendor advisory
  30. 2026-07-05 23:36 UTCGHSA enrichment
  31. 2026-07-05 02:30 UTCEPSS rescore
  32. 2026-07-05 02:30 UTCEPSS rescore
  33. 2026-07-05 01:16 UTCVendor advisory
  34. 2026-07-05 01:16 UTCGHSA enrichment
  35. 2026-07-04 06:31 UTCEPSS rescore
  36. 2026-07-04 02:44 UTCVendor advisory
  37. 2026-07-04 02:43 UTCGHSA enrichment
  38. 2026-07-03 04:20 UTCVendor advisory
  39. 2026-07-03 04:20 UTCGHSA enrichment
  40. 2026-07-02 05:59 UTCVendor advisory
  41. 2026-07-02 05:59 UTCGHSA enrichment
  42. 2026-07-01 15:06 UTCEPSS rescore
  43. 2026-07-01 15:06 UTCEPSS rescore
  44. 2026-07-01 07:37 UTCVendor advisory
  45. 2026-07-01 07:37 UTCGHSA enrichment
  46. 2026-06-30 23:22 UTCEPSS rescore
  47. 2026-06-30 09:16 UTCVendor advisory
  48. 2026-06-30 09:16 UTCGHSA enrichment
  49. 2026-06-29 14:06 UTCEPSS rescore
  50. 2026-06-29 10:56 UTCVendor advisory
  51. 2026-06-29 10:55 UTCGHSA enrichment
  52. 2026-06-28 14:07 UTCEPSS rescore
  53. 2026-06-28 12:34 UTCVendor advisory
  54. 2026-06-28 12:34 UTCGHSA enrichment
  55. 2026-06-28 04:56 UTCEPSS rescore
  56. 2026-06-28 04:56 UTCEPSS rescore
  57. 2026-06-27 14:14 UTCEG score recompute▲ 6.50
  58. 2026-06-27 14:14 UTCVendor advisory
  59. 2026-06-27 14:14 UTCGHSA enrichment
  60. 2026-06-27 03:08 UTCEPSS rescore
  61. 2026-06-26 03:53 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  62. 2026-06-25 13:49 UTCEPSS rescore
  63. 2026-06-24 20:08 UTCEG score recompute
  64. 2026-06-24 20:03 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-13022?
CVE-2026-13022 is a medium vulnerability published on June 24, 2026. Inappropriate implementation in Autofill in Google Chrome prior to 149.0.7827.197 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-13022 disclosed?
CVE-2026-13022 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13022 actively exploited?
CVE-2026-13022 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-13022?
CVE-2026-13022 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-13022?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13022, 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-13022

Explore →

Is Your Infrastructure Affected by CVE-2026-13022?

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

Start Free Scan →Browse All CVEs