NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
34 matching advisories · page 1 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.4 CVE-2026-58873 In addDragDropListener of WindowManagerService.java, there is a possible permission bypass due to a missing permission check. Google · Android XR, google · android_xr 19 days ago high8.4 CVE-2026-58866 In setAccessibilityWindowAttributes of AccessibilityWindowManager.java, there is a possible untrusted/misleading UI issue due to a missing permission check. Google · Android, google · android 19 days ago high7.8 CVE-2026-28577 In addWindow of WindowManagerService.java, there is a possible tapjacking issue due to a tapjacking/overlay attack. google · android 2026-06-01 high7.3 CVE-2025-48634 In relayoutWindow of WindowManagerService.java, there is a possible tapjack attack due to a missing permission check. google · android 2026-03-02 low2.4 CVE-2025-21046 Improper access control in WindowManager in Samsung DeX prior to SMR Oct-2025 Release 1 allows physical attackers to temporarily access to recent app list. samsung · android 2025-10-10 medium4.0 CVE-2025-26422 In dump of WindowManagerService.java, there is a possible way of running dumpsys without the required permission due to a missing permission check. google · android, Google · Android 2025-09-04 high7.8 CVE-2025-22434 In handleKeyGestureEvent of PhoneWindowManager.java, there is a possible lock screen bypass due to a logic error in the code. google · android 2025-09-02 medium6.2 CVE-2024-34637 Improper access control in WindowManagerService prior to SMR Sep-2024 Release 1 in Android 12, and SMR Jun-2024 Release 1 in Android 13 and Android 14 allows l… samsung · android 2024-09-04 medium6.2 CVE-2023-52721 The WindowManager module has a vulnerability in permission control. huawei · harmonyos 2024-05-14 critical9.8 CVE-2023-52378 Vulnerability of incorrect service logic in the WindowManagerServices module.Successful exploitation of this vulnerability may cause features to perform abnorm… huawei · emui, huawei · harmonyos 2024-02-18 high7.5 CVE-2023-52375 Permission control vulnerability in the WindowManagerServices module.Successful exploitation of this vulnerability may affect availability. huawei · emui, huawei · harmonyos 2024-02-18 high7.5 CVE-2023-36293 SQL injection vulnerability in wmanager v.1.0.7 and before allows a remote attacker to obtain sensitive information via a crafted script to the company.php com… wmanager · wmanager 2023-07-11 medium5.5 CVE-2023-21177 In requestAppKeyboardShortcuts of WindowManagerService.java, there is a possible way to infer the app a user is interacting with due to a missing permission ch… google · android 2023-06-28 medium5.5 CVE-2023-21026 In updateInputChannel of WindowManagerService.java, there is a possible way to set a touchable region beyond its own SurfaceControl due to a logic error in the… google · android 2023-03-24 medium6.2 CVE-2023-21440 Improper access control vulnerability in WindowManagerService prior to SMR Feb-2023 Release 1 allows attackers to take a screen capture. samsung · android 2023-02-09 medium5.7 CVE-2022-39899 Improper authentication vulnerability in Samsung WindowManagerService prior to SMR Dec-2022 Release 1 allows attacker to send the input event using S Pen gestu… google · android 2022-12-08 high7.8 CVE-2022-20246 In WindowManager, there is a possible bypass of the restrictions for starting activities from the background due to an incorrect UID/permission check. google · android 2022-08-11 low2.4 CVE-2022-20245 In WindowManager, there is a possible method to create a recording of the lock screen due to an insecure default value. google · android 2022-08-11 low3.9 CVE-2022-20226 In finishDrawingWindow of WindowManagerService.java, there is a possible tapjacking due to improper input validation. google · android 2022-07-13 high7.8 CVE-2022-20192 In grantEmbeddedWindowFocus of WindowManagerService.java, there is a possible way to change an input channel for embedded hierarchy due to a permissions bypass. google · android 2022-06-15 high7.3 CVE-2021-39691 In WindowManager, there is a possible tapjacking attack due to an incorrect window flag when processing user input. google · android 2022-06-15 high7.8 CVE-2021-39758 In WindowManager, there is a possible way to start a foreground activity from the background due to a missing permission check. google · android 2022-03-30 high7.8 CVE-2021-39749 In WindowManager, there is a possible way to start non-exported and protected activities due to a missing permission check. google · android 2022-03-30 high7.0 CVE-2021-0688 In lockNow of PhoneWindowManager.java, there is a possible lock screen bypass due to a race condition. google · android 2021-10-06 high7.8 CVE-2021-0438 In several functions of InputDispatcher.cpp, WindowManagerService.java, and related files, there is a possible tapjacking attack due to an incorrect FLAG_OBSCU… google · android 2021-04-13 high7.8 CVE-2020-0475 In createInputConsumer of WindowManagerService.java, there is a possible way to block and intercept input events due to a missing permission check. google · android 2020-12-15 high7.8 CVE-2020-0099 In addWindow of WindowManagerService.java, there is a possible window overlay attack due to an insecure default value. google · android 2020-12-14 high7.8 CVE-2020-0267 In WindowManager, there is a possible launch of an unexpected app due to a confused deputy. google · android 2020-09-17 high7.3 CVE-2019-2122 In LockTaskController.lockKeyguardIfNeeded of the LockTaskController.java, there was a difference in the handling of the default case between the WindowManager… google · android 2019-08-20 high7.8 CVE-2017-0752 A elevation of privilege vulnerability in the Android framework (windowmanager). google · android 2017-09-08

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.