CVE-2025-12909

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2025-11-08. NVD baseline CVSS 5.3; sources differ by 0.0.

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

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

Insufficient policy enforcement in Devtools in Google Chrome prior to 140.0.7339.80 allowed a remote attacker to leak cross-origin data via Devtools. (Chromium security severity: Low)

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

November 8, 2025

Last Modified

November 21, 2025

References (2)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 139.0.7258.66-1~deb12u1 (248 versions)140.0.7339.80-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 140.0.7339.80-1~deb12u1 (14 versions)140.0.7339.80-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 140.0.7339.80-1~deb13u1 (15 versions)140.0.7339.80-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:13 UTCEPSS rescore
  4. 2026-09-15 03:08 UTCEPSS rescore
  5. 2026-09-13 16:45 UTCEPSS rescore
  6. 2026-09-12 18:36 UTCOSV refresh
  7. 2026-09-12 14:59 UTCEPSS rescore
  8. 2026-09-11 14:51 UTCEPSS rescore
  9. 2026-09-11 09:35 UTCEPSS rescore
  10. 2026-09-10 09:33 UTCEPSS rescore
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-04 13:59 UTCEPSS rescore
  15. 2026-09-04 05:05 UTCEPSS rescore
  16. 2026-09-02 14:10 UTCEPSS rescore
  17. 2026-09-01 13:52 UTCEPSS rescore
  18. 2026-09-01 04:38 UTCEPSS rescore
  19. 2026-08-30 19:16 UTCEPSS rescore
  20. 2026-08-30 01:21 UTCEPSS rescore
  21. 2026-08-28 21:40 UTCEPSS rescore
  22. 2026-08-27 14:24 UTCEPSS rescore
  23. 2026-08-26 14:45 UTCEPSS rescore
  24. 2026-08-25 13:47 UTCEPSS rescore
  25. 2026-08-24 23:44 UTCOSV refresh
Show 75 more
  1. 2026-08-24 14:15 UTCEPSS rescore
  2. 2026-08-23 00:18 UTCEPSS rescore
  3. 2026-08-21 23:48 UTCEPSS rescore
  4. 2026-08-19 17:02 UTCEPSS rescore
  5. 2026-08-18 13:47 UTCEPSS rescore
  6. 2026-08-16 14:55 UTCEPSS rescore
  7. 2026-08-16 02:13 UTCEPSS rescore
  8. 2026-08-16 02:13 UTCEPSS rescore
  9. 2026-08-15 01:29 UTCEPSS rescore
  10. 2026-08-13 21:59 UTCEPSS rescore
  11. 2026-08-12 13:49 UTCEPSS rescore
  12. 2026-08-11 13:41 UTCEPSS rescore
  13. 2026-08-10 23:59 UTCEPSS rescore
  14. 2026-08-09 13:45 UTCEPSS rescore
  15. 2026-08-08 17:19 UTCOSV refresh
  16. 2026-08-07 16:26 UTCEPSS rescore
  17. 2026-08-06 13:45 UTCEPSS rescore
  18. 2026-08-05 19:16 UTCEPSS rescore
  19. 2026-08-04 15:09 UTCEPSS rescore
  20. 2026-08-04 10:37 UTCEPSS rescore
  21. 2026-08-03 10:35 UTCEPSS rescore
  22. 2026-08-02 02:25 UTCEPSS rescore
  23. 2026-08-01 04:14 UTCEPSS rescore
  24. 2026-07-30 16:26 UTCEPSS rescore
  25. 2026-07-30 01:29 UTCEPSS rescore
  26. 2026-07-28 15:35 UTCEPSS rescore
  27. 2026-07-27 14:12 UTCEPSS rescore
  28. 2026-07-26 14:53 UTCEPSS rescore
  29. 2026-07-25 14:17 UTCEPSS rescore
  30. 2026-07-24 14:16 UTCEPSS rescore
  31. 2026-07-23 16:11 UTCOSV refresh
  32. 2026-07-23 14:17 UTCEPSS rescore
  33. 2026-07-23 02:48 UTCEG score recompute
  34. 2026-07-22 14:07 UTCEPSS rescore
  35. 2026-07-22 14:07 UTCEPSS rescore
  36. 2026-07-21 15:24 UTCEPSS rescore
  37. 2026-07-19 14:30 UTCEPSS rescore
  38. 2026-07-19 14:30 UTCEPSS rescore
  39. 2026-07-19 02:28 UTCEPSS rescore
  40. 2026-07-19 02:28 UTCEPSS rescore
  41. 2026-07-18 10:03 UTCEPSS rescore
  42. 2026-07-16 17:02 UTCEPSS rescore
  43. 2026-07-16 17:02 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 01:59 UTCEPSS rescore
  47. 2026-07-15 01:59 UTCEPSS rescore
  48. 2026-07-13 22:29 UTCEPSS rescore
  49. 2026-07-13 22:29 UTCEPSS rescore
  50. 2026-07-13 06:12 UTCEPSS rescore
  51. 2026-07-12 05:46 UTCEPSS rescore
  52. 2026-07-12 05:45 UTCEPSS rescore
  53. 2026-07-11 08:26 UTCEPSS rescore
  54. 2026-07-11 08:26 UTCEPSS rescore
  55. 2026-07-09 19:09 UTCEPSS rescore
  56. 2026-07-08 15:14 UTCEPSS rescore
  57. 2026-07-07 13:45 UTCEPSS rescore
  58. 2026-07-06 16:26 UTCEPSS rescore
  59. 2026-07-06 10:41 UTCOSV refresh
  60. 2026-07-06 02:22 UTCEPSS rescore
  61. 2026-07-06 02:22 UTCEPSS rescore
  62. 2026-07-05 02:30 UTCEPSS rescore
  63. 2026-07-04 06:30 UTCEPSS rescore
  64. 2026-07-01 15:06 UTCEPSS rescore
  65. 2026-06-30 23:21 UTCEPSS rescore
  66. 2026-06-29 14:06 UTCEPSS rescore
  67. 2026-06-28 14:07 UTCEPSS rescore
  68. 2026-06-28 14:07 UTCEPSS rescore
  69. 2026-06-28 04:55 UTCEPSS rescore
  70. 2026-06-27 03:08 UTCEPSS rescore
  71. 2026-06-27 03:08 UTCEPSS rescore
  72. 2026-06-25 13:49 UTCEPSS rescore
  73. 2026-06-25 13:49 UTCEPSS rescore
  74. 2026-06-24 14:04 UTCEPSS rescore
  75. 2026-06-24 14:04 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-12909?
CVE-2025-12909 is a medium vulnerability published on November 8, 2025. Insufficient policy enforcement in Devtools in Google Chrome prior to 140.0.7339.80 allowed a remote attacker to leak cross-origin data via Devtools. (Chromium security severity: Low)
When was CVE-2025-12909 disclosed?
CVE-2025-12909 was first published in the National Vulnerability Database on November 8, 2025, with the most recent update on November 21, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-12909 actively exploited?
CVE-2025-12909 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 90.4% of all scored CVEs.
What is the CVSS score of CVE-2025-12909?
CVE-2025-12909 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2025-12909?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-12909, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-12909

Explore →

Is Your Infrastructure Affected by CVE-2025-12909?

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

Start Free Scan →Browse All CVEs