CVE-2018-1000007
No exploitation reported by the sources we read.
- Published2018-01-24
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.
Timeline
dates in UTC- 2018-01-2422:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-1000007?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-1000007?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.4 | = 12.04 | no fix published | NVD |
| 14.4 | = 14.04 | no fix published | NVD |
| 16.4 | = 16.04 | no fix published | NVD |
| 17.10 | = 17.10 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.0 | = 7.0 | no fix published | NVD |
| 8.0 | = 8.0 | no fix published | NVD |
| 9.0 | = 9.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | < xcp3070 | xcp3070 | NVD |
| — | < xcp2361 | xcp2361 | NVD |
11 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- curl.haxx.sePatch · Vendor Advisory
- www.oracle.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- FIRST EPSSEPSS score6.6 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-01-24
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-1000007?
Is CVE-2018-1000007 actively exploited?
What is the CVSS score for CVE-2018-1000007?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.