NetSight

Security Dashboard

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

Reset
1,802 matching advisories · page 5 of 61Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.8 CVE-2026-85317 Use of Cache Containing Sensitive Information vulnerability in Apache Camel HTTP component. apache · camel 33 days ago medium4.8 CVE-2026-85316 Insufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component. apache · camel 33 days ago medium5.3 CVE-2026-85315 Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel gRPC component. apache · camel 33 days ago medium6.5 CVE-2026-85314 Improper Input Validation vulnerability in Apache Camel Mail component. apache · camel 33 days ago medium4.3 CVE-2026-85313 Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Jetty component. apache · camel 33 days ago medium4.8 CVE-2026-85312 Improper Input Validation vulnerability in Apache Camel Core component. apache · camel 33 days ago medium4.8 CVE-2026-85301 Improper Authentication vulnerability in Apache Camel Keycloak component. Apache Camel: from, from 33 days ago medium5.5 CVE-2026-85300 Incorrect Default Permissions vulnerability in Apache Camel PQC component. Apache Camel: from, from 33 days ago medium6.5 CVE-2026-85296 Exposure of Data Element to Wrong Session vulnerability in Apache Camel AS2 component. apache · camel 33 days ago medium5.5 CVE-2026-85260 Insertion of Sensitive Information into Log File vulnerability in Apache Camel MLLP component. apache · camel 33 days ago medium5.3 CVE-2026-85257 Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CXF component. apache · camel 33 days ago medium6.5 CVE-2026-85254 Improper Handling of Case Sensitivity vulnerability in Apache Camel Platform HTTP component. apache · camel 33 days ago medium6.5 CVE-2026-85249 Improper Input Validation vulnerability in Apache Camel Tika component. apache · camel 33 days ago medium5.9 CVE-2026-85248 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Camel PQC component. Apache Camel: from, from 33 days ago medium5.9 CVE-2026-85247 Improper Certificate Validation vulnerability in Apache Camel Knative component. apache · camel 33 days ago medium5.3 CVE-2026-85246 Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Mina component. apache · camel 33 days ago medium5.9 CVE-2026-85245 Exposure of Data Element to Wrong Session vulnerability in Apache Camel Thrift component. apache · camel 33 days ago medium5.9 CVE-2026-85243 Improper Validation of Integrity Check Value vulnerability in Apache Camel Crypto PGP component. apache · camel 33 days ago medium5.9 CVE-2026-84181 Improper Authentication vulnerability in Apache Camel Shiro component. apache · camel 33 days ago medium5.3 CVE-2026-84180 Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Knative component. apache · camel 33 days ago medium6.1 CVE-2026-84178 Cross-Site Request Forgery (CSRF) vulnerability in Apache Camel OAuth component. Apache Camel: from, from 33 days ago medium6.5 CVE-2026-84176 Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache Camel Platform HTTP Vertx component. apache · camel 33 days ago medium5.9 CVE-2026-78163 Server-Side Request Forgery (SSRF), Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') and Exposure of Sensitive Information to an … Apache Camel: from, from 33 days ago medium5.4 CVE-2026-86589 Incorrect implementation of authentication algorithm vulnerability in Apache Answer. Apache Answer 33 days ago medium4.3 CVE-2026-71563 Missing Authorization vulnerability in Apache Answer. Apache Answer 33 days ago medium5.3 CVE-2026-68482 Missing Authorization vulnerability in Apache Answer. Apache Answer 33 days ago medium5.4 CVE-2026-67249 A vulnerability in Apache Answer. Apache Answer 33 days ago medium6.5 CVE-2026-108780 Potential JDBC source configuration validation vulnerability in Apache Kylin. Apache Kylin: from 33 days ago medium5.3 CVE-2026-108776 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Kylin. Apache Kylin: from 33 days ago medium6.5 CVE-2026-108766 Missing authorization on jdbc source config update in Apache Kylin. Apache Kylin: from 33 days ago

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.