NetSight

Security Dashboard

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

Reset
50 matching advisories · page 2 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-hc4g-m39w-r595 Malicious code in able_squid_z3n (npm)Malware npm · able_squid_z3n 2026-08-31 critical9.1 CVE-2026-24736 Squidex is an open source headless content management system and content management hub. squidex.io · squidex 2026-01-27 critical GHSA-v8qf-r8wm-683x Malware in grumpy-squidwardMalware npm · grumpy-squidward 2025-11-11 critical10.0 CVE-2025-62168 Squid is a caching proxy for the Web. squid-cache · squid 2025-10-17 critical9.3 CVE-2025-54574 Squid is a caching proxy for the Web. squid-cache · squid 2025-08-01 critical9.1 CVE-2023-46253 Squidex is an open source headless CMS and content management hub. squidex.io · squidex 2023-11-07 critical9.3 CVE-2023-46846 SQUID is vulnerable to HTTP request smuggling, caused by chunked decoder lenience, allows a remote attacker to perform Request/Response smuggling past firewall… squid-cache · squid, redhat · enterprise_linux, redhat · enterprise_linux_eus +17 2023-11-03 critical9.9 CVE-2020-15049 An issue was discovered in http/ContentLengthInterpreter.cc in Squid before 4.12 and 5.x before 5.0.3. squid-cache · squid, fedoraproject · fedora 2020-06-30 critical9.8 CVE-2020-11945 An issue was discovered in Squid before 5.0.2. squid-cache · squid, debian · debian_linux, opensuse · leap +2 2020-04-23 critical9.8 CVE-2019-12519 An issue was discovered in Squid through 4.7. squid-cache · squid, debian · debian_linux, canonical · ubuntu_linux +1 2020-04-15 critical9.8 CVE-2019-12524 An issue was discovered in Squid through 4.7. squid-cache · squid, debian · debian_linux, canonical · ubuntu_linux 2020-04-15 critical9.8 CVE-2019-12526 An issue was discovered in Squid before 4.9. squid-cache · squid, canonical · ubuntu_linux, fedoraproject · fedora +2 2019-11-26 critical9.1 CVE-2019-12523 An issue was discovered in Squid before 4.9. squid-cache · squid, canonical · ubuntu_linux, fedoraproject · fedora +2 2019-11-26 critical9.8 CVE-2019-12525 An issue was discovered in Squid 3.3.9 through 3.5.28 and 4.x through 4.7. squid-cache · squid, debian · debian_linux, opensuse · leap +2 2019-07-11 critical9.8 CVE-2016-5408 Stack-based buffer overflow in the munge_other_line function in cachemgr.cgi in the squid package before 3.1.23-16.el6_8.6 in Red Hat Enterprise Linux 6 allows… oracle · linux, redhat · enterprise_linux_server, redhat · enterprise_linux_workstation 2016-08-10 critical9.3 CVE-2008-7249 Buffer overflow in Squid Analysis Report Generator (Sarg) 2.2.3.1, and probably later, allows user-assisted remote attackers to execute arbitrary code via a lo… pedro_lineu_orso · sarg 2009-12-30 critical10.0 CVE-2008-1922 Multiple stack-based buffer overflows in Sarg might allow attackers to execute arbitrary code via unknown vectors, probably a crafted Squid log file. sarg · squid_analysis_report_generator 2008-05-13 critical10.0 CVE-2008-1167 Stack-based buffer overflow in the useragent function in useragent.c in Squid Analysis Report Generator (Sarg) 2.2.3.1 allows remote attackers to execute arbit… sarg · squid_analysis_report_generator 2008-03-05 critical10.0 CVE-2005-0194 Squid 2.5, when processing the configuration file, parses empty Access Control Lists (ACLs), including proxy_auth ACLs without defined auth schemes, in a way t… squid · squid 2005-05-02 critical10.0 CVE-2004-0541 Buffer overflow in the ntlm_check_auth (NTLM authentication) function for Squid Web Proxy Cache 2.5.x and 3.x, when compiled with NTLM handlers enabled, allows… national_science_foundation · squid_web_proxy_cache 2004-08-06

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.