CVE-2026-124709 (GCVE-0-2026-124709)
Vulnerability from cvelistv5 – Published: 2026-11-17 08:14 – Updated: 2026-11-17 16:50- CWE-401 - Missing Release of Memory after Effective Lifetime
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-124709",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:50:13.860911Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:50:38.539Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Bhabani Sankar Das"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Bhabani Sankar Das"
}
],
"datePublic": "2026-11-17T07:01:24.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A QUIC server that rejects a stream opened by the peer may\u003cbr\u003eretain that stream\u0027s state for the lifetime of the connection if the peer\u003cbr\u003eresets the stream before the rejection is signalled, even though the peer\u0027s\u003cbr\u003estream credit is returned.\u003cbr\u003e\u003cbr\u003eImpact summary: A remote client that completes a QUIC handshake can repeatedly\u003cbr\u003eopen and reset streams, causing server memory to grow without bound until the\u003cbr\u003eprocess runs out of memory and every connection on it is lost. This is a\u003cbr\u003eDenial of Service.\u003cbr\u003e\u003cbr\u003eCWE: CWE-401: Missing Release of Memory after Effective Lifetime\u003cbr\u003e\u003cbr\u003eDescription: QUIC servers track each stream the peer opens. When the incoming\u003cbr\u003estream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks\u003cbr\u003ethe stream deleted and returns the peer\u0027s stream credit. A deleted stream is\u003cbr\u003ecollected only once its receive part is fully drained, which for a rejected\u003cbr\u003estream means the STOP_SENDING has been acknowledged. If the peer sends\u003cbr\u003eRESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never\u003cbr\u003esent or acknowledged and the stream is never collected.\u003cbr\u003e\u003cbr\u003eThe default configuration reaches this path. Once a connection has a default\u003cbr\u003estream, meaning the application has read from or written to the connection as\u003cbr\u003ethe tutorial server does, the effective incoming stream policy rejects streams\u003cbr\u003ethe application does not accept. Applications that set the REJECT policy\u003cbr\u003eexplicitly are affected too.\u003cbr\u003e\u003cbr\u003eEach retained stream costs about 300 bytes, and the peer\u0027s stream credit\u003cbr\u003ewindow paces how quickly they accumulate. A client that keeps the connection\u003cbr\u003eopen and keeps opening and resetting streams grows server memory without\u003cbr\u003ebound. The severity is Low because growth is slow, needs a long-lived\u003cbr\u003econnection, and causes no memory corruption or disclosure.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe affected code is outside the FIPS module boundary."
}
],
"value": "Issue summary: A QUIC server that rejects a stream opened by the peer may\nretain that stream\u0027s state for the lifetime of the connection if the peer\nresets the stream before the rejection is signalled, even though the peer\u0027s\nstream credit is returned.\n\nImpact summary: A remote client that completes a QUIC handshake can repeatedly\nopen and reset streams, causing server memory to grow without bound until the\nprocess runs out of memory and every connection on it is lost. This is a\nDenial of Service.\n\nCWE: CWE-401: Missing Release of Memory after Effective Lifetime\n\nDescription: QUIC servers track each stream the peer opens. When the incoming\nstream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks\nthe stream deleted and returns the peer\u0027s stream credit. A deleted stream is\ncollected only once its receive part is fully drained, which for a rejected\nstream means the STOP_SENDING has been acknowledged. If the peer sends\nRESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never\nsent or acknowledged and the stream is never collected.\n\nThe default configuration reaches this path. Once a connection has a default\nstream, meaning the application has read from or written to the connection as\nthe tutorial server does, the effective incoming stream policy rejects streams\nthe application does not accept. Applications that set the REJECT policy\nexplicitly are affected too.\n\nEach retained stream costs about 300 bytes, and the peer\u0027s stream credit\nwindow paces how quickly they accumulate. A client that keeps the connection\nopen and keeps opening and resetting streams grows server memory without\nbound. The severity is Low because growth is slow, needs a long-lived\nconnection, and causes no memory corruption or disclosure.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-401",
"description": "Missing Release of Memory after Effective Lifetime",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T08:14:35.674Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261117.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ead311df1037e7994a6d86c7e862d71ad59c52c7"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/22291a6af12f158fbb13bfbd572a33dbdbf290d2"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/f3acb0a3328046741479482c51cec815839e1b05"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Unbounded Memory Retention in QUIC Server for Rejected Streams",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-124709",
"datePublished": "2026-11-17T08:14:35.674Z",
"dateReserved": "2026-11-09T10:45:57.951Z",
"dateUpdated": "2026-11-17T16:50:38.539Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-124709",
"date": "2026-11-17",
"epss": "0.00191",
"percentile": "0.08854"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"source": "openssl-security@openssl.org"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Issue summary: A QUIC server that rejects a stream opened by the peer may\nretain that stream\u0027s state for the lifetime of the connection if the peer\nresets the stream before the rejection is signalled, even though the peer\u0027s\nstream credit is returned.\n\nImpact summary: A remote client that completes a QUIC handshake can repeatedly\nopen and reset streams, causing server memory to grow without bound until the\nprocess runs out of memory and every connection on it is lost. This is a\nDenial of Service.\n\nCWE: CWE-401: Missing Release of Memory after Effective Lifetime\n\nDescription: QUIC servers track each stream the peer opens. When the incoming\nstream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks\nthe stream deleted and returns the peer\u0027s stream credit. A deleted stream is\ncollected only once its receive part is fully drained, which for a rejected\nstream means the STOP_SENDING has been acknowledged. If the peer sends\nRESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never\nsent or acknowledged and the stream is never collected.\n\nThe default configuration reaches this path. Once a connection has a default\nstream, meaning the application has read from or written to the connection as\nthe tutorial server does, the effective incoming stream policy rejects streams\nthe application does not accept. Applications that set the REJECT policy\nexplicitly are affected too.\n\nEach retained stream costs about 300 bytes, and the peer\u0027s stream credit\nwindow paces how quickly they accumulate. A client that keeps the connection\nopen and keeps opening and resetting streams grows server memory without\nbound. The severity is Low because growth is slow, needs a long-lived\nconnection, and causes no memory corruption or disclosure.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"id": "CVE-2026-124709",
"lastModified": "2026-11-17T17:17:57.453",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-124709",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:50:13.860911Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-17T09:17:27.227",
"references": [
{
"source": "openssl-security@openssl.org",
"url": "https://github.com/openssl/openssl/commit/22291a6af12f158fbb13bfbd572a33dbdbf290d2"
},
{
"source": "openssl-security@openssl.org",
"url": "https://github.com/openssl/openssl/commit/ead311df1037e7994a6d86c7e862d71ad59c52c7"
},
{
"source": "openssl-security@openssl.org",
"url": "https://github.com/openssl/openssl/commit/f3acb0a3328046741479482c51cec815839e1b05"
},
{
"source": "openssl-security@openssl.org",
"url": "https://openssl-library.org/news/secadv/20261117.txt"
}
],
"sourceIdentifier": "openssl-security@openssl.org",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-401"
}
],
"source": "openssl-security@openssl.org",
"type": "Secondary"
}
]
}
}
}
}
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.