NetSight

Security Dashboard

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

Reset
83 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2026-6192 A vulnerability was identified in uclouvain openjpeg up to 2.5.4. uclouvain openjpeg 2026-04-13 medium6.5 CVE-2025-50952 openjpeg v 2.5.0 was discovered to contain a NULL pointer dereference via the component /openjp2/dwt.c. uclouvain · openjpeg 2025-08-07 critical9.8 CVE-2025-54874 OpenJPEG is an open-source JPEG 2000 codec. uclouvain · openjpeg 2025-08-05 medium6.5 CVE-2023-39329 A flaw was found in OpenJPEG. uclouvain · openjpeg, Red Hat · Red Hat AI Inference Server 3.2 2024-07-13 medium4.3 CVE-2023-39327 A flaw was found in OpenJPEG. uclouvain · openjpeg, Red Hat · Red Hat AI Inference Server 3.2 2024-07-13 medium5.5 CVE-2023-39328 A vulnerability was found in OpenJPEG similar to CVE-2019-6988. uclouvain · openjpeg 2024-07-09 medium5.5 CVE-2022-1122 A flaw was found in the opj2_decompress program in openjpeg2 2.4.0 in the way it handles an input directory with a large number of files. uclouvain · openjpeg, fedoraproject · fedora, debian · debian_linux 2022-03-29 high7.8 CVE-2021-3575 A heap-based buffer overflow was found in openjpeg in color.c:379:42 in sycc420_to_rgb when decompressing a crafted .j2k file. uclouvain · openjpeg, redhat · enterprise_linux, fedoraproject · fedora 2022-03-04 high7.8 CVE-2020-27823 A flaw was found in OpenJPEG’s encoder. uclouvain · openjpeg, fedoraproject · fedora, debian · debian_linux 2021-05-13 medium5.5 CVE-2020-27824 A flaw was found in OpenJPEG’s encoder in the opj_dwt_calc_explicit_stepsizes() function. uclouvain · openjpeg, redhat · enterprise_linux, fedoraproject · fedora +1 2021-05-13 medium5.5 CVE-2021-29338 Integer Overflow in OpenJPEG v2.4.0 allows remote attackers to crash the application, causing a Denial of Service (DoS). uclouvain · openjpeg, fedoraproject · fedora, debian · debian_linux 2021-04-14 high7.8 CVE-2020-27814 A heap-buffer overflow was found in the way openjpeg2 handled certain PNG format files. uclouvain · openjpeg, debian · debian_linux 2021-01-26 medium5.5 CVE-2020-27845 There's a flaw in src/lib/openjp2/pi.c of openjpeg in versions prior to 2.4.0. uclouvain · openjpeg, fedoraproject · fedora, debian · debian_linux +1 2021-01-05 high7.8 CVE-2020-27844 A flaw was found in openjpeg's src/lib/openjp2/t2.c in versions prior to 2.4.0. uclouvain · openjpeg, debian · debian_linux, oracle · outside_in_technology 2021-01-05 medium5.5 CVE-2020-27843 A flaw was found in OpenJPEG in versions prior to 2.4.0. uclouvain · openjpeg, fedoraproject · fedora, oracle · outside_in_technology +1 2021-01-05 medium5.5 CVE-2020-27842 There's a flaw in openjpeg's t2 encoder in versions prior to 2.4.0. uclouvain · openjpeg, fedoraproject · extra_packages_for_enterprise_linux, fedoraproject · fedora +8 2021-01-05 medium5.5 CVE-2020-27841 There's a flaw in openjpeg in versions prior to 2.4.0 in src/lib/openjp2/pi.c. uclouvain · openjpeg, fedoraproject · fedora, debian · debian_linux +1 2021-01-05 medium6.5 CVE-2020-15389 jp2/opj_decompress.c in OpenJPEG through 2.3.1 has a use-after-free that can be triggered if there is a mix of valid and invalid files in a directory operated … uclouvain · openjpeg, debian · debian_linux, oracle · outside_in_technology 2020-06-29 medium5.5 CVE-2016-3182 The color_esycc_to_rgb function in bin/common/color.c in OpenJPEG before 2.1.1 allows attackers to cause a denial of service (memory corruption) via a crafted … uclouvain · openjpeg 2020-02-20 high8.8 CVE-2020-8112 opj_t1_clbl_decode_processor in openjp2/t1.c in OpenJPEG 2.3.1 through 2020-01-28 has a heap-based buffer overflow in the qmfbid==1 case, a different issue tha… uclouvain · openjpeg, debian · debian_linux 2020-01-28 high7.5 CVE-2020-6851 OpenJPEG through 2.3.1 has a heap-based buffer overflow in opj_t1_clbl_decode_processor in openjp2/t1.c because of lack of opj_j2k_update_image_dimensions vali… uclouvain · openjpeg, fedoraproject · fedora, debian · debian_linux +9 2020-01-13 high8.8 CVE-2018-21010 OpenJPEG before 2.3.1 has a heap buffer overflow in color_apply_icc_profile in bin/common/color.c. uclouvain · openjpeg, debian · debian_linux 2019-09-05 medium5.5 CVE-2019-12973 In OpenJPEG 2.3.1, there is excessive iteration in the opj_t1_encode_cblks function of openjp2/t1.c. uclouvain · openjpeg, opensuse · leap, debian · debian_linux +2 2019-06-26 high8.8 CVE-2018-20847 An improper computation of p_tx0, p_tx1, p_ty0 and p_ty1 in the function opj_get_encoding_parameters in openjp2/pi.c in OpenJPEG through 2.3.0 can lead to an i… uclouvain · openjpeg, debian · debian_linux 2019-06-26 medium6.5 CVE-2018-20846 Out-of-bounds accesses in the functions pi_next_lrcp, pi_next_rlcp, pi_next_rpcl, pi_next_pcrl, pi_next_rpcl, and pi_next_cprl in openmj2/pi.c in OpenJPEG thro… uclouvain · openjpeg 2019-06-26 medium6.5 CVE-2018-20845 Division-by-zero vulnerabilities in the functions pi_next_pcrl, pi_next_cprl, and pi_next_rpcl in openmj2/pi.c in OpenJPEG through 2.3.0 allow remote attackers… uclouvain · openjpeg 2019-06-26 medium6.5 CVE-2019-6988 An issue was discovered in OpenJPEG 2.3.0. uclouvain · openjpeg 2019-01-28 medium6.5 CVE-2018-18088 OpenJPEG 2.3.0 has a NULL pointer dereference for "red" in the imagetopnm function of jp2/convert.c uclouvain · openjpeg, debian · debian_linux 2018-10-09 high8.8 CVE-2018-16376 An issue was discovered in OpenJPEG 2.3.0. uclouvain · openjpeg 2018-09-03 high8.8 CVE-2018-16375 An issue was discovered in OpenJPEG 2.3.0. uclouvain · openjpeg 2018-09-03

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.