{"items":[{"id":"NVI-00014157","kind":"vulnerability","title":"AsyncHttpClient re-sends client-wide realm credentials to a cross-origin redirect target","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f8m2-889x-vw4x","CVE-2026-85717"],"plain_summary":"GitHub lists this reviewed advisory for org.asynchttpclient:async-http-client, org.asynchttpclient:async-http-client. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1f1c22af25bf427bc380e24d8ba87821"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-17T17:19:33.000Z","value":"6.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5163e92ca3295ee7bdba688e619e191d"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.530%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.44806. Missing scores are unknown.","source_id":"sr-1f1c22af25bf427bc380e24d8ba87821"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5163e92ca3295ee7bdba688e619e191d","url":"https://github.com/advisories/GHSA-f8m2-889x-vw4x","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-f8m2-889x-vw4x","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T14:29:49.409Z"},{"id":"sr-1f1c22af25bf427bc380e24d8ba87821","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-85717","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:17:01.143Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5163e92ca3295ee7bdba688e619e191d"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nA client configured with a client-wide realm (a Realm set on the config builder rather than on an individual request) and following redirects could re-send those credentials to a redirect target on a different origin. The redirect code strips the per-exchange realm, but when the target answered 401 the credentials were re-derived from the client config, handing Basic or Digest credentials, or a Negotiate or NTLM token, to an attacker controlled origin. This is a residual of the earlier cross-origin credential leak advisories, whose strip this bypassed.\n\n### Affected versions\n* 3.x: 3.0.9 through 3.0.11\n* 2.x: 2.14.5 through 2.16.0\n\nReleases below those floors are covered by the earlier advisories GHSA-cmxv-58fp-fm3g and GHSA-fmxf-pm6p-7xgm: the cross-origin strip that this issue bypasses did not exist yet, so the leak there is the original one rather than this residual.\n\n### Patches\nFixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. The realm is taken from the per-exchange state that the redirect already cleared, rather than being re-derived from the client configuration.\n\n### Workarounds\nSet the Realm on the individual request instead of on the client config","public_affected_ranges":[">= 3.0.9, <= 3.0.11"]},{"certainty":"source_listed","source_ids":["sr-5163e92ca3295ee7bdba688e619e191d"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nA client configured with a client-wide realm (a Realm set on the config builder rather than on an individual request) and following redirects could re-send those credentials to a redirect target on a different origin. The redirect code strips the per-exchange realm, but when the target answered 401 the credentials were re-derived from the client config, handing Basic or Digest credentials, or a Negotiate or NTLM token, to an attacker controlled origin. This is a residual of the earlier cross-origin credential leak advisories, whose strip this bypassed.\n\n### Affected versions\n* 3.x: 3.0.9 through 3.0.11\n* 2.x: 2.14.5 through 2.16.0\n\nReleases below those floors are covered by the earlier advisories GHSA-cmxv-58fp-fm3g and GHSA-fmxf-pm6p-7xgm: the cross-origin strip that this issue bypasses did not exist yet, so the leak there is the original one rather than this residual.\n\n### Patches\nFixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. The realm is taken from the per-exchange state that the redirect already cleared, rather than being re-derived from the client configuration.\n\n### Workarounds\nSet the Realm on the individual request instead of on the client config","public_affected_ranges":[">= 2.14.5, <= 2.16.0"]}],"null_published_at":"2026-11-07T14:01:58.731Z","source_updated_at":"2026-09-17T17:19:33.000Z","source_disclosed_at":"2026-09-17T17:19:31.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T14:29:49.409Z"},{"id":"NVI-00014157","kind":"vulnerability","title":"AsyncHttpClient re-sends client-wide realm credentials to a cross-origin redirect target","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f8m2-889x-vw4x","CVE-2026-85717"],"plain_summary":"GitHub lists this reviewed advisory for org.asynchttpclient:async-http-client, org.asynchttpclient:async-http-client. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5163e92ca3295ee7bdba688e619e191d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-17T17:19:33.000Z","value":"6.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5163e92ca3295ee7bdba688e619e191d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5163e92ca3295ee7bdba688e619e191d","url":"https://github.com/advisories/GHSA-f8m2-889x-vw4x","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-f8m2-889x-vw4x","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T14:29:49.409Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5163e92ca3295ee7bdba688e619e191d"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nA client configured with a client-wide realm (a Realm set on the config builder rather than on an individual request) and following redirects could re-send those credentials to a redirect target on a different origin. The redirect code strips the per-exchange realm, but when the target answered 401 the credentials were re-derived from the client config, handing Basic or Digest credentials, or a Negotiate or NTLM token, to an attacker controlled origin. This is a residual of the earlier cross-origin credential leak advisories, whose strip this bypassed.\n\n### Affected versions\n* 3.x: 3.0.9 through 3.0.11\n* 2.x: 2.14.5 through 2.16.0\n\nReleases below those floors are covered by the earlier advisories GHSA-cmxv-58fp-fm3g and GHSA-fmxf-pm6p-7xgm: the cross-origin strip that this issue bypasses did not exist yet, so the leak there is the original one rather than this residual.\n\n### Patches\nFixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. The realm is taken from the per-exchange state that the redirect already cleared, rather than being re-derived from the client configuration.\n\n### Workarounds\nSet the Realm on the individual request instead of on the client config","public_affected_ranges":[">= 3.0.9, <= 3.0.11"]},{"certainty":"source_listed","source_ids":["sr-5163e92ca3295ee7bdba688e619e191d"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nA client configured with a client-wide realm (a Realm set on the config builder rather than on an individual request) and following redirects could re-send those credentials to a redirect target on a different origin. The redirect code strips the per-exchange realm, but when the target answered 401 the credentials were re-derived from the client config, handing Basic or Digest credentials, or a Negotiate or NTLM token, to an attacker controlled origin. This is a residual of the earlier cross-origin credential leak advisories, whose strip this bypassed.\n\n### Affected versions\n* 3.x: 3.0.9 through 3.0.11\n* 2.x: 2.14.5 through 2.16.0\n\nReleases below those floors are covered by the earlier advisories GHSA-cmxv-58fp-fm3g and GHSA-fmxf-pm6p-7xgm: the cross-origin strip that this issue bypasses did not exist yet, so the leak there is the original one rather than this residual.\n\n### Patches\nFixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. The realm is taken from the per-exchange state that the redirect already cleared, rather than being re-derived from the client configuration.\n\n### Workarounds\nSet the Realm on the individual request instead of on the client config","public_affected_ranges":[">= 2.14.5, <= 2.16.0"]}],"null_published_at":"2026-11-02T10:00:37.215Z","source_updated_at":"2026-09-17T17:19:33.000Z","source_disclosed_at":"2026-09-17T17:19:31.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T14:29:49.409Z"}],"next_cursor":null,"snapshot_revision":"42594"}