NetSight

Security Dashboard

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

Reset
109 matching advisories · page 3 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.9 CVE-2026-30938 Parse Server has denylist `requestKeywordDenylist` keyword scan bypass through nested object placement npm · parse-server 2026-03-10 high8.2 CVE-2026-30925 Parse Server has Regular Expression Denial of Service (ReDoS) via `$regex` query in LiveQuery npm · parse-server 2026-03-10 critical9.3 CVE-2026-30863 Parse Server: JWT audience validation bypass in Google, Apple, and Facebook authentication adapters npm · parse-server 2026-03-07 medium6.9 CVE-2026-30854 Parse Server: GraphQL `__type` introspection bypass via inline fragments when public introspection is disabled npm · parse-server 2026-03-07 medium6.3 CVE-2026-30850 Parse Server: File metadata endpoint bypasses `beforeFind` / `afterFind` trigger authorization npm · parse-server 2026-03-07 medium6.3 CVE-2026-30848 Parse Server: `PagesRouter` path traversal allows reading files outside configured pages directory npm · parse-server 2026-03-07 medium6.9 CVE-2026-30835 parse-server: Malformed `$regex` query leaks database error details in API response npm · parse-server 2026-03-06 high8.5 CVE-2026-30229 parse-server's endpoint `/loginAs` allows `readOnlyMasterKey` to gain full read and write access as any user npm · parse-server 2026-03-06 medium6.9 CVE-2026-30228 parse-server's file creation and deletion bypasses `readOnlyMasterKey` write restriction npm · parse-server 2026-03-06 high8.6 CVE-2026-29182 Parse Server's Cloud Hooks and Cloud Jobs bypass `readOnlyMasterKey` write restriction npm · parse-server 2026-03-05 critical9.3 CVE-2026-27804 Parse Server: Account takeover via JWT algorithm confusion in Google auth adapter npm · parse-server 2026-02-25 high7.0 CVE-2026-27610 Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions npm · parse-dashboard 2026-02-25 high8.3 CVE-2026-27609 Parse Dashboard is Missing CSRF Protection for its Agent Endpoint npm · parse-dashboard 2026-02-25 critical9.3 CVE-2026-27608 Parse Dashboard is Missing Authorization for its Agent Endpoint npm · parse-dashboard 2026-02-25 critical9.9 CVE-2026-27595 Parse Dashboard has incomplete authentication on AI Agent endpoint npm · parse-dashboard 2026-02-25 high8.3 CVE-2025-68150 Parse Server is vulnerable to Server-Side Request Forgery (SSRF) via Instagram OAuth Adapter npm · parse-server 2025-12-16 medium5.3 CVE-2025-68115 Parse Server has a Cross-Site Scripting (XSS) vulnerability via Unescaped Mustache Template Variables npm · parse-server 2025-12-16 critical9.8 CVE-2025-67727 Parse Server is an open source backend that can be deployed to any infrastructure that runs Node.js. parseplatform · parse-server 2025-12-12 medium6.5 CVE-2025-57324 parse is vulnerable to prototype pollution npm · parse 2025-09-24 high8.1 CVE-2024-47183 Parse Server's custom object ID allows to acquire role privileges npm · parse-server 2024-10-04 critical9.0 CVE-2024-29027 Server crashes on invalid Cloud Function or Cloud Job name npm · parse-server 2024-03-19 critical10.0 CVE-2024-27298 ZDI-CAN-19105: Parse Server literalizeRegexPart SQL Injection npm · parse-server 2024-03-01 high7.5 CVE-2023-46119 Parse Server may crash when uploading file without extension npm · parse-server 2023-10-24 high7.5 CVE-2023-41058 Trigger `beforeFind` not invoked in internal query pipeline when fetching pointer npm · parse-server 2023-09-04 critical9.8 CVE-2023-36475 Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. npm · parse-server 2023-06-28 medium6.3 CVE-2023-32689 Phishing attack vulnerability by uploading malicious HTML file npm · parse-server 2023-05-30 medium4.9 CVE-2023-32688 Invalid push request payload crashes Parse Server npm · parse-server-push-adapter 2023-05-22 high8.7 CVE-2023-22474 Parse Server option `masterKeyIps` vulnerability to IP spoofing npm · parse-server 2023-01-31 high7.2 CVE-2022-41879 Parse Server is vulnerable to Prototype Pollution via Cloud Code Webhooks npm · parse-server 2022-11-10 high7.2 CVE-2022-41878 Parse Server vulnerable to Prototype Pollution via Cloud Code Webhooks or Cloud Code Triggers npm · parse-server 2022-11-09

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.