{"items":[{"id":"NVI-00013989","kind":"vulnerability","title":"HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pf96-p4fj-6566","CVE-2026-84380"],"plain_summary":"GitHub lists this reviewed advisory for httpx2. 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-04d260d561d3aa97dd5ab995d56e7352"],"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-08T20:46:28.000Z","value":"5.6 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-2d7535a8c7590bef61fbe42936ffff57"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.221%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.1276. Missing scores are unknown.","source_id":"sr-04d260d561d3aa97dd5ab995d56e7352"}],"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-2d7535a8c7590bef61fbe42936ffff57","url":"https://github.com/advisories/GHSA-pf96-p4fj-6566","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pf96-p4fj-6566","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:20:31.767Z"},{"id":"sr-04d260d561d3aa97dd5ab995d56e7352","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-84380","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:45:16.083Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2d7535a8c7590bef61fbe42936ffff57"],"technology":"httpx2","known_exclusions":[],"conditions_summary":"### Summary\n\nHTTPX2 can automatically add a `Content-Length` header to a request that already contains a caller-supplied `Transfer-Encoding` header. The resulting HTTP/1.1 request contains both framing headers, which can create an ambiguous message boundary and enable request smuggling or connection desynchronization when processed by intermediaries that disagree about which header takes precedence.\n\n### Details\n\nWhen a request body has a known size, HTTPX2's content encoder returns a default `Content-Length`. `Request._prepare()` applies each default header with `setdefault()`, which only checks whether that same header is already present. It does not check whether the mutually exclusive `Transfer-Encoding` header is present.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"http://example.com/\",\n    headers={\"Transfer-Encoding\": \"chunked\"},\n    content=b\"test 123\",\n)\n\nprint(request.headers)\n```\n\nThe request contains both:\n\n```text\nTransfer-Encoding: chunked\nContent-Length: 8\n```\n\nOn an HTTP/1.1 connection, the body is serialized using chunked transfer coding while both headers are sent on the wire. This violates HTTP message-framing requirements. ","public_affected_ranges":["< 2.11.0"]}],"null_published_at":"2026-11-04T10:04:41.544Z","source_updated_at":"2026-09-08T20:46:28.000Z","source_disclosed_at":"2026-09-08T20:46:28.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-02T02:20:31.767Z"},{"id":"NVI-00013989","kind":"vulnerability","title":"HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pf96-p4fj-6566","CVE-2026-84380"],"plain_summary":"GitHub lists this reviewed advisory for httpx2. 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-06e1c69cb45f6d705a6bfd8d897b2d21"],"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-08T20:46:28.000Z","value":"5.6 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-2d7535a8c7590bef61fbe42936ffff57"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.221%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.12712. Missing scores are unknown.","source_id":"sr-06e1c69cb45f6d705a6bfd8d897b2d21"}],"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-2d7535a8c7590bef61fbe42936ffff57","url":"https://github.com/advisories/GHSA-pf96-p4fj-6566","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pf96-p4fj-6566","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:20:31.767Z"},{"id":"sr-06e1c69cb45f6d705a6bfd8d897b2d21","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-84380","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:17:01.143Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2d7535a8c7590bef61fbe42936ffff57"],"technology":"httpx2","known_exclusions":[],"conditions_summary":"### Summary\n\nHTTPX2 can automatically add a `Content-Length` header to a request that already contains a caller-supplied `Transfer-Encoding` header. The resulting HTTP/1.1 request contains both framing headers, which can create an ambiguous message boundary and enable request smuggling or connection desynchronization when processed by intermediaries that disagree about which header takes precedence.\n\n### Details\n\nWhen a request body has a known size, HTTPX2's content encoder returns a default `Content-Length`. `Request._prepare()` applies each default header with `setdefault()`, which only checks whether that same header is already present. It does not check whether the mutually exclusive `Transfer-Encoding` header is present.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"http://example.com/\",\n    headers={\"Transfer-Encoding\": \"chunked\"},\n    content=b\"test 123\",\n)\n\nprint(request.headers)\n```\n\nThe request contains both:\n\n```text\nTransfer-Encoding: chunked\nContent-Length: 8\n```\n\nOn an HTTP/1.1 connection, the body is serialized using chunked transfer coding while both headers are sent on the wire. This violates HTTP message-framing requirements. ","public_affected_ranges":["< 2.11.0"]}],"null_published_at":"2026-11-03T17:49:15.013Z","source_updated_at":"2026-09-08T20:46:28.000Z","source_disclosed_at":"2026-09-08T20:46:28.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-02T02:20:31.767Z"},{"id":"NVI-00013989","kind":"vulnerability","title":"HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pf96-p4fj-6566","CVE-2026-84380"],"plain_summary":"GitHub lists this reviewed advisory for httpx2. 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-2d7535a8c7590bef61fbe42936ffff57"],"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-08T20:46:28.000Z","value":"5.6 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-2d7535a8c7590bef61fbe42936ffff57"}],"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-2d7535a8c7590bef61fbe42936ffff57","url":"https://github.com/advisories/GHSA-pf96-p4fj-6566","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pf96-p4fj-6566","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:20:31.767Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2d7535a8c7590bef61fbe42936ffff57"],"technology":"httpx2","known_exclusions":[],"conditions_summary":"### Summary\n\nHTTPX2 can automatically add a `Content-Length` header to a request that already contains a caller-supplied `Transfer-Encoding` header. The resulting HTTP/1.1 request contains both framing headers, which can create an ambiguous message boundary and enable request smuggling or connection desynchronization when processed by intermediaries that disagree about which header takes precedence.\n\n### Details\n\nWhen a request body has a known size, HTTPX2's content encoder returns a default `Content-Length`. `Request._prepare()` applies each default header with `setdefault()`, which only checks whether that same header is already present. It does not check whether the mutually exclusive `Transfer-Encoding` header is present.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"http://example.com/\",\n    headers={\"Transfer-Encoding\": \"chunked\"},\n    content=b\"test 123\",\n)\n\nprint(request.headers)\n```\n\nThe request contains both:\n\n```text\nTransfer-Encoding: chunked\nContent-Length: 8\n```\n\nOn an HTTP/1.1 connection, the body is serialized using chunked transfer coding while both headers are sent on the wire. This violates HTTP message-framing requirements. ","public_affected_ranges":["< 2.11.0"]}],"null_published_at":"2026-11-02T10:00:37.194Z","source_updated_at":"2026-09-08T20:46:28.000Z","source_disclosed_at":"2026-09-08T20:46:28.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-02T02:20:31.767Z"}],"next_cursor":null,"snapshot_revision":"42594"}