NetSight

Security Dashboard

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

Reset
105 matching advisories · page 2 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2026-71327 Traefik: Gateway API route identity collision allows cross-namespace backend hijacking go · github.com/traefik/traefik/v3 2026-08-06 low3.8 CVE-2026-71326 Traefik: BasicAuth singleflight key collision allows authenticated identity spoofing go · github.com/traefik/traefik/v3 2026-08-06 critical9.1 CVE-2026-71324 Traefik: Cross-user response poisoning via proxied CONNECT on Traefik's shared backend keep-alive pool go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik 2026-08-06 high7.8 GHSA-7qf5-7ppr-87v8 Duplicate Advisory: Kubernetes Ingress NGINX RewriteTarget Path Traversal Allows Route-Level Authentication Bypass go · github.com/traefik/traefik/v3 2026-08-01 high7.5 CVE-2026-67309 Traefik versions >= v3.7.0 and <= v3.7.7 contain a path traversal vulnerability in the Kubernetes Ingress NGINX provider's RewriteTarget middleware (generated … go · github.com/traefik/traefik/v3 2026-08-01 high7.8 GHSA-rhg6-2vjh-j5qc Duplicate Advisory: Traefik: Authentication Bypass via Path Traversal in ReplacePathRegex Middleware go · github.com/traefik/traefik/v2 2026-07-22 medium5.3 GHSA-7m3p-wc52-rmc6 Duplicate Advisory: Traefik CRD IngressRouteTCP ServersTransport Cross-Provider Namespace Bypass go · github.com/traefik/traefik 2026-07-22 medium5.3 GHSA-6mxq-jr92-3h2r Duplicate Advisory: Traefik Gateway API HTTPRoute BackendRef ExtensionRef Namespace Confusion go · github.com/traefik/traefik 2026-07-22 high8.8 CVE-2026-65602 Traefik 3.6.0 through 3.6.22 and 3.7.0 through 3.7.6 fail to enforce the crossProviderNamespaces allowlist for IngressRouteTCP service serversTransport referen… go · github.com/traefik/traefik/v3 2026-07-22 high8.8 CVE-2026-65601 Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. go · Traefik 2026-07-22 critical9.1 CVE-2026-65600 Traefik versions <= v2.11.51, >= v3.6.0 <= v3.6.22, and >= v3.7.0 <= v3.7.6 contain an authentication bypass via path traversal in the ReplacePathRegex middlew… go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik 2026-07-22 high8.5 CVE-2026-54765 Traefik: Gateway HTTPRoute backendRef filters can leak backend context across routes sharing a Service:port go · github.com/traefik/traefik/v3 2026-07-06 medium5.8 CVE-2026-54764 Traefik: ForwardAuth middleware leaks X-Forwarded-Port spoofing via untrusted X-Forwarded-Proto when trustForwardHeader=false go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik 2026-07-06 critical10.0 CVE-2026-54763 Traefik: Incomplete fix for CVE-2026-33433 + CVE-2026-39858 cross-cohort: headerField underscore-variant identity spoofing in BasicAuth / DigestAuth / ForwardAuth go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3 2026-07-06 high7.5 GHSA-pvrg-q6jw-42p7 Duplicate Advisory: Traefik vulnerable to HTTP/2 request causing denial of service go · github.com/traefik/traefik 2026-06-23 high8.6 CVE-2026-54762 Traefik Kubernetes Ingress NGINX provider fails open when auth-secret resolution fails go · github.com/traefik/traefik/v3 2026-06-19 high7.1 CVE-2026-54761 Traefik: Kubernetes Gateway crossProviderNamespaces bypass allows HTTPRoute outside the allowlist to expose internal Traefik services go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik 2026-06-17 critical10.0 CVE-2026-53622 Traefik: HTTP/3 mTLS bypass via exact SNI TLSOptions lookup for wildcard and mixed-case hosts go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik, go · github.com/traefik/traefik/v3 2026-06-16 critical10.0 CVE-2026-48491 Traefik: SNICheck ignores wildcard TLSOptions mappings, allowing domain-fronted mTLS bypass go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3 2026-06-16 critical10.0 CVE-2026-48020 Traefik has a StripPrefix Route-Level Auth Bypass via Path Normalization go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3 2026-06-11 critical9.9 CVE-2026-44774 Traefik: Gateway API TraefikService backend accepts rest@internal, allowing unauthorized exposure of the REST provider despite providers.rest.insecure=false go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik 2026-05-13 medium5.8 CVE-2026-41181 Traefik's errors middleware forwards Authorization and Cookie headers to separate error page service go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3 2026-05-04 medium3.7 CVE-2026-41263 Traefik: A timing side-channel vulnerability allows for valid username enumeration via BasicAuth middleware go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik 2026-04-24 medium6.4 CVE-2026-41174 Traefik Kubernetes CRD allows unauthorized cross-namespace middleware binding go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik 2026-04-24 high8.2 CVE-2026-40912 Traefik has an StripPrefixRegex Middleware Authorization Bypass via Path/RawPath Desync go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik 2026-04-24 critical10.0 CVE-2026-39858 Traefik: Pre-authentication decision bypass due to forwarded alias spoofing go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik 2026-04-24 critical10.0 CVE-2026-35051 Traefik's ForwardAuth trustForwardHeader=false allows spoofed X-Forwarded-Prefix to bypass authentication go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik 2026-04-24 medium6.1 CVE-2026-34206 Captcha Protect is a Traefik middleware to add an anti-bot challenge to individual IPs in a subnet when traffic spikes are detected from that subnet. libops · captcha_protect 2026-03-31 high7.8 GHSA-46wh-3698-f2cx Traefik: Deny Rule Bypass via Unauthenticated Malicious gRPC Requests in gRPC-Go Dependency (CVE-2026-33186) go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3, go · github.com/traefik/traefik/v3 2026-03-29 high8.8 CVE-2026-33433 Traefik Vulnerable to BasicAuth/DigestAuth Identity Spoofing via Non-Canonical headerField go · github.com/traefik/traefik/v2, go · github.com/traefik/traefik/v3 2026-03-27

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.