CVE-2026-94266 password leak in CURLINFO_EFFECTIVE_URL
Not scored
Published
Updated
Check this codebase for CVE-2026-94266 and fix it if it is affected.
What it is: CVE-2026-94266 is a vulnerability in curl, published on 20 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-94266 in the wild and no public exploit code.
Affected product: curl. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-94266/ (Markdown: https://insights.sbomify.com/CVE-2026-94266/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-94266?
CVE-2026-94266 is a vulnerability in curl, published on 20 Oct 2026.
Official description
libcurl could accidentally return a URL for `curl_easy_getinfo()`'s `CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.
Which versions are affected by CVE-2026-94266?
How do I fix CVE-2026-94266?
Upgrade to a fixed version.
Is CVE-2026-94266 being exploited?
There is no known exploitation of CVE-2026-94266 in the wild and no public exploit code.
Sources
Also known as ALPINE-CVE-2026-94266, AZL-109908, AZL-109947, AZL-110034, AZL-110157, AZL-110220 and 8 more.