{"api_version":"1","generated_at":"2026-09-27T02:57:16+00:00","cve":"CVE-2026-69209","urls":{"html":"https://cve.report/CVE-2026-69209","api":"https://cve.report/api/cve/CVE-2026-69209.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-69209","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-69209"},"summary":{"title":"Http4s: WebSocket decoder accepts unbounded message sizes","description":"Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, The shared WebSocket decoder permits unbounded message buffering because defragmentation accumulates fragments without a limit and FrameTranscoder accepts declared lengths up to Int.MaxValue. A remote client that completes a WebSocket handshake against an http4s-blaze-server or http4s-ember-server endpoint can exhaust server memory with oversized frames or fragmented messages. The patched decoder applies a configurable 64 MiB default limit to individual frames and defragmented messages through EmberServerBuilder.withMaxWebSocketMessageSize. This issue is fixed in versions 0.23.35 and 1.0.0-M47.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-09-15 19:17:37","updated_at":"2026-09-16 20:39:16"},"problem_types":["CWE-400","CWE-770","CWE-400 CWE-400: Uncontrolled Resource Consumption","CWE-770 CWE-770: Allocation of Resources Without Limits or Throttling"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"7.5","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.5","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","data":{"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"}}],"references":[{"url":"https://github.com/http4s/http4s/releases/tag/v1.0.0-M47","name":"https://github.com/http4s/http4s/releases/tag/v1.0.0-M47","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/http4s/http4s/security/advisories/GHSA-jrxx-w2m8-5hf5","name":"https://github.com/http4s/http4s/security/advisories/GHSA-jrxx-w2m8-5hf5","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/http4s/http4s/releases/tag/v0.23.35","name":"https://github.com/http4s/http4s/releases/tag/v0.23.35","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/http4s/http4s/commit/d578c3c9da6193627d40fa785e612cda7fcd77b3","name":"https://github.com/http4s/http4s/commit/d578c3c9da6193627d40fa785e612cda7fcd77b3","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-69209","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-69209","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"http4s","product":"http4s","version":"affected < 0.23.35","platforms":[]},{"source":"CNA","vendor":"http4s","product":"http4s","version":"affected >= 1.0.0-M1, < 1.0.0-M47","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"69209","cve":"CVE-2026-69209","epss":"0.003500000","percentile":"0.284970000","score_date":"2026-09-16","updated_at":"2026-09-17 00:07:15"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-69209","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-09-16T18:25:00.686488Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-09-16T18:37:15.546Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"product":"http4s","vendor":"http4s","versions":[{"status":"affected","version":"< 0.23.35"},{"status":"affected","version":">= 1.0.0-M1, < 1.0.0-M47"}]}],"descriptions":[{"lang":"en","value":"Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, The shared WebSocket decoder permits unbounded message buffering because defragmentation accumulates fragments without a limit and FrameTranscoder accepts declared lengths up to Int.MaxValue. A remote client that completes a WebSocket handshake against an http4s-blaze-server or http4s-ember-server endpoint can exhaust server memory with oversized frames or fragmented messages. The patched decoder applies a configurable 64 MiB default limit to individual frames and defragmented messages through EmberServerBuilder.withMaxWebSocketMessageSize. This issue is fixed in versions 0.23.35 and 1.0.0-M47."}],"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"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-400","description":"CWE-400: Uncontrolled Resource Consumption","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-770","description":"CWE-770: Allocation of Resources Without Limits or Throttling","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-09-15T18:55:29.782Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/http4s/http4s/security/advisories/GHSA-jrxx-w2m8-5hf5","tags":["x_refsource_CONFIRM"],"url":"https://github.com/http4s/http4s/security/advisories/GHSA-jrxx-w2m8-5hf5"},{"name":"https://github.com/http4s/http4s/commit/d578c3c9da6193627d40fa785e612cda7fcd77b3","tags":["x_refsource_MISC"],"url":"https://github.com/http4s/http4s/commit/d578c3c9da6193627d40fa785e612cda7fcd77b3"},{"name":"https://github.com/http4s/http4s/releases/tag/v0.23.35","tags":["x_refsource_MISC"],"url":"https://github.com/http4s/http4s/releases/tag/v0.23.35"},{"name":"https://github.com/http4s/http4s/releases/tag/v1.0.0-M47","tags":["x_refsource_MISC"],"url":"https://github.com/http4s/http4s/releases/tag/v1.0.0-M47"}],"source":{"advisory":"GHSA-jrxx-w2m8-5hf5","discovery":"UNKNOWN"},"title":"Http4s: WebSocket decoder accepts unbounded message sizes"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-69209","datePublished":"2026-09-15T18:55:29.782Z","dateReserved":"2026-08-03T16:57:50.124Z","dateUpdated":"2026-09-16T18:37:15.546Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-15 19:17:37","lastModifiedDate":"2026-09-16 20:39:16","problem_types":["CWE-400","CWE-770","CWE-400 CWE-400: Uncontrolled Resource Consumption","CWE-770 CWE-770: Allocation of Resources Without Limits or Throttling"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":3.6}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-09-16T18:25:00.686488Z","id":"CVE-2026-69209","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"69209","Ordinal":"1","Title":"Http4s: WebSocket decoder accepts unbounded message sizes","CVE":"CVE-2026-69209","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"69209","Ordinal":"1","NoteData":"Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, The shared WebSocket decoder permits unbounded message buffering because defragmentation accumulates fragments without a limit and FrameTranscoder accepts declared lengths up to Int.MaxValue. A remote client that completes a WebSocket handshake against an http4s-blaze-server or http4s-ember-server endpoint can exhaust server memory with oversized frames or fragmented messages. The patched decoder applies a configurable 64 MiB default limit to individual frames and defragmented messages through EmberServerBuilder.withMaxWebSocketMessageSize. This issue is fixed in versions 0.23.35 and 1.0.0-M47.","Type":"Description","Title":"Http4s: WebSocket decoder accepts unbounded message sizes"}]}}}