{"items":[{"id":"NVI-00011698","kind":"vulnerability","title":"AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jmqq-x5g9-9p2w","CVE-2026-107282"],"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-2c5bfd1ef6ded685ea160f70bdc2b972"],"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-10T03:17:06.900Z","value":"9.4 CRITICAL (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-315cbab52368a220228fda88159143b4"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.189%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.08542. Missing scores are unknown.","source_id":"sr-2c5bfd1ef6ded685ea160f70bdc2b972"}],"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-04d0a6cffad813c92df049a845a7da42","url":"https://github.com/advisories/GHSA-jmqq-x5g9-9p2w","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jmqq-x5g9-9p2w","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:38.867Z"},{"id":"sr-315cbab52368a220228fda88159143b4","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-107282","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-107282","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:29.490Z"},{"id":"sr-2c5bfd1ef6ded685ea160f70bdc2b972","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-107282","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.264Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-04d0a6cffad813c92df049a845a7da42"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nWhen a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host.\n\nA replay happens through documented, ordinary features: a `ResponseFilter` that returns a different request, which is the supported failover pattern, and the IOException retry path. The attacker does not need to induce the replay; an application that uses failover produces it by design.\n\n* The socket to host B is filed in the connection pool under host A's key. A later request the application addresses to A is served over the connection to B, and A's `Authorization` header goes to B.\n* Over a CONNECT tunnel, the client tunnels to B and negotiates TLS with B correctly, then writes A's request into that tunnel. B receives A's path, A's `Host`, and A's `Authorization`. TLS does not protect against this, because the handshake really is with B, so no certificate mismatch occurs.\n* The replay reuses the original realm, so A's credentials are regenerated onto a replay request that carries no realm of it","public_affected_ranges":[">= 3.0.0, <= 3.0.12"]},{"certainty":"source_listed","source_ids":["sr-04d0a6cffad813c92df049a845a7da42"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nWhen a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host.\n\nA replay happens through documented, ordinary features: a `ResponseFilter` that returns a different request, which is the supported failover pattern, and the IOException retry path. The attacker does not need to induce the replay; an application that uses failover produces it by design.\n\n* The socket to host B is filed in the connection pool under host A's key. A later request the application addresses to A is served over the connection to B, and A's `Authorization` header goes to B.\n* Over a CONNECT tunnel, the client tunnels to B and negotiates TLS with B correctly, then writes A's request into that tunnel. B receives A's path, A's `Host`, and A's `Authorization`. TLS does not protect against this, because the handshake really is with B, so no certificate mismatch occurs.\n* The replay reuses the original realm, so A's credentials are regenerated onto a replay request that carries no realm of it","public_affected_ranges":[">= 2.0.0, <= 2.16.0"]}],"null_published_at":"2026-11-06T15:18:11.460Z","source_updated_at":"2026-10-08T16:30:47.000Z","source_disclosed_at":"2026-10-08T16:30: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-00011698","kind":"vulnerability","title":"AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jmqq-x5g9-9p2w","CVE-2026-107282"],"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-315cbab52368a220228fda88159143b4"],"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-10T03:17:06.900Z","value":"9.4 CRITICAL (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-315cbab52368a220228fda88159143b4"}],"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-04d0a6cffad813c92df049a845a7da42","url":"https://github.com/advisories/GHSA-jmqq-x5g9-9p2w","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jmqq-x5g9-9p2w","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:38.867Z"},{"id":"sr-315cbab52368a220228fda88159143b4","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-107282","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-107282","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:29.490Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-04d0a6cffad813c92df049a845a7da42"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nWhen a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host.\n\nA replay happens through documented, ordinary features: a `ResponseFilter` that returns a different request, which is the supported failover pattern, and the IOException retry path. The attacker does not need to induce the replay; an application that uses failover produces it by design.\n\n* The socket to host B is filed in the connection pool under host A's key. A later request the application addresses to A is served over the connection to B, and A's `Authorization` header goes to B.\n* Over a CONNECT tunnel, the client tunnels to B and negotiates TLS with B correctly, then writes A's request into that tunnel. B receives A's path, A's `Host`, and A's `Authorization`. TLS does not protect against this, because the handshake really is with B, so no certificate mismatch occurs.\n* The replay reuses the original realm, so A's credentials are regenerated onto a replay request that carries no realm of it","public_affected_ranges":[">= 3.0.0, <= 3.0.12"]},{"certainty":"source_listed","source_ids":["sr-04d0a6cffad813c92df049a845a7da42"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nWhen a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host.\n\nA replay happens through documented, ordinary features: a `ResponseFilter` that returns a different request, which is the supported failover pattern, and the IOException retry path. The attacker does not need to induce the replay; an application that uses failover produces it by design.\n\n* The socket to host B is filed in the connection pool under host A's key. A later request the application addresses to A is served over the connection to B, and A's `Authorization` header goes to B.\n* Over a CONNECT tunnel, the client tunnels to B and negotiates TLS with B correctly, then writes A's request into that tunnel. B receives A's path, A's `Host`, and A's `Authorization`. TLS does not protect against this, because the handshake really is with B, so no certificate mismatch occurs.\n* The replay reuses the original realm, so A's credentials are regenerated onto a replay request that carries no realm of it","public_affected_ranges":[">= 2.0.0, <= 2.16.0"]}],"null_published_at":"2026-11-03T10:03:31.391Z","source_updated_at":"2026-10-08T16:30:47.000Z","source_disclosed_at":"2026-10-08T16:30:46.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-01T00:58:38.867Z"},{"id":"NVI-00011698","kind":"vulnerability","title":"AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jmqq-x5g9-9p2w","CVE-2026-107282"],"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-04d0a6cffad813c92df049a845a7da42"],"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":[],"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-04d0a6cffad813c92df049a845a7da42","url":"https://github.com/advisories/GHSA-jmqq-x5g9-9p2w","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jmqq-x5g9-9p2w","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:38.867Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-04d0a6cffad813c92df049a845a7da42"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nWhen a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host.\n\nA replay happens through documented, ordinary features: a `ResponseFilter` that returns a different request, which is the supported failover pattern, and the IOException retry path. The attacker does not need to induce the replay; an application that uses failover produces it by design.\n\n* The socket to host B is filed in the connection pool under host A's key. A later request the application addresses to A is served over the connection to B, and A's `Authorization` header goes to B.\n* Over a CONNECT tunnel, the client tunnels to B and negotiates TLS with B correctly, then writes A's request into that tunnel. B receives A's path, A's `Host`, and A's `Authorization`. TLS does not protect against this, because the handshake really is with B, so no certificate mismatch occurs.\n* The replay reuses the original realm, so A's credentials are regenerated onto a replay request that carries no realm of it","public_affected_ranges":[">= 3.0.0, <= 3.0.12"]},{"certainty":"source_listed","source_ids":["sr-04d0a6cffad813c92df049a845a7da42"],"technology":"org.asynchttpclient:async-http-client","known_exclusions":[],"conditions_summary":"### Impact\nWhen a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host.\n\nA replay happens through documented, ordinary features: a `ResponseFilter` that returns a different request, which is the supported failover pattern, and the IOException retry path. The attacker does not need to induce the replay; an application that uses failover produces it by design.\n\n* The socket to host B is filed in the connection pool under host A's key. A later request the application addresses to A is served over the connection to B, and A's `Authorization` header goes to B.\n* Over a CONNECT tunnel, the client tunnels to B and negotiates TLS with B correctly, then writes A's request into that tunnel. B receives A's path, A's `Host`, and A's `Authorization`. TLS does not protect against this, because the handshake really is with B, so no certificate mismatch occurs.\n* The replay reuses the original realm, so A's credentials are regenerated onto a replay request that carries no realm of it","public_affected_ranges":[">= 2.0.0, <= 2.16.0"]}],"null_published_at":"2026-11-01T01:03:56.586Z","source_updated_at":"2026-10-08T16:30:47.000Z","source_disclosed_at":"2026-10-08T16:30: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"}