NetSight

Security Dashboard

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

Reset
17 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.2 CVE-2026-5857 Contiki-NG's MQTT client parse_publish_vhdr() in os/net/app-layer/mqtt/mqtt.c sets topic_len_received=1 before checking topic_len against the 64-byte limit, so… contiki-ng · contiki-ng 2026-08-06 critical9.1 CVE-2021-42147 Buffer over-read vulnerability in the dtls_sha256_update function in Contiki-NG tinyDTLS through master branch 53a0d97 allows remote attackers to cause a denia… contiki-ng · tinydtls 2024-01-24 critical9.8 CVE-2021-42144 Buffer over-read vulnerability in Contiki-NG tinyDTLS through master branch 53a0d97 allows attackers obtain sensitive information via crafted input to dtls_ccm… contiki-ng · contiki-ng_tinydtls 2024-01-24 critical9.1 CVE-2021-42143 An issue was discovered in Contiki-NG tinyDTLS through master branch 53a0d97. contiki-ng · tinydtls 2024-01-24 critical9.8 CVE-2021-42142 An issue was discovered in Contiki-NG tinyDTLS through master branch 53a0d97. contiki-ng · tinydtls 2024-01-23 critical9.8 CVE-2021-42141 An issue was discovered in Contiki-NG tinyDTLS through 2018-08-30. contiki-ng · tinydtls 2024-01-22 critical9.1 CVE-2020-27634 In Contiki 4.5, TCP ISNs are improperly random. contiki-ng · contiki-ng 2023-10-10 critical9.8 CVE-2023-30546 Contiki-NG is an operating system for Internet of Things devices. contiki-ng · contiki-ng 2023-04-26 critical9.1 CVE-2020-12141 An out-of-bounds read in the SNMP stack in Contiki-NG 4.4 and earlier allows an attacker to cause a denial of service and potentially disclose information via … contiki-ng · contiki-ng 2021-10-19 critical9.8 CVE-2020-24336 An issue was discovered in Contiki through 3.0 and Contiki-NG through 4.5. contiki-ng · contiki-ng, contiki-os · contiki 2020-12-11 critical9.8 CVE-2020-14936 Buffer overflows were discovered in Contiki-NG 4.4 through 4.5, in the SNMP agent. contiki-ng · contiki-ng 2020-08-18 critical9.8 CVE-2020-14935 Buffer overflows were discovered in Contiki-NG 4.4 through 4.5, in the SNMP bulk get request response encoding function. contiki-ng · contiki-ng 2020-08-18 critical9.8 CVE-2020-14934 Buffer overflows were discovered in Contiki-NG 4.4 through 4.5, in the SNMP agent. contiki-ng · contiki-ng 2020-08-18 critical9.1 CVE-2020-14937 Memory access out of buffer boundaries issues was discovered in Contiki-NG 4.4 through 4.5, in the SNMP BER encoder/decoder. contiki-ng · contiki-ng 2020-08-18 critical9.8 CVE-2019-8359 An issue was discovered in Contiki-NG through 4.3 and Contiki through 3.0. contiki-ng · contiki-ng, contiki-os · contiki 2020-04-23 critical10.0 CVE-2018-19417 An issue was discovered in the MQTT server in Contiki-NG before 4.2. contiki-ng · contiki-ng 2018-11-21 critical9.8 CVE-2018-1000804 contiki-ng version 4 contains a Buffer Overflow vulnerability in AQL (Antelope Query Language) database engine that can result in Attacker can perform Remote C… contiki-ng · contiki-ng 2018-10-08

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.