Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, ResponseCookie.render writes attacker-influenced name, content, domain, path, and extension values without neutralizing semicolons or control characters. An application that constructs a ResponseCookie from unvalidated input can therefore emit injected cookie attributes such as Domain, Path, or SameSite, widening cookie scope or weakening protections, and control characters may enable header splitting on permissive backends. The patch strips control characters from all five fields and strips semicolons from name, content, domain, and path while retaining the extension delimiter behavior. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
CVE-2026-69211
MEDIUMPre-NVD 4.84.8—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.8
- EG Score
- 4.8(medium)
- EG Risk
- 22(Track)EG Risk 22/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity48% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026Patch available. Sources: github, github_commit, github_release.
github_release Patch Available
v1.0.0-M47
Patch available: http4s/http4s v1.0.0-M47 (pre-release)
https://github.com/http4s/http4s/releases/tag/v1.0.0-M47github_release Patch Available
v0.23.35
Patch available: http4s/http4s v0.23.35
https://github.com/http4s/http4s/releases/tag/v0.23.35github_commit Patch Available
commit 5c8e69ac0f4a (http4s/http4s)
Patch available: http4s/http4s v0.23.35 (contains commit 5c8e69ac0f4a)
https://github.com/http4s/http4s/commit/5c8e69ac0f4a2fe03c3481dccd74101cd2e2a890github Patch Available
Set-Cookie rendering does not escape attribute delimiters · Advisory · http4s/http4s · GitHub
https://github.com/http4s/http4s/security/advisories/GHSA-7qh7-rghh-698hWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:57 UTCEG score recompute
- 2026-09-16 14:25 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 14:06 UTCEG score recompute
- 2026-09-15 19:32 UTCEG score recompute
- 2026-09-15 19:03 UTCEG score recompute
- 2026-09-15 19:02 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-69211?
CVE-2026-69211 is a medium vulnerability published on September 15, 2026. Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, ResponseCookie.render writes attacker-influenced name, content, domain, path, and extension values without neutralizing semicolons or control characters. An application that constructs a ResponseCookie from unvalidated…
When was CVE-2026-69211 disclosed?
CVE-2026-69211 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69211 actively exploited?
CVE-2026-69211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.6% of all scored CVEs.
What is the CVSS score of CVE-2026-69211?
CVE-2026-69211 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-69211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-69211
Is Your Infrastructure Affected by CVE-2026-69211?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.