{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-69212 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-69212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-69212 is a medium-severity vulnerability in http4s, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-69212 and fix it if it is affected.\n\nWhat it is: CVE-2026-69212 is a medium-severity vulnerability in http4s, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-69212 in the wild and no public exploit code.\n\nAffected product: http4s. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-69212/ (Markdown: https://insights.sbomify.com/CVE-2026-69212/index.md)","id":"CVE-2026-69212","markdown":"https://insights.sbomify.com/CVE-2026-69212/index.md","name":"CVE-2026-69212","record":{"aliases":["GHSA-2rgg-r783-mrx4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Scala HTTP library","requires_auth":"none","summary":"Attackers can capture sensitive credentials transmitted over plaintext HTTP due to a flaw in Http4s FollowRedirect middleware handling same-authority downgrades.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, The FollowRedirect client middleware strips Authorization and Cookie headers only when a redirect changes authority, but authority comparison excludes the URI scheme. A same-authority redirect from HTTPS to HTTP therefore preserves credentials and transmits them over a plaintext connection. An attacker who can induce the downgrade and observe the network can capture those sensitive headers from applications using FollowRedirect. This issue is fixed in versions 0.23.35 and 1.0.0-M47.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-28","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-28T19:30:00Z","kind":"github_poc","ref":"https://github.com/c0gnit00/CVE-2026-69212","stars":2,"title":" Python poc, exploit for CVE-2025-69212"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Http4s: FollowRedirect middleware leaks credentials over https-\u003ehttp same-authority redirect","id":"CVE-2026-69212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Http4s Ember HTTP/2: unbounded outbound frame queue","id":"CVE-2026-69213"},"packages":[],"prev":{"headline":"Http4s: Set-Cookie rendering does not escape attribute delimiters","id":"CVE-2026-69211"},"products":["http4s"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-15","vendors":["http4s"]},"summary":"Attackers can capture sensitive credentials transmitted over plaintext HTTP due to a flaw in Http4s FollowRedirect middleware handling same-authority downgrades.","url":"https://insights.sbomify.com/CVE-2026-69212/"}