curl — security advisory
libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.
- Products
- curl
- Affected versions
- Not specified
- Fixed versions
- 7.58.0-r0
- CVEs
- CVE-2018-1000005
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 22:08 UTC · Revision 1
Source evidence
libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.
osv:ALPINE-CVE-2018-1000005
curl
Fixed versions: 7.58.0-r0
curl
Fixed versions: 7.58.0-r0
curl
Fixed versions: 7.58.0-r0
curl
Fixed versions: 7.58.0-r0
Complete source record
{
"id": "3111bba30f125b77f6726762c2f2b07e8cff0650f52961d98efff4797eef87de",
"url": "https://osv.dev/vulnerability/ALPINE-CVE-2018-1000005",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ALPINE-CVE-2018-1000005",
"summary": "libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like `:` to the target buffer, while this was recently changed to `: ` (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.",
"evidence": "osv:ALPINE-CVE-2018-1000005",
"products": [
{
"name": {
"value": "curl",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.58.0-r0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "curl",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.58.0-r0",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "curl",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.58.0-r0",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "curl",
"evidence": "/affected/3/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.58.0-r0",
"evidence": "/affected/3/ranges"
}
],
"affected_versions": []
}
],
"severity": "critical",
"structured": {
"id": "ALPINE-CVE-2018-1000005",
"aliases": [
"ALPINE-CVE-2018-1000005"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "7.58.0-r0"
}
]
}
],
"package": {
"name": "curl",
"purl": "pkg:apk/alpine/curl?arch=source",
"ecosystem": "Alpine:v3.4"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/alpine/ALPINE-CVE-2018-1000005.json"
},
"ecosystem_specific": {}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "7.58.0-r0"
}
]
}
],
"package": {
"name": "curl",
"purl": "pkg:apk/alpine/curl?arch=source",
"ecosystem": "Alpine:v3.5"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/alpine/ALPINE-CVE-2018-1000005.json"
},
"ecosystem_specific": {}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "7.58.0-r0"
}
]
}
],
"package": {
"name": "curl",
"purl": "pkg:apk/alpine/curl?arch=source",
"ecosystem": "Alpine:v3.6"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/alpine/ALPINE-CVE-2018-1000005.json"
},
"ecosystem_specific": {}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "7.58.0-r0"
}
]
}
],
"package": {
"name": "curl",
"purl": "pkg:apk/alpine/curl?arch=source",
"ecosystem": "Alpine:v3.7"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/alpine/ALPINE-CVE-2018-1000005.json"
},
"ecosystem_specific": {}
}
],
"modified": "2026-10-23T17:23:28.122535644Z",
"provider": "osv",
"upstream": [
"CVE-2018-1000005"
],
"references": [
"https://security.alpinelinux.org/vuln/CVE-2018-1000005"
]
},
"related_cves": [
{
"value": "CVE-2018-1000005",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 415665,
"published_at": "2018-01-24T22:29:00.307+00:00"
}