NetSight

Security Dashboard

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

Reset
19 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.6 CVE-2025-66606 A vulnerability has been found in FAST/TOOLS provided by Yokogawa Electric Corporation. yokogawa · fast\/tools 2026-02-09 critical9.8 CVE-2025-66603 A vulnerability has been found in FAST/TOOLS provided by Yokogawa Electric Corporation. yokogawa · fast\/tools 2026-02-09 critical9.8 CVE-2025-66602 A vulnerability has been found in FAST/TOOLS provided by Yokogawa Electric Corporation. yokogawa · fast\/tools 2026-02-09 critical9.8 CVE-2025-1863 Insecure default settings have been found in recorder products provided by Yokogawa Electric Corporation. 2025-04-18 critical9.8 CVE-2022-40984 Stack-based buffer overflow in WTViewerE series WTViewerE 761941 from 1.31 to 1.61 and WTViewerEfree from 1.01 to 1.52 allows an attacker to cause the product … yokogawa · wtviewere_761941, yokogawa · wtviewerefree 2022-10-24 critical9.1 CVE-2022-26034 Improper authentication vulnerability in the communication protocol provided by AD (Automation Design) server of CENTUM VP R6.01.10 to R6.09.00, CENTUM VP Smal… yokogawa · b\/m9000_vp, yokogawa · centum_vp 2022-04-15 critical9.8 CVE-2022-23402 The following Yokogawa Electric products hard-code the password for CAMS server applications: CENTUM VP versions from R5.01.00 to R5.04.20 and versions from R6… yokogawa · centum_vp_firmware, yokogawa · centum_vp_entry_firmware, yokogawa · exaopc 2022-03-11 critical9.8 CVE-2022-21194 The following Yokogawa Electric products do not change the passwords of the internal Windows accounts from the initial configuration: CENTUM VP versions from R… yokogawa · centum_vp_firmware, yokogawa · centum_vp_entry_firmware, yokogawa · exaopc 2022-03-11 critical9.8 CVE-2020-5609 Directory traversal vulnerability in CAMS for HIS CENTUM CS 3000 (includes CENTUM CS 3000 Small) R3.08.10 to R3.09.50, CENTUM VP (includes CENTUM VP Small, Bas… yokogawa · centum_cs_3000_firmware, yokogawa · centum_vp_firmware, yokogawa · b\/m9000cs_firmware +1 2020-08-05 critical9.8 CVE-2020-5608 CAMS for HIS CENTUM CS 3000 (includes CENTUM CS 3000 Small) R3.08.10 to R3.09.50, CENTUM VP (includes CENTUM VP Small, Basic) R4.01.00 to R6.07.00, B/M9000CS R… yokogawa · centum_cs_3000_firmware, yokogawa · centum_vp_firmware, yokogawa · b\/m9000cs_firmware +1 2020-08-05 critical9.8 CVE-2015-5628 Stack-based buffer overflow in Yokogawa CENTUM CS 1000 R3.08.70 and earlier, CENTUM CS 3000 R3.09.50 and earlier, CENTUM CS 3000 Entry R3.09.50 and earlier, CE… yokogawa · centum_cs_1000_firmware, yokogawa · centum_cs_3000_firmware, yokogawa · centum_cs_3000_entry_firmware +9 2020-02-05 critical9.8 CVE-2015-5627 Stack-based buffer overflow in Yokogawa CENTUM CS 1000 R3.08.70 and earlier, CENTUM CS 3000 R3.09.50 and earlier, CENTUM CS 3000 Entry R3.09.50 and earlier, CE… yokogawa · centum_cs_1000_firmware, yokogawa · centum_cs_3000_firmware, yokogawa · centum_cs_3000_entry_firmware +9 2020-02-05 critical9.8 CVE-2015-5626 Stack-based buffer overflow in Yokogawa CENTUM CS 1000 R3.08.70 and earlier, CENTUM CS 3000 R3.09.50 and earlier, CENTUM CS 3000 Entry R3.09.50 and earlier, CE… yokogawa · centum_cs_1000_firmware, yokogawa · centum_cs_3000_firmware, yokogawa · centum_cs_3000_entry_firmware +9 2020-02-05 critical9.8 CVE-2019-5909 License Manager Service of YOKOGAWA products (CENTUM VP (R5.01.00 - R6.06.00), CENTUM VP Entry Class (R5.01.00 - R6.06.00), ProSafe-RS (R3.01.00 - R4.04.00), P… yokogawa · b\/m_9000_vp, yokogawa · centum_vp, yokogawa · prm +1 2019-02-13 critical9.8 CVE-2018-0651 Buffer overflow in the license management function of YOKOGAWA products (iDefine for ProSafe-RS R1.16.3 and earlier, STARDOM VDS R7.50 and earlier, STARDOM FCN… yokogawa · idefine_for_prosafe-rs_firmware, yokogawa · stardom_versatile_data_server_firmware, yokogawa · stardom_fcn\/fcj_simulator_firmware +2 2019-01-09 critical9.8 CVE-2018-17900 Yokogawa STARDOM Controllers FCJ, FCN-100, FCN-RTU, FCN-500, All versions R4.10 and prior, The web application improperly protects credentials which could allo… yokogawa · fcj_firmware, yokogawa · fcn-100_firmware, yokogawa · fcn-rtu_firmware +1 2018-10-12 critical9.8 CVE-2018-10592 Yokogawa STARDOM FCJ controllers R4.02 and prior, FCN-100 controllers R4.02 and prior, FCN-RTU controllers R4.02 and prior, and FCN-500 controllers R4.02 and p… yokogawa · fcj_firmware, yokogawa · fcn-100_firmware, yokogawa · fcn-rtu_firmware +1 2018-07-31 critical9.0 CVE-2014-0783 Stack-based buffer overflow in BKHOdeq.exe in Yokogawa CENTUM CS 3000 R3.09.50 and earlier allows remote attackers to execute arbitrary code via a crafted TCP … yokogawa · centum_cs_3000 2014-03-14 critical9.3 CVE-2014-0781 Heap-based buffer overflow in BKCLogSvr.exe in Yokogawa CENTUM CS 3000 R3.09.50 and earlier allows remote attackers to execute arbitrary code via crafted UDP p… yokogawa · centum_cs_3000 2014-03-14

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.