NetSight

Security Dashboard

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

Reset
74 matching advisories · page 1 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.3 CVE-2026-46587 Apache Camel-Couchbase: Non-Camel-prefixed Exchange headers bypass HeaderFilterStrategy allowing operation override from untrusted input maven · org.apache.camel:camel-couchbase 2026-07-06 critical GHSA-3xgr-445x-7mm6 Malware in @mastra/couchbaseMalware npm · @mastra/couchbase 2026-06-17 high7.3 GHSA-jfwg-rxf3-p7r9 Authorizer: CQL/N1QL Injection in Cassandra and Couchbase Backends via fmt.Sprintf String Interpolation go · github.com/authorizerdev/authorizer 2026-04-06 high7.3 CVE-2025-52490 Couchbase Sync Gateway shows cleartext passwords in redacted and unredacted output go · github.com/couchbase/sync_gateway 2025-07-29 medium4.9 CVE-2025-49015 Couchbase .NET SDK (client library) does not properly enable hostname verification for TLS certificates nuget · CouchbaseNetClient 2025-06-18 high7.6 CVE-2025-46619 A security issue has been discovered in Couchbase Server before 7.6.4 and fixed in v.7.6.4 and v.7.2.7 for Windows that could allow unauthorized access to sens… couchbase · couchbase_server 2025-04-30 medium6.5 CVE-2024-56178 An issue was discovered in Couchbase Server 7.6.x through 7.6.3. couchbase · couchbase_server 2025-01-27 medium6.1 CVE-2024-25673 Couchbase Server 7.6.x before 7.6.2, 7.2.x before 7.2.6, and all earlier versions allows HTTP Host header injection. couchbase · couchbase_server 2024-09-19 medium5.9 CVE-2024-37034 An issue was discovered in Couchbase Server before 7.2.5 and 7.6.0 before 7.6.1. couchbase · couchbase_server 2024-07-26 high7.5 CVE-2023-43768 An issue was discovered in Couchbase Server 6.6.x through 7.2.0, before 7.1.5 and 7.2.1. couchbase · couchbase_server 2024-03-27 high7.5 CVE-2024-23302 Couchbase Server before 7.2.4 has a private key leak in goxdcr.log. couchbase · couchbase_server 2024-02-29 high8.6 CVE-2023-50437 An issue was discovered in Couchbase Server before 7.2.x before 7.2.4. couchbase · couchbase_server 2024-02-29 medium5.3 CVE-2023-50436 An issue was discovered in Couchbase Server before 7.2.4. couchbase · couchbase_server 2024-02-29 medium5.4 CVE-2023-49932 An issue was discovered in Couchbase Server before 7.2.4. couchbase · couchbase_server 2024-02-29 critical9.8 CVE-2023-49931 An issue was discovered in Couchbase Server before 7.2.4. couchbase · couchbase_server 2024-02-29 critical9.8 CVE-2023-49930 An issue was discovered in Couchbase Server before 7.2.4. couchbase · couchbase_server 2024-02-29 medium4.3 CVE-2023-45874 An issue was discovered in Couchbase Server through 7.2.2. couchbase · couchbase_server 2024-02-29 medium6.3 CVE-2023-43769 An issue was discovered in Couchbase Server through 7.1.4 before 7.1.5 and before 7.2.1. couchbase · couchbase_server 2024-02-29 high7.5 CVE-2023-49338 Couchbase Server 7.1.x and 7.2.x before 7.2.4 does not require authentication for the /admin/stats and /admin/vitals endpoints on TCP port 8093 of localhost. couchbase · couchbase_server 2024-02-28 medium6.5 CVE-2023-45873 An issue was discovered in Couchbase Server through 7.2.2. couchbase · couchbase_server 2024-02-28 high7.5 CVE-2023-50782 Python Cryptography package vulnerable to Bleichenbacher timing oracle attack pip · cryptography 2024-02-05 high8.8 CVE-2024-0519 Google Chromium V8 Out-of-Bounds Memory Access VulnerabilityExploited google · chrome, fedoraproject · fedora, couchbase · couchbase_server 2024-01-16 high7.5 CVE-2023-36667 Couchbase Server 7.1.4 before 7.1.5 and 7.2.0 before 7.2.1 allows Directory Traversal. couchbase · couchbase_server 2023-11-08 high7.5 CVE-2023-45875 An issue was discovered in Couchbase Server 7.2.0. couchbase · couchbase_server 2023-11-08 high8.8 CVE-2023-3079 Google Chromium V8 Type Confusion VulnerabilityExploited google · chrome, fedoraproject · fedora, debian · debian_linux +1 2023-06-05 high8.8 CVE-2023-2033 Google Chromium V8 Type Confusion VulnerabilityExploited google · chrome, debian · debian_linux, fedoraproject · fedora +1 2023-04-14 medium5.3 CVE-2023-28470 In Couchbase Server 5 through 7 before 7.1.4, the nsstats endpoint is accessible without authentication. couchbase · couchbase_server 2023-03-23 high7.5 CVE-2023-25016 Couchbase Server before 6.6.6, 7.x before 7.0.5, and 7.1.x before 7.1.2 exposes Sensitive Information to an Unauthorized Actor. couchbase · couchbase_server 2023-02-06 high8.1 CVE-2022-42951 An issue was discovered in Couchbase Server 6.5.x and 6.6.x before 6.6.6, 7.x before 7.0.5, and 7.1.x before 7.1.2. couchbase · couchbase_server 2023-02-06 medium4.9 CVE-2022-42950 An issue was discovered in Couchbase Server 7.x before 7.0.5 and 7.1.x before 7.1.2. couchbase · couchbase_server 2023-02-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.