32247 matches found
CVE-2026-85217
A maliciously crafted add-in, when installed and executed in Autodesk Fusion Desktop, can modify persistent network proxy settings without user notification or consent. A successful exploit may allow an attacker to redirect authenticated Fusion network traffic through an attacker-controlled proxy...
CVE-2026-85217
Autodesk Fusion Desktop is vulnerable to a Man-in-the-Middle (MITM) attack via a maliciously crafted add-in that, when installed and executed, can modify persistent network proxy settings without user notification or consent. A successful exploit allows an attacker to redirect authenticated Fusio...
CVE-2026-85217 Man-in-the-Middle (MITM) Vulnerability in Autodesk Fusion Desktop
A maliciously crafted add-in, when installed and executed in Autodesk Fusion Desktop, can modify persistent network proxy settings without user notification or consent. A successful exploit may allow an attacker to redirect authenticated Fusion network traffic through an attacker-controlled proxy...
EUVD-2026-75449
A maliciously crafted add-in, when installed and executed in Autodesk Fusion Desktop, can modify persistent network proxy settings without user notification or consent. A successful exploit may allow an attacker to redirect authenticated Fusion network traffic through an attacker-controlled proxy...
CVE-2026-85217 Man-in-the-Middle (MITM) Vulnerability in Autodesk Fusion Desktop
A maliciously crafted add-in, when installed and executed in Autodesk Fusion Desktop, can modify persistent network proxy settings without user notification or consent. A successful exploit may allow an attacker to redirect authenticated Fusion network traffic through an attacker-controlled proxy...
CVE-2026-88879 Traefik before v2.11.56 Identity Spoofing via Header Alias
Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, XAuthUser and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable...
CVE-2026-88879
Traefik (HTTP reverse proxy and load balancer) is vulnerable to identity spoofing via dot-form header aliasing in versions v1.x, v2.x–v2.11.55, and v3.0.0–v3.7.11. Because Go canonicalizes header names on dashes only, a client can send a dot-form alias (e.g., X.Authenticated.User) alongside the c...
CVE-2026-88879 Traefik before v2.11.56 Identity Spoofing via Header Alias
Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, XAuthUser and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable...
CVE-2026-88879
Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, XAuthUser and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable...
CVE-2026-88877 Traefik v3.7.0 Authentication Bypass via from-to-www-redirect
Traefik is a HTTP reverse proxy and load balancer. In versions = v3.7.0 and = v3.7.11, the Kubernetes ingress-nginx provider mishandles Ingresses that carry both an authentication annotation and the nginx.ingress.kubernetes.io/from-to-www-redirect annotation. For such Ingresses the provider creat...
ROOT-APP-NPM-CVE-2024-21536 CVE-2024-21536 in http-proxy-middleware - Patched by Root
Root has patched CVE-2024-21536 in the http-proxy-middleware package for Root:npm. Multiple fixed versions available...
Malicious code in eta-proxy-omicron-theta-sanitize (npm)
Source: amazon-inspector 236c542af2b6ed42542ff27935ed3593b1509125430b4348128a798de5c9fe1d This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in epic-http-proxy (npm)
Source: amazon-inspector 863036bf2f0ff62d106f010a0cc099bd3c46d4e9523731ae59449678897ee556 The package epic-http-proxy was found to contain malicious code. --- Credit: OpenSSF source...
Malicious code in enum-proxy-sun-omicron-nu (npm)
Source: amazon-inspector 0f1ce60002a208a96e55d2294bff4e57212734d00871e99d52812712e529377e This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
Malicious code in enum-compress-proxy-thread-user (npm)
Source: amazon-inspector c95ef3cbb61db1cbeab2893204a04eaefaa1591655f7dcd34ecb4c43b883a579 This package appears to be part of the tea.xyz token reward campaign that flooded npm. These packages typically contain autopublish scripts auto.js, autopublish.js, autopublish2.js, autopublish3.js designed ...
PYSEC-2026-3844 HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies
Summary httpcore2 does not start TLS for wss:// connections routed through a SOCKS5 proxy. The WebSocket opening handshake and all subsequent frames are sent in plaintext through the proxy path, despite the caller selecting the secure wss scheme. The transport flaw affects httpcore2 releases befo...
PYSEC-2026-3845 HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies
Summary httpcore2 does not start TLS for wss:// connections routed through a SOCKS5 proxy. The WebSocket opening handshake and all subsequent frames are sent in plaintext through the proxy path, despite the caller selecting the secure wss scheme. The transport flaw affects httpcore2 releases befo...
HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies
Summaryhttpcore2 does not start TLS for wss:// connections routed through a SOCKS5 proxy. The WebSocket opening handshake and all subsequent frames are sent in plaintext through the proxy path, despite the caller selecting the secure wss scheme.The transport flaw affects httpcore2 releases before...
HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies
Summaryhttpcore2 does not start TLS for wss:// connections routed through a SOCKS5 proxy. The WebSocket opening handshake and all subsequent frames are sent in plaintext through the proxy path, despite the caller selecting the secure wss scheme.The transport flaw affects httpcore2 releases before...
