CVE-2026-101897
Description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. From 1.20.0 until 1.21.1, the Angular DevTools background service worker accepts chrome.runtime.sendMessage runtime messages from untrusted web pages or third-party content scripts without adequately verifying the message source. An untrusted sender that obtains a valid randomized victim tabId can direct the extension to use chrome.debugger to attach to another browser tab and trigger Chrome DevTools Protocol breakpoints. This can display the debugging banner, pause JavaScript execution, and prevent interaction with the target tab, but it does not provide remote code execution, privilege escalation, or cross-origin access to memory or credentials. This issue is fixed in version 1.21.1.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://github.com/angular/angular/commit/7c053599c79a6ddd785a9bae33ff9fc7b355ea0d
- https://github.com/angular/angular/commit/cf492e8a372e2bbddb84987df12c33a52c23c72f
- https://github.com/angular/angular/commit/e02c4d89bcf5da9af499e0dfbba8c29206976ab3
- https://github.com/angular/angular/pull/70623
- https://github.com/angular/angular/security/advisories/GHSA-r653-wxfp-pp9c
CWEs
CWE-346 CWE-441 CWE-940
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.