UBUNTU-CVE-2026-90588 (CVE-2026-90588)
Vulnerability from osv_ubuntu – Published: 2026-11-09 22:18 – Updated: 2026-11-18 11:08 – Source websiteThe HTTP client's debug helper print_header_field() in subsys/net/lib/http/http_client.c formatted an http_parser data-callback slice with a %s conversion: snprintk(output, len + 1, "%s", str). The parser hands its callbacks a pointer and a length into the caller's receive buffer, and those bytes are not NUL terminated. The size argument of snprintk() bounds only the destination, while the %s conversion measures the source first — lib/os/cbprintf_complete.c uses strlen() when no precision is given, and lib/os/cbprintf_nano.c uses strlen() unconditionally — so the read walks past the end of the header field and past the end of the receive buffer until it finds a zero byte. The slice reaches the helper from on_url(), on_header_field() and on_header_value(), which the parser invokes on bytes that http_wait_data() read straight off the socket into the application-supplied recv_buf. A malicious or compromised HTTP server, or an attacker able to answer a plaintext request, therefore controls both the header field and the bytes that follow it in the buffer, and can guarantee that no zero byte appears before the buffer ends, forcing the over-read. The in-tree tests/net/lib/http_client suite reproduces the over-read under CONFIG_ASAN=y on an ordinary GET. The impact is bounded. The whole helper body is compiled only when the HTTP client log module is explicitly set to Debug (CONFIG_NET_HTTP_LOG_LEVEL_DBG=y, which the global CONFIG_LOG_DEFAULT_LEVEL does not set), so default builds are unaffected. No out-of-bounds write occurs and none of the over-read bytes are emitted into the log, so there is no information disclosure; the consequence is an out-of-bounds read that can fault and panic the device where the buffer abuts an unmapped or MPU/MMU-protected region. The fix copies exactly the len bytes the parser offered with memcpy() and terminates them, instead of relying on a %s conversion (a %.*s precision would not have sufficed, since cbprintf_nano.c measures the source in full before applying it).
| URL | Type |
|---|---|
| https://ubuntu.com/security/CVE-2026-90588 | REPORT |
| https://www.cve.org/CVERecord?id=CVE-2026-90588 | REPORT |
| Ecosystem | Package | Version |
|---|---|---|
| Ubuntu:16.04:LTS |
zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1build1?arch=source&distro=xenial
|
Affected: All versions (ecosystem)
3.1.2-13.1.2-1build1
|
| Ubuntu:18.04:LTS |
zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1build2?arch=source&distro=bionic
|
Affected: All versions (ecosystem)
3.1.2-1build13.1.2-1build2
|
| Ubuntu:20.04:LTS |
zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source&distro=focal
|
Affected: All versions (ecosystem)
3.1.2-1build3
|
| Ubuntu:22.04:LTS |
zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source&distro=jammy
|
Affected: All versions (ecosystem)
3.1.2-1build3
|
| Ubuntu:24.04:LTS |
zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1.1build1?arch=source&distro=noble
|
Affected: All versions (ecosystem)
3.1.2-1.13.1.2-1.1build1
|
| Ubuntu:26.10 |
zephyr
pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source&distro=stonking
|
Affected: All versions (ecosystem)
3.1.2-4
|
| Ubuntu:26.04:LTS |
zephyr
pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source&distro=resolute
|
Affected: All versions (ecosystem)
3.1.2-1.1build13.1.2-4
|
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1build1"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1build1"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1build1"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1build1"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1",
"3.1.2-1build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1build2"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1build2"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1build2"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1build2"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1build2"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build2?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1build1",
"3.1.2-1build2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1build3"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1build3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1build3"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1build3"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1build3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-1.1build1"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-1.1build1"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-1.1build1"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-1.1build1"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-1.1build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-1.1build1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1.1",
"3.1.2-1.1build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-4"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-4"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libzephyr4",
"binary_version": "3.1.2-4"
},
{
"binary_name": "libzephyr4-krb5",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-clients",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-server",
"binary_version": "3.1.2-4"
},
{
"binary_name": "zephyr-server-krb5",
"binary_version": "3.1.2-4"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "zephyr",
"purl": "pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.1.2-1.1build1",
"3.1.2-4"
]
}
],
"aliases": [],
"details": "The HTTP client\u0027s debug helper print_header_field() in subsys/net/lib/http/http_client.c formatted an http_parser data-callback slice with a %s conversion: snprintk(output, len + 1, \"%s\", str). The parser hands its callbacks a pointer and a length into the caller\u0027s receive buffer, and those bytes are not NUL terminated. The size argument of snprintk() bounds only the destination, while the %s conversion measures the source first \u2014 lib/os/cbprintf_complete.c uses strlen() when no precision is given, and lib/os/cbprintf_nano.c uses strlen() unconditionally \u2014 so the read walks past the end of the header field and past the end of the receive buffer until it finds a zero byte. The slice reaches the helper from on_url(), on_header_field() and on_header_value(), which the parser invokes on bytes that http_wait_data() read straight off the socket into the application-supplied recv_buf. A malicious or compromised HTTP server, or an attacker able to answer a plaintext request, therefore controls both the header field and the bytes that follow it in the buffer, and can guarantee that no zero byte appears before the buffer ends, forcing the over-read. The in-tree tests/net/lib/http_client suite reproduces the over-read under CONFIG_ASAN=y on an ordinary GET. The impact is bounded. The whole helper body is compiled only when the HTTP client log module is explicitly set to Debug (CONFIG_NET_HTTP_LOG_LEVEL_DBG=y, which the global CONFIG_LOG_DEFAULT_LEVEL does not set), so default builds are unaffected. No out-of-bounds write occurs and none of the over-read bytes are emitted into the log, so there is no information disclosure; the consequence is an out-of-bounds read that can fault and panic the device where the buffer abuts an unmapped or MPU/MMU-protected region. The fix copies exactly the len bytes the parser offered with memcpy() and terminates them, instead of relying on a %s conversion (a %.*s precision would not have sufficed, since cbprintf_nano.c measures the source in full before applying it).",
"id": "UBUNTU-CVE-2026-90588",
"modified": "2026-11-18T11:08:36Z",
"published": "2026-11-09T22:18:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-90588"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90588"
},
{
"type": "REPORT",
"url": "github.com/zephyrproject-rtos/zephyr"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-90588"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.