{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-107284 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-107284 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-107284 is a low-severity vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 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-107284 and fix it if it is affected.\n\nWhat it is: CVE-2026-107284 is a low-severity vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 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-107284 in the wild and no public exploit code.\n\nAffected product: AsyncHttpClient async-http-client. 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-107284/ (Markdown: https://insights.sbomify.com/CVE-2026-107284/index.md)","id":"CVE-2026-107284","markdown":"https://insights.sbomify.com/CVE-2026-107284/index.md","name":"CVE-2026-107284","record":{"aliases":["DEBIAN-CVE-2026-107284","GHSA-rwhr-j9rv-85f8","UBUNTU-CVE-2026-107284"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java HTTP client library","requires_auth":"none","summary":"Attackers can bypass WebSocket handshake validation to receive frames from unverified peers, potentially exposing data or enabling further attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Prior to 3.0.12 and 2.16.1, WebSocketHandler.upgrade aborts a handshake whose Sec-WebSocket-Accept value is missing or invalid but continues into pipeline installation and onOpen delivery. Frames coalesced with the invalid 101 response can be decoded and delivered from a peer that did not prove the handshake, although the request future fails and the channel closes. This issue is fixed in versions 3.0.12 and 2.16.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"AsyncHttpClient: WebSocket handshake continues after a failed Sec-WebSocket-Accept check","id":"CVE-2026-107284","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"AsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel","id":"CVE-2026-107285"},"packages":[],"prev":{"headline":"AsyncHttpClient: Digest authentication cnonce generated with a non-cryptographic random source","id":"CVE-2026-107283"},"products":["async-http-client"],"published":"2026-10-07","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["AsyncHttpClient"]},"summary":"Attackers can bypass WebSocket handshake validation to receive frames from unverified peers, potentially exposing data or enabling further attacks.","url":"https://insights.sbomify.com/CVE-2026-107284/"}