NetSight

Security Dashboard

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

Reset
32 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-133702 free5GC PCF through 1.4.6 contains a resource leak in postAppSessCtxProcedure that leaves PCC rules and QoS data in the SM policy decision after rejected Npcf_… free5gc · pcf, Free5Gc · pcf 31 hours ago medium5.3 CVE-2026-94043 A vulnerability was determined in Free5GC up to 4.2.3. Free5GC 2026-09-20 medium6.9 CVE-2026-53551 free5GC AUSF: null byte injection in supiOrSuci causes HTTP 500 internal service failure go · github.com/free5gc/free5gc, go · github.com/free5gc/ausf 2026-07-31 medium6.9 CVE-2026-47780 free5GC UDR has improper `ueId` validation in EE subscription handlers that allows arbitrary identifier persistence go · github.com/free5gc/udr 2026-06-11 medium6.5 CVE-2026-44324 free5GC's UDR nudr-dr DELETE amf-subscriptions panics on missing UE state via nil interface type assertion (single authenticated request) go · github.com/free5gc/udr 2026-05-08 medium4.3 CVE-2026-44323 free5GC's UDR nudr-dr DELETE amf-subscriptions panics on missing subsId when UE state exists (nil pointer dereference) go · github.com/free5gc/udr 2026-05-08 medium6.5 CVE-2026-44318 free5GC's BSF concurrent PUT /nbsf-management/v1/subscriptions/{subId} crashes the BSF process via concurrent map read/write on Subscriptions go · github.com/free5gc/bsf 2026-05-08 medium6.5 CVE-2026-44317 free5GC's PCF npcf-policyauthorization POST /app-sessions panics on suppFeat=1 with missing AfRoutReq via nil pointer dereference go · github.com/free5gc/pcf 2026-05-08 medium6.1 CVE-2026-42081 Free5GC AMF Bypasses UE Security Capabilities on NGAP PathSwitchRequest go · github.com/free5gc/amf 2026-05-07 medium5.3 CVE-2026-41136 free5GC AMF provides Access & Mobility Management Function (AMF) for free5GC, an an open-source project for 5th generation (5G) mobile core networks. go · github.com/free5gc/amf 2026-04-22 medium5.8 CVE-2026-40343 free5GC UDR is the user data repository (UDR) for free5GC, an an open-source project for 5th generation (5G) mobile core networks. go · github.com/free5gc/udr 2026-04-21 medium5.3 CVE-2026-40249 free5gc UDR fail-open request handling in PolicyDataSubsToNotifySubsIdPut may allow unintended subscription updates after input errors go · github.com/free5gc/udr 2026-04-14 medium5.3 CVE-2026-5661 A vulnerability was identified in Free5GC 4.2.0. 2026-04-06 medium5.3 CVE-2026-4531 Free5GC AMF is vulnerable to DoS through its HandleRegistrationComplete function go · github.com/free5gc/amf 2026-03-22 medium6.9 CVE-2026-33065 free5GC UDM incorrectly returns 500 for empty supi path parameter in DELETE sdm-subscriptions request go · github.com/free5gc/udm 2026-03-18 medium5.3 CVE-2026-27643 free5GC UDR is the user data repository (UDR) for free5GC, an an open-source project for 5th generation (5G) mobile core networks. free5gc · udr 2026-02-24 medium5.3 CVE-2025-69253 free5GC is an open-source project for 5th generation (5G) mobile core networks. free5gc · udr 2026-02-24 medium5.3 CVE-2025-69251 free5gc UDM provides Unified Data Management (UDM) for free5GC, an open-source project for 5th generation (5G) mobile core networks. free5gc · udm 2026-02-24 medium5.3 CVE-2025-69208 free5GC UDR is the user data repository (UDR) for free5GC, an an open-source project for 5th generation (5G) mobile core networks. free5gc · udr 2026-02-23 medium5.3 CVE-2026-2525 A vulnerability has been found in Free5GC up to 4.1.0. free5gc · free5gc 2026-02-16 medium5.3 CVE-2026-1976 A weakness has been identified in Free5GC up to 4.1.0. free5gc · free5gc 2026-02-06 medium5.3 CVE-2026-1975 A security flaw has been discovered in Free5GC up to 4.1.0. free5gc · free5gc 2026-02-06 medium5.3 CVE-2026-1974 A vulnerability was identified in Free5GC up to 4.1.0. free5gc · free5gc 2026-02-06 medium5.3 CVE-2026-1973 A vulnerability was determined in Free5GC up to 4.1.0. free5gc · free5gc 2026-02-06 medium5.3 CVE-2026-1739 A vulnerability has been found in Free5GC pcf up to 1.4.1. free5gc · pcf 2026-02-02 medium5.3 CVE-2026-1684 A vulnerability was found in Free5GC SMF up to 4.1.0. free5gc · free5gc 2026-01-30 medium5.3 CVE-2026-1683 A vulnerability has been found in Free5GC SMF up to 4.1.0. free5gc · free5gc 2026-01-30 medium5.3 CVE-2026-1682 A flaw has been found in Free5GC SMF up to 4.1.0. free5gc · free5gc 2026-01-30 medium6.5 CVE-2025-60633 An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via the Nudm_SubscriberDataManagement API. go · github.com/free5gc/udm, go · github.com/free5gc/openapi 2025-11-24 medium6.5 CVE-2025-60632 An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via crafted POST request to the Npcf_BDTPolicyControl AP… go · github.com/free5gc/pcf 2025-11-24

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.