NetSight

Security Dashboard

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

Reset
6,003 matching advisories · page 15 of 201Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-1462 A vulnerability in the `TFSMLayer` class of the `keras` package, version 3.13.0, allows attacker-controlled TensorFlow SavedModels to be loaded during deserial… pip · keras 2026-04-13 high8.5 CVE-2026-5483 A flaw was found in odh-dashboard in Red Hat Openshift AI. redhat · openshift_ai 2026-04-10 high8.8 CVE-2026-40217 LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.Exploited pip · litellm 2026-04-10 high7.5 CVE-2026-34486 Apache Tomcat Missing Encryption of Sensitive Data VulnerabilityExploited maven · org.apache.tomcat:tomcat, maven · org.apache.tomcat:tomcat-tribes 2026-04-09 high7.5 CVE-2026-1584 A flaw was found in gnutls. gnu · gnutls, redhat · hardened_images 2026-04-09 medium6.7 CVE-2026-4878 A flaw was found in libcap. libcap_project · libcap, redhat · openshift_container_platform, redhat · enterprise_linux 2026-04-09 high7.1 CVE-2026-32590 A flaw was found in Red Hat Quay's handling of resumable container image layer uploads. redhat · mirror_registry_for_red_hat_openshift, redhat · quay 2026-04-08 high7.4 CVE-2026-32589 A flaw was found in Red Hat Quay's container image upload process. redhat · mirror_registry_for_red_hat_openshift, redhat · quay 2026-04-08 medium5.3 CVE-2025-14243 A flaw was found in the OpenShift Mirror Registry. redhat · mirror_registry_for_red_hat_openshift 2026-04-08 medium5.2 CVE-2026-32591 A flaw was found in Red Hat Quay's Proxy Cache configuration feature. When an organization... Red Hat · Red Hat Quay 3.10, Red Hat · Red Hat Quay 3.9, Red Hat · Red Hat Quay 3.17 +9 2026-04-08 medium6.5 CVE-2026-2377 A flaw was found in Red Hat Quay and mirror registry for Red Hat OpenShift. Red Hat · Red Hat Quay 3.12, Red Hat · Red Hat Quay 3.15, Red Hat · Red Hat Quay 3.14 +5 2026-04-08 medium6.4 CVE-2025-58713 A container privilege escalation flaw was found in certain Red Hat Process Automation Manager images. redhat · process_automation_manager 2026-04-08 medium6.4 CVE-2025-57854 A container privilege escalation flaw was found in certain OpenShift Update Service (OSUS) images. redhat · openshift_update_service 2026-04-08 medium6.4 CVE-2025-57853 A container privilege escalation flaw was found in certain Web Terminal images. redhat · web_terminal 2026-04-08 medium6.4 CVE-2025-57851 A container privilege escalation flaw was found in certain Multicluster Engine for Kubernetes images. redhat · advanced_cluster_management_for_kubernetes 2026-04-08 medium6.4 CVE-2025-57847 A container privilege escalation flaw was found in certain Ansible Automation Platform images. redhat · ansible_automation_platform 2026-04-08 high7.8 CVE-2025-14821 A flaw was found in libssh. libssh · libssh, redhat · hardened_images 2026-04-07 medium5.5 CVE-2026-5745 A flaw was found in libarchive. libarchive · libarchive, redhat · hardened_images, redhat · openshift_container_platform +1 2026-04-07 high8.2 CVE-2026-4740 Rhacm: open cluster management (ocm): cross-cluster privilege escalation via improper kubernetes client certificate renewal validation go · open-cluster-management.io/ocm 2026-04-07 medium5.0 CVE-2026-5704 A flaw was found in tar. gnu · tar, redhat · hardened_images, redhat · enterprise_linux 2026-04-06 medium5.6 CVE-2026-5673 A flaw was found in libtheora. xiph · theora, redhat · enterprise_linux 2026-04-06 low3.7 CVE-2026-37977 Keycloak vulnerable to information disclosure via CORS header injection due to unvalidated JWT azp claim maven · org.keycloak:keycloak-services 2026-04-06 medium4.0 CVE-2026-2625 A flaw was found in rust-rpm-sequoia. redhat · hardened_images, sequoia-pgp · rpm-sequoia, redhat · enterprise_linux 2026-04-03 low3.7 CVE-2026-3184 A flaw was found in util-linux. kernel · util-linux, redhat · hardened_images, Red Hat · Red Hat Hardened Images 2026-04-03 high8.1 CVE-2026-4636 Keycloak: UMA Policy Resource Injection Allows Unauthorized Cross-User Permission Grants maven · org.keycloak:keycloak-services 2026-04-02 high7.5 CVE-2026-4634 Keycloak: Application-Level DoS via Scope Processing maven · org.keycloak:keycloak-services 2026-04-02 medium5.3 CVE-2026-4325 Keycloak: Replay of action tokens via improper handling of single-use entries maven · org.keycloak:keycloak-services 2026-04-02 high7.4 CVE-2026-4282 Keycloak: Privilege escalation via forged authorization codes due to SingleUseObjectProvider isolation flaw maven · org.keycloak:keycloak-services 2026-04-02 high7.3 CVE-2026-3872 Keycloak: Redirect URI validation bypass via ..;/ path traversal in OIDC auth endpoint maven · org.keycloak:keycloak-services 2026-04-02 high7.5 CVE-2026-35092 A flaw was found in Corosync. corosync · corosync, redhat · openshift, redhat · enterprise_linux 2026-04-01

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.