{"items":[{"id":"NVI-00012094","kind":"vulnerability","title":"AsyncHttpClient: Pooled connections can still be shared across NTLM, Negotiate and proxy logins","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-v2j5-22fr-j62r","CVE-2026-107230"],"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-01d7972361cfbcceaee9282dd0664fb2"],"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-10-08T16:49:47.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-a4aaad5f8605964caa249eb4edb7d0b4"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.188%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.08485. Missing scores are unknown.","source_id":"sr-01d7972361cfbcceaee9282dd0664fb2"}],"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-a4aaad5f8605964caa249eb4edb7d0b4","url":"https://github.com/advisories/GHSA-v2j5-22fr-j62r","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-v2j5-22fr-j62r","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:38.867Z"},{"id":"sr-01d7972361cfbcceaee9282dd0664fb2","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-107230","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.264Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a4aaad5f8605964caa249eb4edb7d0b4"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nThe fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that request as the first one.\n\n1. **A login with no configured principal.** Kerberos and SPNEGO against the ticket cache or the default JAAS login, which is the usual deployment, leave the realm's principal unset, and the key stayed unscoped in that case. A request to the same host that carries no credentials at all draws the authenticated socket and is served as the service identity.\n2. **The proxy realm.** Only the origin realm went into the key. A connection authenticated to a proxy with NTLM or Negotiate is handed to requests of another proxy identity, or of none, and the proxy acts for them as the first identity.\n3. **Identities that share a user name.** Only the principal string went into the key, so `CORP\\alice` and `OTHER\\alice` shared connections, as did two realms differing only in ","public_affected_ranges":[">= 3.0.0, < 3.0.14"]},{"certainty":"source_listed","source_ids":["sr-a4aaad5f8605964caa249eb4edb7d0b4"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nThe fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that request as the first one.\n\n1. **A login with no configured principal.** Kerberos and SPNEGO against the ticket cache or the default JAAS login, which is the usual deployment, leave the realm's principal unset, and the key stayed unscoped in that case. A request to the same host that carries no credentials at all draws the authenticated socket and is served as the service identity.\n2. **The proxy realm.** Only the origin realm went into the key. A connection authenticated to a proxy with NTLM or Negotiate is handed to requests of another proxy identity, or of none, and the proxy acts for them as the first identity.\n3. **Identities that share a user name.** Only the principal string went into the key, so `CORP\\alice` and `OTHER\\alice` shared connections, as did two realms differing only in ","public_affected_ranges":[">= 2.0.0, <= 2.16.1"]}],"null_published_at":"2026-11-02T20:21:07.737Z","source_updated_at":"2026-10-08T16:49:47.000Z","source_disclosed_at":"2026-10-08T16:49:46.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-01T00:58:38.867Z"},{"id":"NVI-00012094","kind":"vulnerability","title":"AsyncHttpClient: Pooled connections can still be shared across NTLM, Negotiate and proxy logins","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-v2j5-22fr-j62r","CVE-2026-107230"],"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-097079c83585a51f98bf6b0587e2df9e"],"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-10-08T16:49:47.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-a4aaad5f8605964caa249eb4edb7d0b4"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.188%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.08489. Missing scores are unknown.","source_id":"sr-097079c83585a51f98bf6b0587e2df9e"}],"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-a4aaad5f8605964caa249eb4edb7d0b4","url":"https://github.com/advisories/GHSA-v2j5-22fr-j62r","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-v2j5-22fr-j62r","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:38.867Z"},{"id":"sr-097079c83585a51f98bf6b0587e2df9e","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-107230","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.065Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a4aaad5f8605964caa249eb4edb7d0b4"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nThe fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that request as the first one.\n\n1. **A login with no configured principal.** Kerberos and SPNEGO against the ticket cache or the default JAAS login, which is the usual deployment, leave the realm's principal unset, and the key stayed unscoped in that case. A request to the same host that carries no credentials at all draws the authenticated socket and is served as the service identity.\n2. **The proxy realm.** Only the origin realm went into the key. A connection authenticated to a proxy with NTLM or Negotiate is handed to requests of another proxy identity, or of none, and the proxy acts for them as the first identity.\n3. **Identities that share a user name.** Only the principal string went into the key, so `CORP\\alice` and `OTHER\\alice` shared connections, as did two realms differing only in ","public_affected_ranges":[">= 3.0.0, < 3.0.14"]},{"certainty":"source_listed","source_ids":["sr-a4aaad5f8605964caa249eb4edb7d0b4"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nThe fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that request as the first one.\n\n1. **A login with no configured principal.** Kerberos and SPNEGO against the ticket cache or the default JAAS login, which is the usual deployment, leave the realm's principal unset, and the key stayed unscoped in that case. A request to the same host that carries no credentials at all draws the authenticated socket and is served as the service identity.\n2. **The proxy realm.** Only the origin realm went into the key. A connection authenticated to a proxy with NTLM or Negotiate is handed to requests of another proxy identity, or of none, and the proxy acts for them as the first identity.\n3. **Identities that share a user name.** Only the principal string went into the key, so `CORP\\alice` and `OTHER\\alice` shared connections, as did two realms differing only in ","public_affected_ranges":[">= 2.0.0, <= 2.16.1"]}],"null_published_at":"2026-11-01T14:34:14.095Z","source_updated_at":"2026-10-08T16:49:47.000Z","source_disclosed_at":"2026-10-08T16:49:46.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-01T00:58:38.867Z"},{"id":"NVI-00012094","kind":"vulnerability","title":"AsyncHttpClient: Pooled connections can still be shared across NTLM, Negotiate and proxy logins","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-v2j5-22fr-j62r","CVE-2026-107230"],"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-a4aaad5f8605964caa249eb4edb7d0b4"],"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-10-08T16:49:47.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-a4aaad5f8605964caa249eb4edb7d0b4"}],"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-a4aaad5f8605964caa249eb4edb7d0b4","url":"https://github.com/advisories/GHSA-v2j5-22fr-j62r","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-v2j5-22fr-j62r","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:38.867Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a4aaad5f8605964caa249eb4edb7d0b4"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nThe fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that request as the first one.\n\n1. **A login with no configured principal.** Kerberos and SPNEGO against the ticket cache or the default JAAS login, which is the usual deployment, leave the realm's principal unset, and the key stayed unscoped in that case. A request to the same host that carries no credentials at all draws the authenticated socket and is served as the service identity.\n2. **The proxy realm.** Only the origin realm went into the key. A connection authenticated to a proxy with NTLM or Negotiate is handed to requests of another proxy identity, or of none, and the proxy acts for them as the first identity.\n3. **Identities that share a user name.** Only the principal string went into the key, so `CORP\\alice` and `OTHER\\alice` shared connections, as did two realms differing only in ","public_affected_ranges":[">= 3.0.0, < 3.0.14"]},{"certainty":"source_listed","source_ids":["sr-a4aaad5f8605964caa249eb4edb7d0b4"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nThe fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that request as the first one.\n\n1. **A login with no configured principal.** Kerberos and SPNEGO against the ticket cache or the default JAAS login, which is the usual deployment, leave the realm's principal unset, and the key stayed unscoped in that case. A request to the same host that carries no credentials at all draws the authenticated socket and is served as the service identity.\n2. **The proxy realm.** Only the origin realm went into the key. A connection authenticated to a proxy with NTLM or Negotiate is handed to requests of another proxy identity, or of none, and the proxy acts for them as the first identity.\n3. **Identities that share a user name.** Only the principal string went into the key, so `CORP\\alice` and `OTHER\\alice` shared connections, as did two realms differing only in ","public_affected_ranges":[">= 2.0.0, <= 2.16.1"]}],"null_published_at":"2026-11-01T01:03:56.630Z","source_updated_at":"2026-10-08T16:49:47.000Z","source_disclosed_at":"2026-10-08T16:49:46.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-01T00:58:38.867Z"}],"next_cursor":null,"snapshot_revision":"42594"}