A URL value can include a secret

CVE-2026-94266 affects libcurl’s CURLINFO_EFFECTIVE_URL result. The curl project says a returned URL could contain credentials even when neither the original URL nor the redirected URL did. This can happen when curl reads credentials from a `.netrc` file. The command line tool exposes the value through `%{url_effective}`.

Affected versions are 7.62.0 through 8.22.0. The issue is rated Low and fixed in 8.23.0, with listed backports. Check whether application logs, monitoring or shell output record effective URLs.

Search logs and scripts for URL output

Review code that calls CURLINFO_EFFECTIVE_URL and scripts that use `--write-out`. Check whether output goes to application logs, job logs, support tickets or monitoring systems. Restrict access to `.netrc` files and use dedicated service accounts.

Avoid putting usernames, passwords or tokens in URL logs. If an effective URL with credentials was stored in a shared or external log system, follow the organisation’s credential rotation and log-retention process.

Update every libcurl consumer

Install the fixed curl or libcurl package and restart applications that load the old library. Rebuild containers and verify the version used by scheduled jobs and web services.

Test the logging format after the update. Confirm that no credential appears in the effective URL or job output when `.netrc` supplies authentication.