NetSight

Security Dashboard

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

Reset
204 matching advisories · page 5 of 7Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
unscored CVE-2025-68217 In the Linux kernel, the following vulnerability has been resolved: Input: pegasus-notetaker - fix potential out-of-bounds access In the pegasus_notetaker driv… 2025-12-16 medium5.3 CVE-2025-62181 Pega Platform versions 7.1.0 through Infinity 25.1.0 are affected by a User Enumeration. 2025-12-10 medium6.5 CVE-2025-9559 Pega Platform versions 8.7.5 to Infinity 24.2.2 are affected by a Insecure Direct Object Reference issue in a user interface component that can only be used to… pega · pega_platform 2025-10-16 medium5.5 CVE-2025-8681 Pega Platform versions 7.1.0 to Infinity 24.2.2 are affected by a Stored XSS issue in a user interface component. pega · pega_platform 2025-09-10 high7.1 CVE-2025-2161 Pega Platform versions 7.2.1 to Infinity 24.2.1 are affected by an XSS issue with Mashup pega · pega_platform 2025-04-14 high8.1 CVE-2025-2160 Pega Platform versions 8.4.3 to Infinity 24.2.1 are affected by an XSS issue with Mashup pega · pega_platform 2025-04-14 medium5.4 CVE-2024-12211 Pega Platform versions 8.1 to Infinity 24.2.0 are affected by an Stored XSS issue with profile. pega · pega_platform 2025-01-13 medium5.9 CVE-2024-10716 Pega Platform versions 8.1 to Infinity 24.2.0 are affected by an XSS issue with search. pega · infinity 2024-12-05 critical9.1 CVE-2024-10094 Pega Platform versions 6.x to Infinity 24.1.1 are affected by an issue with Improper Control of Generation of Code pega · infinity 2024-11-20 critical9.8 CVE-2024-50490 Missing Authorization vulnerability in lowcage PegaPoll pegapoll allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects PegaPoll: f… PegaPoll: from n/a through 2024-10-29 medium5.2 CVE-2024-6702 Pega Platform versions 8.1 to Infinity 24.1.2 are affected by an HTML Injection issue with Stage. pega · infinity 2024-09-12 medium5.5 CVE-2024-6701 Pega Platform versions 8.1 to Infinity 24.1.2 are affected by an XSS issue with case type. pega · infinity 2024-09-12 medium5.5 CVE-2024-6700 Pega Platform versions 8.1 to Infinity 24.1.2 are affected by an XSS issue with App name. pega · infinity 2024-09-12 high7.7 CVE-2023-50168 Pega Platform from 6.x to 8.8.4 is affected by an XXE issue with PDF Generation. pega · pega_platform 2024-03-14 medium5.4 CVE-2023-50167 Pega Platform from 7.1.7 to 23.1.1 is affected by an XSS issue with editing/rendering user html content. pega · pega_platform 2024-03-06 medium6.1 CVE-2023-50166 Pega Platform from 8.5.4 to 8.8.3 is affected by an XSS issue with an unauthenticated user and the redirect parameter. pega · platform 2024-01-31 high8.5 CVE-2023-50165 Pega Platform versions 8.2.1 to Infinity 23.1.0 are affected by an Generated PDF issue that could expose file contents. pega · platform 2024-01-31 medium4.6 CVE-2023-32089 Pega Platform versions 8.1 to 8.8.2 are affected by an XSS issue with Pin description pega · platform 2023-10-18 medium4.6 CVE-2023-32088 Pega Platform versions 8.1 to Infinity 23.1.0 are affected by an XSS issue with ad-hoc case creation pega · platform 2023-10-18 medium4.6 CVE-2023-32087 Pega Platform versions 8.1 to Infinity 23.1.0 are affected by an XSS issue with task creation pega · platform 2023-10-18 medium4.3 CVE-2023-4843 Pega Platform versions 7.1 to 8.8.3 are affected by an HTML Injection issue with a name field utilized in Visual Business Director, however this field can only… pega · pega_platform 2023-09-08 critical9.8 CVE-2023-32090 Pega platform clients who are using versions 6.1 through 7.3.1 may be utilizing default credentials pega · pega_platform 2023-08-07 high8.1 CVE-2023-28094 Pega platform clients who are using versions 7.4 through 8.8.x and have upgraded from a version prior to 8.x may be utilizing default credentials. pega · pega_platform 2023-06-22 medium6.1 CVE-2023-26465 Pega Platform versions 7.2 to 8.8.1 are affected by an XSS issue. pega · pega_platform 2023-06-09 medium5.4 CVE-2023-26467 A man in the middle can redirect traffic to a malicious server in a compromised configuration. pega · synchronization_engine 2023-04-10 medium6.5 CVE-2023-28093 A user with a compromised configuration can start an unsigned binary as a service. pega · synchronization_engine 2023-04-10 high7.8 CVE-2023-26466 A user with non-Admin access can change a configuration file on the client to modify the Server URL. pega · synchronization_engine 2023-04-10 medium4.5 CVE-2022-35656 Pega Platform from 8.3 to 8.7.3 vulnerability may allow authenticated security administrators to alter CSRF settings directly. pega · pega_platform 2022-08-22 medium6.1 CVE-2022-35655 Pega Platform from 7.3 to 8.7.3 is affected by an XSS issue due to a misconfiguration of a datapage setting. pega · pega_platform 2022-08-22 medium6.1 CVE-2022-35654 Pega Platform from 8.5.4 to 8.7.3 is affected by an XSS issue with an unauthenticated user and the redirect parameter. pega · pega_platform 2022-08-22

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.