Missing Encryption of Sensitive Data Affecting nextcloud-server-33 package, versions <33.0.5-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.11% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-WOLFILATEST-NEXTCLOUDSERVER33-17400840
  • published22 Jun 2026
  • disclosed23 Jun 2026

Introduced: 22 Jun 2026

CVE-2026-55568  (opens in a new tab)
CWE-311  (opens in a new tab)
CWE-319  (opens in a new tab)
CWE-636  (opens in a new tab)

How to fix?

Upgrade Wolfi nextcloud-server-33 to version 33.0.5-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nextcloud-server-33 package and not the nextcloud-server-33 package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, in certain configurations, traffic expected to be protected by TLS on the hop to the proxy is transmitted in cleartext. Proxy authentication credentials (the Proxy-Authorization header, proxy userinfo in the proxy URL, or CURLOPT_PROXYUSERPWD) are sent without encryption, and the CONNECT target host and port for tunneled HTTPS requests are exposed. The built-in cURL handlers (GuzzleHttp\Handler\CurlHandler and GuzzleHttp\Handler\CurlMultiHandler, used by default whenever the PHP cURL extension is available) accept an https:// proxy. libcurl older than 7.50.2 silently treats an https:// proxy as a plaintext http:// proxy. The TLS connection to the proxy is never established, and the proxy leg is cleartext with no error or warning. An application is affected when it sends requests through one of the built-in cURL handlers, configures an https:// proxy expecting the proxy connection itself to be encrypted, and runs with libcurl older than 7.50.2. This vulnerability is fixed in 7.12.1.