Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 3 May 2023 15:27:32 +0200
From: Mariusz Felisiak <>
Subject: Django: CVE-2023-31047 Potential bypass of validation when uploading
 multiple files using one form field

In accordance with `our security release policy
<>`_, the 
Django team
is issuing
`Django 4.2.1 <>`_,
`Django 4.1.9 <>`_, and
`Django 3.2.19 <>`_.
These releases addresses the security issue detailed below. We encourage all
users of Django to upgrade as soon as possible.

CVE-2023-31047: Potential bypass of validation when uploading multiple 
files using one form field

Uploading multiple files using one form field has never been supported by
``forms.FileField`` or ``forms.ImageField`` as only the last
uploaded file was validated. Unfortunately, `Uploading multiple files 
topic suggested otherwise.

In order to avoid the vulnerability, ``ClearableFileInput``
and `FileInput`` form widgets now raise ``ValueError`` when
the ``multiple`` HTML attribute is set on them. To prevent the exception and
keep the old behavior, set ``allow_multiple_selected`` to ``True``.

For more details on using the new attribute and handling of multiple files
through a single field, see `Uploading multiple files 

Thanks Moataz Al-Sharida and nawaik for reports.

This issue has severity "low" according to the Django security policy.

Affected supported versions

* Django main branch
* Django 4.2
* Django 4.1
* Django 3.2


Patches to resolve the issue have been applied to Django's main branch 
and the
4.2, 4.1, and 3.2 release branches. The patches may be obtained from the
following changesets:

* On the `main branch 
* On the `4.2 release branch 
* On the `4.1 release branch 
* On the `3.2 release branch 

The following releases have been issued:

* Django 4.2.1 (`download Django 4.2.1 
<>`_ | 
`4.2.1 checksums 
* Django 4.1.9 (`download Django 4.1.9 
<>`_ | 
`4.1.9 checksums 
* Django 3.2.19 (`download Django 3.2.19 
<>`_ | 
`3.2.19 checksums 

The PGP key ID used for this release is Mariusz Felisiak: 
`2EF56372BA48CD1B <>`_.

General notes regarding security reporting

As always, we ask that potential security issues be reported via
private email to ````, and not via Django's
Trac instance or the django-developers list. Please see `our security
policies <>`_ for further

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.