Understand vulnerabilities. Protect your applications.
Discover which vulnerabilities affect your technologies and how to fix them. Explore clear explanations, affected versions and practical recommendations - from CMS platforms and plugins to application libraries.
Vulnerability archive 31
Reset filterscertifi bundles emSign root CAs with compromised intermediate CA keys
Certain certifi releases bundled a root certificate with compromised intermediate keys. An attacker on the network path could issue forged certificates for any hostname and intercept or modify TLS connections.
Apprise forwards configured auth headers across cross-origin HTTP redirects
Apprise HTTP notification plugins and loaders follow redirects by default while re-sending configured authentication headers. If a configured destination is compromised or subjected to a man-in-the-middle attack, secrets can be leaked to an arbitrary cross-origin host.
Docling has SSRF guard bypass in remote resource fetching (DNS rebinding / multi-record resolution; no IP validation in HTML render mode)
urllib3: Chunked Deflate streaming can enter an infinite loop
urllib3: HTTPResponse.stream()/read_chunked() buffers an unbounded chunk-size line into memory
urllib3: HTTPS proxy TLS configuration may be ignored or overridden
local-deep-research has an SSRF bypass in `safe_get`
Bunsink has an SSRF bypass in `validate_webhook_url`
vLLM has SSRF Protection Bypass
vLLM vulnerable to Server-Side Request Forgery (SSRF) through MediaConnector
Decompression-bomb safeguards bypassed when following HTTP redirects (streaming API)
urllib3 streaming API improperly handles highly compressed data
urllib3 allows an unbounded number of links in the decompression chain
urllib3 does not control redirects in browsers and Node.js
urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation
urllib3's Proxy-Authorization request header isn't stripped during cross-origin redirects
urllib3: Decompression-bomb safeguards bypassed in parts of the streaming API
urllib3: Sensitive headers forwarded across origins in proxied low-level redirects
urllib3's request body not stripped after redirect from 303 status changes request method to GET
urllib3 before 1.24.2 does not remove the authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in t
`Cookie` HTTP header isn't stripped on cross-origin redirects
Unintended leak of Proxy-Authorization header in requests
Versions 1.17 and 1.18 of the Python urllib3 library suffer from a vulnerability that can cause them, in certain configurations, to not correctly validate TLS certificates. This places users of the li
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.