Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
RHSA-2026:82895
No affected components available
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
- CVE-2026-86413Upstream
- CVE-2026-87866Upstream
- CVE-2025-9086
1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with only a slash as path (`path="/"`). Since this site is not secure, the cookie *should* be ignored. 4. A bug in the path comparison logic makes curl read outside a heap buffer boundary The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path. The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.
Upstream, EPSS 1.46% - EUVD-2026-105314Upstream
- EUVD-2026-105359Upstream
- EUVD-2026-105355Upstream
- CVE-2026-86414Upstream
- CVE-2026-92386Upstream
- CVE-2026-92391Upstream
- EUVD-2026-105276Upstream
- CVE-2025-14819
When doing TLS related transfers with reused easy or multi handles and altering the `CURLSSLOPT_NO_PARTIALCHAIN` option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.
Upstream, EPSS 0.76% - EUVD-2026-105315Upstream
- CVE-2026-92388Upstream
- EUVD-2026-1581Upstream
- CVE-2026-87862Upstream
- EUVD-2026-105310Upstream
- EUVD-2026-105312Upstream
- EUVD-2026-105318Upstream
- CVE-2026-94265Upstream
- EUVD-2026-105309Upstream
- EUVD-2026-105357Upstream
- CVE-2026-87861Upstream
- CVE-2026-87863Upstream
- CVE-2026-87865Upstream
- EUVD-2026-105277Upstream
- EUVD-2026-105322Upstream
- CVE-2026-92390Upstream
- EUVD-2026-105320Upstream
- EUVD-2026-105306Upstream
- EUVD-2026-105317Upstream
- EUVD-2026-100915Upstream
- CVE-2026-86409Upstream
- EUVD-2026-1566Upstream
- EUVD-2026-105308Upstream
- CVE-2026-87864Upstream
- CVE-2026-92387Upstream
- CVE-2026-94266Upstream
- CVE-2026-86410Upstream
- EUVD-2026-105311Upstream
- CVE-2026-92392Upstream
- CVE-2026-107928Upstream
- CVE-2026-92389Upstream
- CVE-2026-86411Upstream
- CVE-2026-86412Upstream
- EUVD-2026-105319Upstream
- EUVD-2025-29014Upstream
- EUVD-2026-105275Upstream
- EUVD-2026-105279Upstream
- CVE-2026-107929Upstream
- EUVD-2026-105274Upstream
- EUVD-2026-105353Upstream
- CVE-2025-14017
When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.
Upstream, EPSS 0.11%
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard