Sign in Sign up
JA · EN · FR
SecPulse
Categories
SUSE-SU-2026:1740-1

Security update for python-Django

Summary

Vulnerability reported (SUSE-SU-2026:1740-1). Risk of unauthorized operations or information disclosure. Exploitable via ASGIRequest.

Original description

The description as published by the source.

This update for python-Django fixes the following issues

  • CVE-2026-3902: headers spoofing by exploiting an ambiguous mapping of two header variants in ASGIRequest requests
    (bsc#1261729).
  • CVE-2026-4277: permissions on inline model instances were not validated on submission of forged POST data in
    GenericInlineModelAdmin (bsc#1261731).
  • CVE-2026-4292: admin changelist forms using ModelAdmin.list_editable incorrectly allowed new instances to be created
    via forged POST data (bsc#1261732).
  • CVE-2026-5766: potential denial-of-service vulnerability in ASGI requests via file upload limit bypass (bsc#1264153).
  • CVE-2026-6907: potential exposure of private data due to incorrect handling of Vary: * in UpdateCacheMiddleware
    (bsc#1264152).
  • CVE-2026-33033: denial of service via missing or understated Content-Length header in ASGI requests (bsc#1261722).
  • CVE-2026-33034: ASGI requests with a missing or understated Content-Length header could bypass the
    DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body (bsc#1261724).
  • CVE-2026-35192: session fixation via public cached pages and SESSION_SAVE_EVERY_REQUEST (bsc#1264154).

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as SUSE-SU-2026:1740-1 has been found.
Attackers can target a specific entry point like ASGIRequest over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SUSE-SU-2026:1740-1" on the vendor's site.

SUSE-SU-2026:1740-1
Attack surface: ASGIRequest / UpdateCacheMiddleware / DATA_UPLOAD_MAX_MEMORY_SIZE / SESSION_SAVE_EVERY_REQUEST
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) has been reported. Attackers reach the vulnerable code path via ASGIRequest.

📍 Affected scope

Check the vendor advisory for the affected versions. Attack surface: ASGIRequest / UpdateCacheMiddleware / DATA_UPLOAD_MAX_MEMORY_SIZE / SESSION_SAVE_EVERY_REQUEST.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details