per page, with , order by , clip by
Results of 1 - 10 of about 70 for affected (0.001 sec.)
Django 5.2.15 release notes — Django 6.1 ドキュメント 11095
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.15 release notes ¶ June 3, 2026 Django 5.2.15 fixes five security issues with severity "low" in 5.2.14. CVE-2026-6873: Signed cookie salt ... derivation. For backwards compatibility, cookies signed by older Django versions are accepted until Django 2028. Projects affected by the above ambiguity should set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject older cookies immediately. This is ... , as used by send_mail() and BrokenLinkEmailsMiddleware , among others. Connections configured with EMAIL_USE_SSL are not affected. This issue has severity "low" according to the Django security policy . CVE-2026-8404: Potential exposure of private data ... using mixed or uppercase values (e.g. Private ). The cache_control() decorator and patch_cache_control() function were not affected, since they normalize directives to lowercase. This issue only affects responses where Cache-Control is set manually. This ...
https://man.mtool.work/django/6.1/releases/5.2.15.html
Django 5.2.15 release notes — Django 6.1 ドキュメント 10925
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.15 release notes ¶ June 3, 2026 Django 5.2.15 fixes five security issues with severity "low" in 5.2.14. CVE-2026-6873: Signed cookie salt ... derivation. For backwards compatibility, cookies signed by older Django versions are accepted until Django 2028. Projects affected by the above ambiguity should set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject older cookies immediately. This is ... , as used by send_mail() and BrokenLinkEmailsMiddleware , among others. Connections configured with EMAIL_USE_SSL are not affected. This issue has severity "low" according to the Django security policy . CVE-2026-8404: Potential exposure of private data ... using mixed or uppercase values (e.g. Private ). The cache_control() decorator and patch_cache_control() function were not affected, since they normalize directives to lowercase. This issue only affects responses where Cache-Control is set manually. This ...
https://man.mtool.work/django/6.1/releases/5.2.15.html
Django 6.0.6 release notes — Django 6.1 ドキュメント 10925
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.0.6 release notes ¶ June 3, 2026 Django 6.0.6 fixes five security issues with severity "low" and one bug in 6.0.5. Also, the latest string ... derivation. For backwards compatibility, cookies signed by older Django versions are accepted until Django 2028. Projects affected by the above ambiguity should set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject older cookies immediately. This is ... , as used by send_mail() and BrokenLinkEmailsMiddleware , among others. Connections configured with EMAIL_USE_SSL are not affected. This issue has severity "low" according to the Django security policy . CVE-2026-8404: Potential exposure of private data ... using mixed or uppercase values (e.g. Private ). The cache_control() decorator and patch_cache_control() function were not affected, since they normalize directives to lowercase. This issue only affects responses where Cache-Control is set manually. This ...
https://man.mtool.work/django/6.1/releases/6.0.6.html
Django 5.2.16 release notes — Django 6.1 ドキュメント 10573
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.16 release notes ¶ July 7, 2026 Django 5.2.16 fixes three security issues with severity "low" in 5.2.15. CVE-2026-48588: Potential exposu ... ure of adjacent heap memory or, in rare cases, a segmentation fault. Only rasters stored in GDAL's virtual filesystem were affected. This issue has severity "low" according to the Django security policy . CVE-2026-53878: Header injection possibility sinc ... possible. Django itself wasn't vulnerable because HttpResponse prohibits newlines in HTTP headers. The vulnerability only affected uses of DomainNameValidator outside Django form fields, as CharField strips newlines by default. This issue has severity " ... security policy buffer were DomainNameValidator Cookie response cache responses request stored over read GDALRaster bytes affected injection accepted release notes July クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/5.2.16.html
Django 6.0.7 release notes — Django 6.1 ドキュメント 10235
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.0.7 release notes ¶ July 7, 2026 Django 6.0.7 fixes three security issues with severity "low" and one bug in 6.0.6. CVE-2026-48588: Potenti ... ure of adjacent heap memory or, in rare cases, a segmentation fault. Only rasters stored in GDAL's virtual filesystem were affected. This issue has severity "low" according to the Django security policy . CVE-2026-53878: Header injection possibility sinc ... possible. Django itself wasn't vulnerable because HttpResponse prohibits newlines in HTTP headers. The vulnerability only affected uses of DomainNameValidator outside Django form fields, as CharField strips newlines by default. This issue has severity " ... raised UnicodeDecodeError for bytes passwords that were not valid UTF-8. Passwords supplied as str or as UTF-8 bytes are unaffected ( #37184 ). 目次 Django 6.0.7 release notes CVE-2026-48588: Potential exposure of private data via cached Set-Cookie respo ...
https://man.mtool.work/django/6.1/releases/6.0.7.html
Django 3.0.14 リリースノート — Django 6.1 ドキュメント 9882
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.0.14 リリースノート ¶ April 6, 2021 Django 3.0.14 fixes a security issue with severity "low" in 3.0.13. CVE-2021-28658: Potential directory ... tParser allowed directory-traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability. 目次 Django 3.0.14 リリースノート CVE-2021-28658: Potential directory-traversal via uploaded files ... April fixes security issue severity Potential MultiPartParser allowed suitably crafted names Built-in upload handlers were affected vulnerability クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/3.0.14.html
Django 2.2.20 リリースノート — Django 6.1 ドキュメント 9713
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.2.20 リリースノート ¶ April 6, 2021 Django 2.2.20 fixes a security issue with severity "low" in 2.2.19. CVE-2021-28658: Potential directory ... tParser allowed directory-traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability. 目次 Django 2.2.20 リリースノート CVE-2021-28658: Potential directory-traversal via uploaded files ... April fixes security issue severity Potential MultiPartParser allowed suitably crafted names Built-in upload handlers were affected vulnerability クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/2.2.20.html
Django 3.1.8 リリースノート — Django 6.1 ドキュメント 9530
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.1.8 リリースノート ¶ April 6, 2021 Django 3.1.8 fixes a security issue with severity "low" and a bug in 3.1.7. CVE-2021-28658: Potential di ... tParser allowed directory-traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability. バグ修正 ¶ Fixed a bug in Django 3.1 where the output was hidden on a test error or failure when us ... April fixes security issue severity Potential MultiPartParser allowed suitably crafted names Built-in upload handlers were affected vulnerability バグ 修正 Fixed クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/3.1.8.html
Django 6.0.6 release notes — Django 6.1 ドキュメント 9361
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.0.6 release notes ¶ June 3, 2026 Django 6.0.6 fixes five security issues with severity "low" and one bug in 6.0.5. Also, the latest string ... derivation. For backwards compatibility, cookies signed by older Django versions are accepted until Django 2028. Projects affected by the above ambiguity should set SIGNED_COOKIE_LEGACY_SALT_FALLBACK to False to reject older cookies immediately. This is ... , as used by send_mail() and BrokenLinkEmailsMiddleware , among others. Connections configured with EMAIL_USE_SSL are not affected. This issue has severity "low" according to the Django security policy . CVE-2026-8404: Potential exposure of private data ... using mixed or uppercase values (e.g. Private ). The cache_control() decorator and patch_cache_control() function were not affected, since they normalize directives to lowercase. This issue only affects responses where Cache-Control is set manually. This ...
https://man.mtool.work/django/6.1/releases/6.0.6.html
Django 5.2.16 release notes — Django 6.1 ドキュメント 8501
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.16 release notes ¶ July 7, 2026 Django 5.2.16 fixes three security issues with severity "low" in 5.2.15. CVE-2026-48588: Potential exposu ... ure of adjacent heap memory or, in rare cases, a segmentation fault. Only rasters stored in GDAL's virtual filesystem were affected. This issue has severity "low" according to the Django security policy . CVE-2026-53878: Header injection possibility sinc ... possible. Django itself wasn't vulnerable because HttpResponse prohibits newlines in HTTP headers. The vulnerability only affected uses of DomainNameValidator outside Django form fields, as CharField strips newlines by default. This issue has severity " ...
https://man.mtool.work/django/6.1/releases/5.2.16.html
PREV 1 2 3 4 5 6 7 NEXT