Improper Validation of Syntactic Correctness of Input Affecting satellite/iop-vmaas-rhel9 package, versions *


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.18% (8th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-SATELLITEIOPVMAASRHEL9-17732754
  • published30 Jun 2026
  • disclosed22 Jun 2026

Introduced: 22 Jun 2026

CVE-2026-53537  (opens in a new tab)
CWE-1286  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 satellite/iop-vmaas-rhel9.

NVD Description

Note: Versions mentioned in the description apply only to the upstream satellite/iop-vmaas-rhel9 package and not the satellite/iop-vmaas-rhel9 package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, parse_options_header parsed Content-Disposition (and Content-Type) headers with email.message.Message, which transparently applies RFC 2231/5987 decoding. The extended parameter syntax (filename*=charset'lang'value, name*=..., and the filename0/filename1 continuation form) is decoded and surfaced under the bare filename/name key, and overrides the plain parameter when both are present. RFC 7578 §4.2 explicitly forbids the filename* form in multipart/form-data. Components that follow RFC 7578, or that do not implement RFC 2231/5987 decoding for multipart/form-data (WAFs, proxies, gateways), may interpret such a header differently. An attacker can exploit that difference to smuggle a different field name or filename past an upstream inspector to the backend. This vulnerability is fixed in 0.0.30.

CVSS Base Scores

version 3.1