---
title: "Django 2.2.9 release notes"
version: 4.1
locale: pl
source: https://docs.djangoproject.com/pl/4.1/releases/2.2.9/
canonical: https://djangodocs.dev/pl/4.1/releases/2.2.9/
---
# Django 2.2.9 release notes

*December 18, 2019*

Django 2.2.9 fixes a security issue and a data loss bug in 2.2.8.

## CVE-2019-19844: Potential account hijack via password reset form

By submitting a suitably crafted email address making use of Unicode
characters, that compared equal to an existing user email when lower-cased for
comparison, an attacker could be sent a password reset token for the matched
account.

In order to avoid this vulnerability, password reset requests now compare the
submitted email using the stricter, recommended algorithm for case-insensitive
comparison of two identifiers from [Unicode Technical Report 36, section
2.11.2(B)(2)](https://www.unicode.org/reports/tr36/#Recommendations_General). Upon a match, the email containing the reset token will be
sent to the email address on record rather than the submitted address.

## Poprawki błędów

- Fixed a data loss possibility in
  [`SplitArrayField`](/pl/4.1/ref/contrib/postgres/forms/#django.contrib.postgres.forms.SplitArrayField). When using with
  `ArrayField(BooleanField())`, all values after the first `True` value
  were marked as checked instead of preserving passed values ([#31073](https://code.djangoproject.com/ticket/31073)).