NetSight

Security Dashboard

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

Reset
89 matching advisories · page 1 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.9 CVE-2025-65081 An out-of-bounds read vulnerability has been identified in the Postscript interpreter in various Lexmark devices. 2026-02-03 medium6.9 CVE-2025-65080 A type confusion vulnerability has been identified in the Postscript interpreter in various Lexmark devices. 2026-02-03 medium6.9 CVE-2025-65079 A heap-based buffer overflow vulnerability has been identified in the Postscript interpreter in various Lexmark devices. 2026-02-03 critical9.3 CVE-2025-65078 An untrusted search path vulnerability has been identified in the Embedded Solutions Framework in various Lexmark devices. 2026-02-03 high8.8 CVE-2025-65077 A relative path traversal vulnerability has been identified in the Embedded Solutions Framework in various Lexmark devices. Lexmark · MXTCT, MSNGM, MSTGM, MXNGM, MXTGM, CSNGV, CSTGV, CXTGV, MSNGW, MSTGW, MXTGW, CSTLS, CXTLS, MXTLS, CSTMM, CXTMM, CSTPC, CXTPC, MXTPM, MSNSN, MSTSN, MXTSN, CSNZJ, CSTZJ, CXNZJ, CXTZJ, Lexmark · CSTAT, CXTAT, MSLBD, MXLBD, CSLBL, CXLBL, CSLBN, CXLBN, CSTMH, CXTMH, CSTPP, CXTPP, MSLSG, MXLSG 2026-02-03 medium6.9 CVE-2025-9269 A Server-Side Request Forgery (SSRF) vulnerability has been identified in the embedded web server in various Lexmark devices. 2025-09-09 high8.5 CVE-2025-4046 A missing authorization vulnerability in Lexmark Cloud Services badge management allows attacker to reassign badges within their organization 2025-08-19 high8.2 CVE-2025-4044 Improper Restriction of XML External Entity Reference in various Lexmark printer drivers for Windows allows attacker to disclose sensitive information to an ar… 2025-08-19 critical9.1 CVE-2020-35546 Lexmark MX6500 LW75.JD.P296 and previous devices have Incorrect Access Control via the access control settings. 2025-02-19 medium6.1 CVE-2020-13481 Certain Lexmark products through 2020-05-25 allow XSS which allows an attacker to obtain session credentials and other sensitive information. 2025-02-19 high8.1 CVE-2020-10095 Various Lexmark devices have CSRF that allows an attacker to modify the configuration of the device. 2025-02-19 high7.3 CVE-2024-11347 Integer Overflow or Wraparound vulnerability in Lexmark International CX, XC, CS, et. 2025-02-13 high7.3 CVE-2024-11346 : Access of Resource Using Incompatible Type ('Type Confusion') vulnerability in Lexmark International CX, XC, CS, et. CX, XC, CS, et. Al.: from 001.001:0 2025-02-13 high7.3 CVE-2024-11345 A heap-based memory vulnerability has been identified in the Postscript interpreter in various Lexmark devices. 2025-02-13 high7.3 CVE-2024-11344 A type confusion vulnerability has been identified in the Postscript interpreter in various Lexmark devices. 2025-02-13 critical9.3 CVE-2025-1126 A Reliance on Untrusted Inputs in a Security Decision vulnerability has been identified in the Lexmark Print Management Client. 2025-02-11 high8.6 CVE-2023-50733 A Server-Side Request Forgery (SSRF) vulnerability has been identified in the Web Services feature of newer Lexmark devices. 2025-01-21 high8.8 CVE-2023-50739 A buffer overflow vulnerability has been identified in the Internet Printing Protocol (IPP) in various Lexmark devices. 2025-01-18 medium4.3 CVE-2023-50738 A new feature to prevent Firmware downgrades was recently added to some Lexmark products. 2025-01-17 critical9.1 CVE-2023-50737 The SE menu contains information used by Lexmark to diagnose device errors. 2024-02-28 critical9.0 CVE-2023-50736 A memory corruption vulnerability has been identified in PostScript interpreter in various Lexmark devices. 2024-02-28 critical9.0 CVE-2023-50735 A heap corruption vulnerability has been identified in PostScript interpreter in various Lexmark devices. 2024-02-28 critical9.0 CVE-2023-50734 A buffer overflow vulnerability has been identified in PostScript interpreter in various Lexmark devices. 2024-02-28 high7.5 CVE-2023-40239 Certain Lexmark devices (such as CS310) before 2023-08-25 allow XXE attacks, leading to information disclosure. lexmark · c2132_firmware, lexmark · cs310_firmware, lexmark · cs317_firmware +9 2023-09-01 critical9.8 CVE-2023-26070 Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 4 of 4). lexmark · cxtpc_firmware, lexmark · cstpc_firmware, lexmark · mxtct_firmware +9 2023-04-10 critical9.8 CVE-2023-26069 Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 3 of 4). lexmark · cxtpc_firmware, lexmark · cstpc_firmware, lexmark · mxtct_firmware +9 2023-04-10 critical9.8 CVE-2023-26068 Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 2 of 4). lexmark · cxtpc_firmware, lexmark · cstpc_firmware, lexmark · mxtct_firmware +9 2023-04-10 high8.1 CVE-2023-26067 Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 1 of 4). lexmark · cxtpc_firmware, lexmark · cstpc_firmware, lexmark · mxtct_firmware +9 2023-04-10 critical9.8 CVE-2023-26066 Certain Lexmark devices through 2023-02-19 have Improper Validation of an Array Index. lexmark · cxtpc_firmware, lexmark · cstpc_firmware, lexmark · mxtct_firmware +9 2023-04-10 critical9.8 CVE-2023-26065 Certain Lexmark devices through 2023-02-19 have an Integer Overflow. lexmark · cxtpc_firmware, lexmark · cstpc_firmware, lexmark · mxtct_firmware +9 2023-04-10

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.