CVE-2026-111063

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the Secure attribute for a shared cookie is not enforced. An attacker can consequently cause a shared cookie marked Secure to be sent with an unencrypted request. This issue is fixed in version 3.14.4...

PT-2026-117498

Name of the Vulnerable Software and Affected Versions AIOHTTP versions prior to 3.14.4 Description The Secure attribute for a shared cookie is not enforced. This allows an attacker to cause a shared cookie marked Secure to be sent via an unencrypted request. Recommendations Update to version 3.14...

PT-2026-108705

Name of the Vulnerable Software and Affected Versions AsyncHttpClient versions 2.1.0 through 2.16.1 AsyncHttpClient versions 3.0.0 through 3.0.13 Description The ThreadSafeCookieStore in the AsyncHttpClient library fails to track whether a Set-Cookie response was received via a secure transport...

Security Bulletin: IBM Cyber Fraud includes components with multiple known vulnerabilities

Summary IBM Cyber Fraud includes components with known vulnerabilities. These have been addressed in release 1.1.0. Vulnerability Details CVEID:CVE-2026-9825 DESCRIPTION: IBM Cyberfraud has a missing secure attribute allowing sensitive cookies to be transmitted over unencrypted connections,...

CVE-2026-66249

iControl is affected by a Missing Secure Attribute vulnerability, which could allow an attacker to intercept cookies transmitted over unencrypted HTTP connections, enabling the unauthorized extraction of sensitive information such as session identifiers...

EUVD-2026-90816

iControl is affected by a Missing Secure Attribute vulnerability, which could allow an attacker to intercept cookies transmitted over unencrypted HTTP connections, enabling the unauthorized extraction of sensitive information such as session identifiers...

CVE-2026-66249 HCL iControl is affected by a Missing Secure Attribute vulnerability

iControl is affected by a Missing Secure Attribute vulnerability, which could allow an attacker to intercept cookies transmitted over unencrypted HTTP connections, enabling the unauthorized extraction of sensitive information such as session identifiers...

CVE-2026-66249

The HCL iControl application is affected by a Missing Secure Attribute vulnerability. This flaw could allow an attacker to intercept cookies transmitted over unencrypted HTTP connections , potentially leading to the unauthorized extraction of sensitive information, such as session identifiers . N...

CVE-2026-66249: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

iControl is affected by a Missing Secure Attribute vulnerability, which could allow an attacker to intercept cookies transmitted over unencrypted HTTP connections, enabling the unauthorized extraction of sensitive information such as session identifiers...

PT-2026-103867

iControl is affected by a Missing Secure Attribute vulnerability, which could allow an attacker to intercept cookies transmitted over unencrypted HTTP connections, enabling the unauthorized extraction of sensitive information such as session identifiers...

CVE-2026-100725: Exposure of Sensitive Information to an Unauthorized Actor

http4k Maven artifact org.http4k:http4k-core before 6.48.0.0, 5.42.0.0, and 4.51.0.0 ships a BasicCookieStorage client-side cookie store used by ClientFilters.Cookies that does not enforce RFC 6265 scoping rules for the cookie domain, path, and Secure attributes. When a single BasicCookieStorage...

Astra Linux – Vulnerability in Tomcat9

When using RemoteIpFilter with requests received from a reverse proxy via HTTP that includes the X-Forwarded-Proto header set to https, session cookies created by Apache Tomcat 11.0.0-M1 to 11.0.0.-M2, 10.1.0-M1 to 10.1.5, 9.0.0-M1 to 9.0.71, and 8.5.0 to 8.5.85 did not include the secure...

CVE-2026-80255

A "Set-Cookie:" header using tab horizontal tab, ASCII code 9 instead of space ascii code 32 immediately before the "Secure" attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host...

CVE-2026-80255 secure cookie attribute bypass with tab

A Set-Cookie: header using tab horizontal tab, ASCII code 9 instead of space ascii code 32 immediately before the Secure attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host...

CVE-2026-80255 secure cookie attribute bypass with tab

A Set-Cookie: header using tab horizontal tab, ASCII code 9 instead of space ascii code 32 immediately before the Secure attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host...

CVE-2026-80255

The curl utility incorrectly handles the Set-Cookie: header when a horizontal tab (ASCII code 9) is used instead of a space (ASCII code 32) before the Secure attribute. This parsing error causes curl to store the cookie without the Secure flag, potentially leading to the cookie being transmitted ...

CVE-2026-80255: Insertion of Sensitive Information Into Sent Data

A Set-Cookie: header using tab horizontal tab, ASCII code 9 instead of space ascii code 32 immediately before the Secure attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host...

curl: curl: Information disclosure due to secure cookie attribute bypass

A flaw was found in curl. When a Set-Cookie: header uses a tab character instead of a space before the Secure attribute, curl incorrectly stores the cookie without the Secure flag. This can lead to information disclosure, as the cookie may then be sent over unencrypted HTTP connections to the sam...

CURL-CVE-2026-80255 secure cookie attribute bypass with tab

A Set-Cookie: header using tab horizontal tab, ASCII code 9 instead of space ascii code 32 immediately before the Secure attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host...

secure cookie attribute bypass with tab

A Set-Cookie: header using tab horizontal tab, ASCII code 9 instead of space ascii code 32 immediately before the Secure attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host...