https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 12:58:52 +0000 https://cve.radiocsirt.org/vuln/brew-cycode-cve-2026-42561 <p><strong>Affected:</strong> Homebrew: cycode</p> <p>### Summary</p> <p>`python-multipart` has a denial of service vulnerability in multipart part header parsing. When parsing `multipart/form-data`, `MultipartParser` previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.</p> <p>### Impact</p> <p>Applications that parse attacker-controlled `multipart/form-data` with affected versions of `python-multipart` can experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invoke `python-multipart` may have worker or event-loop delays while processing malicious upload requests.</p> <p>### Details</p> <p>The affected parser states are `HEADER_FIELD_START`, `HEADER_FIELD`, `HEADER_VALUE_START`, `HEADER_VALUE`, and `HEADER_VALUE_ALMOST_DONE`. The issue can be triggered by:</p> <p>- A multipart part with an oversized individual header value. - A multipart part with many repeated header lines or an unterminated header block.</p> <p>Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.</p> <p>### Mitigation</p> <p>Upgrade to `python-multipart` `0.0.27` or later.</p> <p>If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of `python-…</p> <p><strong>Affected:</strong> Homebrew: cycode</p> <p>### Summary</p> <p>`python-multipart` has a denial of service vulnerability in multipart part header parsing. When parsing `multipart/form-data`, `MultipartParser` previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.</p> <p>### Impact</p> <p>Applications that parse attacker-controlled `multipart/form-data` with affected versions of `python-multipart` can experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invoke `python-multipart` may have worker or event-loop delays while processing malicious upload requests.</p> <p>### Details</p> <p>The affected parser states are `HEADER_FIELD_START`, `HEADER_FIELD`, `HEADER_VALUE_START`, `HEADER_VALUE`, and `HEADER_VALUE_ALMOST_DONE`. The issue can be triggered by:</p> <p>- A multipart part with an oversized individual header value. - A multipart part with many repeated header lines or an unterminated header block.</p> <p>Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.</p> <p>### Mitigation</p> <p>Upgrade to `python-multipart` `0.0.27` or later.</p> <p>If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of `python-…</p> https://cve.radiocsirt.org/vuln/brew-cycode-cve-2026-42561 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1094 certfr-2026-avi-1094 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1094 https://cve.radiocsirt.org/vuln/cleanstart-2026-az09261 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: airflow-3</p> <p>Multiple security vulnerabilities affect the airflow-3 package. These issues are resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: airflow-3</p> <p>Multiple security vulnerabilities affect the airflow-3 package. These issues are resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-az09261 https://cve.radiocsirt.org/vuln/euvd-2026-349237 EUVD-2026-349237 https://cve.radiocsirt.org/vuln/euvd-2026-349237 https://cve.radiocsirt.org/vuln/fkie_cve-2026-42561 <p>Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.27, python-multipart has a denial of service vulnerability in multipart part header parsing. When parsing multipart/form-data, MultipartParser previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion. This vulnerability is fixed in 0.0.27.</p> <p>Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.27, python-multipart has a denial of service vulnerability in multipart part header parsing. When parsing multipart/form-data, MultipartParser previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion. This vulnerability is fixed in 0.0.27.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-42561 https://cve.radiocsirt.org/vuln/ghsa-pp6c-gr5w-3c5g <p><strong>Affected:</strong> PyPI: python-multipart</p> <p>### Summary</p> <p>`python-multipart` has a denial of service vulnerability in multipart part header parsing. When parsing `multipart/form-data`, `MultipartParser` previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.</p> <p>### Impact</p> <p>Applications that parse attacker-controlled `multipart/form-data` with affected versions of `python-multipart` can experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invoke `python-multipart` may have worker or event-loop delays while processing malicious upload requests.</p> <p>### Details</p> <p>The affected parser states are `HEADER_FIELD_START`, `HEADER_FIELD`, `HEADER_VALUE_START`, `HEADER_VALUE`, and `HEADER_VALUE_ALMOST_DONE`. The issue can be triggered by:</p> <p>- A multipart part with an oversized individual header value. - A multipart part with many repeated header lines or an unterminated header block.</p> <p>Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.</p> <p>### Mitigation</p> <p>Upgrade to `python-multipart` `0.0.27` or later.</p> <p>If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of `python-…</p> <p><strong>Affected:</strong> PyPI: python-multipart</p> <p>### Summary</p> <p>`python-multipart` has a denial of service vulnerability in multipart part header parsing. When parsing `multipart/form-data`, `MultipartParser` previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.</p> <p>### Impact</p> <p>Applications that parse attacker-controlled `multipart/form-data` with affected versions of `python-multipart` can experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invoke `python-multipart` may have worker or event-loop delays while processing malicious upload requests.</p> <p>### Details</p> <p>The affected parser states are `HEADER_FIELD_START`, `HEADER_FIELD`, `HEADER_VALUE_START`, `HEADER_VALUE`, and `HEADER_VALUE_ALMOST_DONE`. The issue can be triggered by:</p> <p>- A multipart part with an oversized individual header value. - A multipart part with many repeated header lines or an unterminated header block.</p> <p>Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.</p> <p>### Mitigation</p> <p>Upgrade to `python-multipart` `0.0.27` or later.</p> <p>If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of `python-…</p> https://cve.radiocsirt.org/vuln/ghsa-pp6c-gr5w-3c5g https://cve.radiocsirt.org/vuln/opensuse-su-2026:10797-1 <p>python311-python-multipart-0.0.28-1.1 on GA media</p> <p>python311-python-multipart-0.0.28-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10797-1 https://cve.radiocsirt.org/vuln/pysec-2026-3039 <p><strong>Affected:</strong> PyPI: python-multipart</p> <p>### Summary</p> <p>`python-multipart` has a denial of service vulnerability in multipart part header parsing. When parsing `multipart/form-data`, `MultipartParser` previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.</p> <p>### Impact</p> <p>Applications that parse attacker-controlled `multipart/form-data` with affected versions of `python-multipart` can experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invoke `python-multipart` may have worker or event-loop delays while processing malicious upload requests.</p> <p>### Details</p> <p>The affected parser states are `HEADER_FIELD_START`, `HEADER_FIELD`, `HEADER_VALUE_START`, `HEADER_VALUE`, and `HEADER_VALUE_ALMOST_DONE`. The issue can be triggered by:</p> <p>- A multipart part with an oversized individual header value. - A multipart part with many repeated header lines or an unterminated header block.</p> <p>Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.</p> <p>### Mitigation</p> <p>Upgrade to `python-multipart` `0.0.27` or later.</p> <p>If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of `python-…</p> <p><strong>Affected:</strong> PyPI: python-multipart</p> <p>### Summary</p> <p>`python-multipart` has a denial of service vulnerability in multipart part header parsing. When parsing `multipart/form-data`, `MultipartParser` previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion.</p> <p>### Impact</p> <p>Applications that parse attacker-controlled `multipart/form-data` with affected versions of `python-multipart` can experience CPU exhaustion. ASGI applications using Starlette, FastAPI, or other frameworks that invoke `python-multipart` may have worker or event-loop delays while processing malicious upload requests.</p> <p>### Details</p> <p>The affected parser states are `HEADER_FIELD_START`, `HEADER_FIELD`, `HEADER_VALUE_START`, `HEADER_VALUE`, and `HEADER_VALUE_ALMOST_DONE`. The issue can be triggered by:</p> <p>- A multipart part with an oversized individual header value. - A multipart part with many repeated header lines or an unterminated header block.</p> <p>Both variants are addressed by enforcing default parser limits for maximum header count and maximum header size.</p> <p>### Mitigation</p> <p>Upgrade to `python-multipart` `0.0.27` or later.</p> <p>If upgrading is not immediately possible, reduce exposure by enforcing request body size limits at the server, proxy, or framework layer. This is only a mitigation; affected versions of `python-…</p> https://cve.radiocsirt.org/vuln/pysec-2026-3039 https://cve.radiocsirt.org/vuln/rhsa-2026:37275 <p>golang: net/url: Memory exhaustion in query parameter parsing in net/url aiohttp: AIOHTTP&#39;s HTTP Parser auto_decompress feature is vulnerable to zip bomb keras: Keras: Arbitrary Code Execution Vulnerability Bypassing Safe Mode mlflow: mlflow: Arbitrary file read via bypassed source path validation python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite pyasn1: pyasn1: Denial of Service due to memory exhaustion from malformed RELATIVE-OID vllm: vLLM: Remote code execution due to hardcoded trust_remote_code setting multipart: denial of service via maliciously crafted HTTP or multipart segment headers python-dotenv: python-dotenv: Arbitrary file overwrite via symbolic link following pyasn1: pyasn1 Vulnerable to Denial of Service via Unbounded Recursion tornado-python: Tornado: Denial of Service via large multipart bodies pyjwt: PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation) simpleeval: SimpleEval: Arbitrary code execution via sandbox escape due to improper object handling google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation nltk: NLTK: Denial of Service via unauthenticated remote shutdown nltk: NLTK: Arbitrary file overwrite and creation via path traversal in XML index files react-router: React Route…</p> <p>golang: net/url: Memory exhaustion in query parameter parsing in net/url aiohttp: AIOHTTP&#39;s HTTP Parser auto_decompress feature is vulnerable to zip bomb keras: Keras: Arbitrary Code Execution Vulnerability Bypassing Safe Mode mlflow: mlflow: Arbitrary file read via bypassed source path validation python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite pyasn1: pyasn1: Denial of Service due to memory exhaustion from malformed RELATIVE-OID vllm: vLLM: Remote code execution due to hardcoded trust_remote_code setting multipart: denial of service via maliciously crafted HTTP or multipart segment headers python-dotenv: python-dotenv: Arbitrary file overwrite via symbolic link following pyasn1: pyasn1 Vulnerable to Denial of Service via Unbounded Recursion tornado-python: Tornado: Denial of Service via large multipart bodies pyjwt: PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation) simpleeval: SimpleEval: Arbitrary code execution via sandbox escape due to improper object handling google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation nltk: NLTK: Denial of Service via unauthenticated remote shutdown nltk: NLTK: Arbitrary file overwrite and creation via path traversal in XML index files react-router: React Route…</p> https://cve.radiocsirt.org/vuln/rhsa-2026:37275 https://cve.radiocsirt.org/vuln/suse-su-2026:21999-1 <p>Security update for python-python-multipart</p> <p>Security update for python-python-multipart</p> https://cve.radiocsirt.org/vuln/suse-su-2026:21999-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-42561 <p><strong>Affected:</strong> Ubuntu:Pro:22.04:LTS: python-multipart, Ubuntu:Pro:24.04:LTS: python-multipart, Ubuntu:25.10: python-multipart, Ubuntu:26.04:LTS: python-multipart</p> <p>Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.27, python-multipart has a denial of service vulnerability in multipart part header parsing. When parsing multipart/form-data, MultipartParser previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion. This vulnerability is fixed in 0.0.27.</p> <p><strong>Affected:</strong> Ubuntu:Pro:22.04:LTS: python-multipart, Ubuntu:Pro:24.04:LTS: python-multipart, Ubuntu:25.10: python-multipart, Ubuntu:26.04:LTS: python-multipart</p> <p>Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.27, python-multipart has a denial of service vulnerability in multipart part header parsing. When parsing multipart/form-data, MultipartParser previously had no limit on the number of part headers or the size of an individual part header. An attacker could send a request with either many repeated headers without terminating the header block or a single very large header value, causing excessive CPU work before request rejection or completion. This vulnerability is fixed in 0.0.27.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-42561 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3046 <p>Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3046