{"answers":{"affected":"1 open source package ship an affected version, including pingora-core.","exploited":"There is no known exploitation of CVE-2026-105297 in the wild and no public exploit code.","fix":"Upgrade pingora-core to 0.8.1 or later.","what":"CVE-2026-105297 is a high-severity vulnerability in https://github.com/cloudflare/pingora, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105297 and fix it if it is affected.\n\nWhat it is: CVE-2026-105297 is a high-severity vulnerability in https://github.com/cloudflare/pingora, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105297 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pingora-core (crates.io): affected from 0.0.0-0; fixed in 0.8.1\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-105297/ (Markdown: https://insights.sbomify.com/CVE-2026-105297/index.md)","id":"CVE-2026-105297","markdown":"https://insights.sbomify.com/CVE-2026-105297/index.md","name":"CVE-2026-105297","record":{"aliases":["GHSA-7gpj-mj4q-x62x","GHSA-x6pg-x323-jhc4","RUSTSEC-2026-0389"],"analysis":null,"analysis_generated_by":null,"assigner":"cloudflare","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Summary\n\nBefore version 0.8.1, Pingora's HTTP/2 server used the h2 crate's default limits unless the application set its own 16 MiB decoded header-list size and no limit on concurrent streams. A remote, unauthenticated client can send 1-byte HPACK references to a near-empty header, making the server allocate hundreds of thousands of header fields per stream across an unlimited number of streams on one connection, and use HTTP/2 flow control to keep those streams open. This can exhaust memory and degrade or terminate the Pingora process.\n\nImpact\n\nRemote, unauthenticated denial of service against any Pingora service that terminates HTTP/2 (h2 or h2c) without explicitly setting max_header_list_size and max_concurrent_streams. The reporter showed that a single connection could get a Pingora process with a 2 GiB memory limit OOM-killed.\n\nNote that Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients.\n\nMitigation:\n\n  *  \n\nUpgrade to pingora 0.8.1 or later (fix:  https://github.com/cloudflare/pingora/commit/d193c8d49b8b7c1c1ede93183759caa4f6906bbd ). When no H2Options are supplied, Pingora now advertises and enforces a 64 KiB decoded header-list limit and at most 100 concurrent streams per connection.\n\n  *  \n\nApplications that supply their own H2Options are not covered by these defaults and must set max_header_list_size and max_concurrent_streams explicitly (this also works on versions before 0.8.1), or, on 0.8.1 and later, start from pingora_core::protocols::http::v2::server::default_h2_options(). H2Options::default() does not include these limits.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Pingora HTTP/2 server memory exhaustion through unbounded default header-list and concurrent-stream limits","id":"CVE-2026-105297","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"Pingora HTTP/2 :authority and Host header mismatch enables cache poisoning and host-based access control bypass","id":"CVE-2026-105298"},"packages":[{"ecosystem":"crates.io","fixed":["0.8.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"pingora-core","purl":"pkg:cargo/pingora-core","source":"RUSTSEC-2026-0389"}],"prev":{"headline":"GitAhead 2.5.0 through 2.7.1 Unverified Update Installation and TLS Bypass","id":"CVE-2026-105295"},"products":["https://github.com/cloudflare/pingora"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["Cloudflare"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-105297/"}