Search

Find a vulnerability

Search criteria

    Related vulnerabilities

    BREW-BUMP-MY-VERSION-CVE… (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 18:58 – Updated: 2026-10-26 09:35 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "bump-my-version",
            "purl": "pkg:brew/bump-my-version"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "1.4.0"
                },
                {
                  "fixed": "1.5.1_1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-bump-my-version-CVE-2026-84379",
      "modified": "2026-10-26T09:35:16Z",
      "published": "2026-09-10T18:58:22Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-HATCH-CVE-2026-84379 (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 19:26 – Updated: 2026-10-23 09:20 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "hatch",
            "purl": "pkg:brew/hatch"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "1.17.0"
                },
                {
                  "fixed": "1.18.0_1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-hatch-CVE-2026-84379",
      "modified": "2026-10-23T09:20:47Z",
      "published": "2026-09-10T19:26:02Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-HERMES-AGENT-CVE-20… (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-10-04 11:46 – Updated: 2026-10-27 17:56 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.12.0",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "hermes-agent",
            "purl": "pkg:brew/hermes-agent"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0.21.6"
                },
                {
                  "fixed": "0.22.2"
                }
              ],
              "type": "ECOSYSTEM"
            },
            {
              "events": [
                {
                  "introduced": "2026.8.31_1"
                },
                {
                  "last_affected": "2026.9.24"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.12.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.12.0"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-hermes-agent-CVE-2026-84379",
      "modified": "2026-10-27T17:56:27Z",
      "published": "2026-10-04T11:46:48Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-HTTPX2-CVE-2026-84379 (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 19:29 – Updated: 2026-11-18 10:12 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "httpx2",
            "purl": "pkg:brew/httpx2"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "2.9.1"
                },
                {
                  "fixed": "2.11.0"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.2",
            "name": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.2"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-httpx2-CVE-2026-84379",
      "modified": "2026-11-18T10:12:49Z",
      "published": "2026-09-10T19:29:23Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-LITECLI-CVE-2026-84379 (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 19:42 – Updated: 2026-10-12 17:50 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.13.1",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "litecli",
            "purl": "pkg:brew/litecli"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "1.17.1_3"
                },
                {
                  "fixed": "1.17.1_4"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.13.1",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.13.1"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-litecli-CVE-2026-84379",
      "modified": "2026-10-12T17:50:02Z",
      "published": "2026-09-10T19:42:52Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-OTERM-CVE-2026-84379 (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 20:19 – Updated: 2026-10-23 08:59 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "oterm",
            "purl": "pkg:brew/oterm"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0.19.0"
                },
                {
                  "fixed": "0.24.0"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-oterm-CVE-2026-84379",
      "modified": "2026-10-23T08:59:58Z",
      "published": "2026-09-10T20:19:31Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-PAPIS-CVE-2026-84379 (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 20:21 – Updated: 2026-11-14 11:55 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "papis",
            "purl": "pkg:brew/papis"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0.15.0_5"
                },
                {
                  "fixed": "0.16.0"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-papis-CVE-2026-84379",
      "modified": "2026-11-14T11:55:47Z",
      "published": "2026-09-10T20:21:27Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-RAPID-MLX-CVE-2026-84379 (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 20:37 – Updated: 2026-11-19 10:42 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.2",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "rapid-mlx",
            "purl": "pkg:brew/rapid-mlx"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0.11.3"
                },
                {
                  "fixed": "0.12.15"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.2",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.2"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-rapid-mlx-CVE-2026-84379",
      "modified": "2026-11-19T10:42:42Z",
      "published": "2026-09-10T20:37:33Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-STRANDS-AGENTS-SOPS… (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 21:05 – Updated: 2026-11-15 10:04 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "strands-agents-sops",
            "purl": "pkg:brew/strands-agents-sops"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "1.1.3"
                },
                {
                  "fixed": "1.1.3_1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-strands-agents-sops-CVE-2026-84379",
      "modified": "2026-11-15T10:04:58Z",
      "published": "2026-09-10T21:05:20Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    BREW-YEWTUBE-CVE-2026-84379 (GHSA-H4X7-GW46-3WM6)

    Vulnerability from osv_homebrew – Published: 2026-09-10 21:31 – Updated: 2026-10-04 22:23 – Source website
    VLAI
    Summary
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Details

    Summary

    HTTPX2 serializes the per-file Content-Type and custom headers supplied through the files= tuple API directly into the multipart/form-data body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.

    Details

    The three-element file tuple accepts (filename, content, content_type), and the four-element form accepts (filename, content, content_type, headers). FileField.render_headers() interpolates the supplied header names and values between CRLF delimiters without validating them.

    For example:

    import httpx2
    
    request = httpx2.Request(
        "POST",
        "https://example.com/upload",
        headers={"Content-Type": "multipart/form-data; boundary=BOUNDARY"},
        files={
            "file": (
                "safe.txt",
                b"payload",
                "text/plain\r\nX-Injected: true",
            )
        },
    )
    
    print(request.read().decode())
    

    The generated body contains an attacker-injected part header:

    --BOUNDARY
    Content-Disposition: form-data; name="file"; filename="safe.txt"
    Content-Type: text/plain
    X-Injected: true
    
    payload
    --BOUNDARY--
    

    The same issue affects names and values in the custom header mapping from the four-element tuple.

    Field names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.

    Impact

    Applications are affected when they pass attacker-controlled upload metadata into the per-file content_type or custom headers arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.

    This does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.

    Mitigation

    Upgrade to HTTPX2 2.11.0 or later. Patched versions reject forbidden control characters in multipart part header names and values and raise ValueError before serializing the request.

    If upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.13.1",
            "upstream_fixed_in": "2.11.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "yewtube",
            "purl": "pkg:brew/yewtube"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "2.13.1_4"
                },
                {
                  "fixed": "2.13.1_5"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.13.1",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.13.1"
          }
        ]
      },
      "details": "### Summary\n\nHTTPX2 serializes the per-file `Content-Type` and custom headers supplied through the `files=` tuple API directly into the `multipart/form-data` body without validating custom header names or values. An attacker who can influence upload metadata passed to HTTPX2 can use CR or LF characters to terminate a multipart part header and inject additional part headers or end the part header block early.\n\n### Details\n\nThe three-element file tuple accepts `(filename, content, content_type)`, and the four-element form accepts `(filename, content, content_type, headers)`. `FileField.render_headers()` interpolates the supplied header names and values between CRLF delimiters without validating them.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n    \"POST\",\n    \"https://example.com/upload\",\n    headers={\"Content-Type\": \"multipart/form-data; boundary=BOUNDARY\"},\n    files={\n        \"file\": (\n            \"safe.txt\",\n            b\"payload\",\n            \"text/plain\\r\\nX-Injected: true\",\n        )\n    },\n)\n\nprint(request.read().decode())\n```\n\nThe generated body contains an attacker-injected part header:\n\n```text\n--BOUNDARY\nContent-Disposition: form-data; name=\"file\"; filename=\"safe.txt\"\nContent-Type: text/plain\nX-Injected: true\n\npayload\n--BOUNDARY--\n```\n\nThe same issue affects names and values in the custom header mapping from the four-element tuple.\n\nField names and filenames are serialized through a separate escaping path and do not permit CRLF header injection.\n\n### Impact\n\nApplications are affected when they pass attacker-controlled upload metadata into the per-file `content_type` or custom `headers` arguments. The receiving server interprets injected lines as genuine multipart part headers. Depending on how that server validates and processes uploads, this can alter part semantics or bypass checks based on part headers.\n\nThis does not split the outer HTTP request: the injected headers are contained within the multipart body. The concrete security impact therefore depends on the downstream multipart parser and application behavior.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions reject forbidden control characters in multipart part header names and values and raise `ValueError` before serializing the request.\n\nIf upgrading is not immediately possible, applications should validate custom multipart header names as HTTP field-name tokens. They should reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL in per-file content types and custom header values before passing them to HTTPX2.",
      "id": "BREW-yewtube-CVE-2026-84379",
      "modified": "2026-10-04T22:23:47Z",
      "published": "2026-09-10T21:31:39Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84379"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1142"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers",
      "upstream": [
        "GHSA-h4x7-gw46-3wm6",
        "CVE-2026-84379",
        "PYSEC-2026-3848"
      ]
    }

    CVE-2026-84379 (GCVE-0-2026-84379)

    Vulnerability from cvelistv5 – Published: 2026-09-02 17:57 – Updated: 2026-09-02 18:20
    VLAI
    Title
    HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
    Summary
    HTTPX2 is a next generation HTTP client for Python. Prior to 2.11.0, FileField.render_headers() in src/httpx2/httpx2/_multipart.py directly interpolates attacker-controlled content_type values and custom headers from the files= three-element (filename, content, content_type) tuple and the files= four-element (filename, content, content_type, headers) tuple into multipart/form-data part headers without validating header names or values. CR or LF characters can terminate a part header, inject additional part headers, or end the part header block early, allowing a downstream multipart parser to treat attacker-supplied lines as genuine headers and potentially alter part semantics or bypass header-based checks. This issue is fixed in version 2.11.0.
    SSVC
    Exploitation: poc Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-09-02 18:20 UTC
    CWE
    • CWE-93 - Improper Neutralization of CRLF Sequences ('CRLF Injection')
    Assigner
    GitHub_M CNA
    Impacted products
    Vendor Product Version
    pydantic httpx2 Affected: < 2.11.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-84379",
                    "options": [
                      {
                        "Exploitation": "poc"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-09-02T18:20:04.628894Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-09-02T18:20:46.599Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "references": [
              {
                "tags": [
                  "exploit"
                ],
                "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
              }
            ],
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "httpx2",
              "vendor": "pydantic",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 2.11.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "HTTPX2 is a next generation HTTP client for Python. Prior to 2.11.0, FileField.render_headers() in src/httpx2/httpx2/_multipart.py directly interpolates attacker-controlled content_type values and custom headers from the files= three-element (filename, content, content_type) tuple and the files= four-element (filename, content, content_type, headers) tuple into multipart/form-data part headers without validating header names or values. CR or LF characters can terminate a part header, inject additional part headers, or end the part header block early, allowing a downstream multipart parser to treat attacker-supplied lines as genuine headers and potentially alter part semantics or bypass header-based checks. This issue is fixed in version 2.11.0."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "LOW",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-93",
                  "description": "CWE-93: Improper Neutralization of CRLF Sequences (\u0027CRLF Injection\u0027)",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-09-02T17:57:17.092Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6"
            },
            {
              "name": "https://github.com/pydantic/httpx2/pull/1142",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/pydantic/httpx2/pull/1142"
            },
            {
              "name": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d"
            },
            {
              "name": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
            }
          ],
          "source": {
            "advisory": "GHSA-h4x7-gw46-3wm6",
            "discovery": "UNKNOWN"
          },
          "title": "HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-84379",
        "datePublished": "2026-09-02T17:57:17.092Z",
        "dateReserved": "2026-09-01T16:27:58.130Z",
        "dateUpdated": "2026-09-02T18:20:46.599Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }