Django 4.2 is end-of-life: it no longer receives security fixes, so move to 5.2 LTS
No CISA KEV additions and no High-or-above vendor advisories for your versions were published in the window; the one live risk is Django 4.2 being end-of-life. nginx and AWS had no qualifying items: the only in-window nginx advisory is vendor-rated medium, so I excluded it. Assumed 'nginx' means open-source nginx.org releases and 'AWS' means the AWS Security Bulletins page.
The 30-second version
Django 4.2 is end-of-life since April 7, 2026; plan the move to 5.2 LTS.
AWS pgcollection RCE (CVE-2026-96883) does not affect RDS; only self-compiled copies need 2.1.2.
No KEV entries touched your stack; Python 3.11 stays security-supported until October 2027.
01Breaking releases and EOL – Django · Apr 7
Django 4.2 LTS no longer gets security fixes
Django's download page lists 4.2 LTS under unsupported releases, with extended support having ended April 7, 2026 and 4.2.30 as the last release. Django's own security archive lists four fixes dated Aug 4, 2026 (CVE-2026-15307 server-side file write and request forgery via spatial lookups, CVE-2026-15337, CVE-2026-15830, CVE-2026-15920 admin XSS). I did not open the advisory text, so whether 4.2 is technically affected is unverified; since it is unsupported, assume no patch will ship.
Exploitation status: none known for these. Severity: Django's archive gives no CVSS; not yet verified.
For your stack: upgrade to Django 5.2 LTS (supported through April 2028) or buy vendor extended support; confirm your exact 4.2.x in use.
AWS pgcollection RCE does not hit RDS, only self-built copies
AWS bulletin 2026-118-AWS (published Sep 24, 2026, rated 'Important') covers CVE-2026-96883, a type confusion in the open-source pgcollection PostgreSQL extension. An authenticated database user could crash the backend or execute arbitrary code. Affected: pgcollection v2.0.0 through v2.1.1; fixed in 2.1.2. No CVSS is given (not yet scored). Exploitation: none known.
AWS states existing RDS for PostgreSQL and Aurora PostgreSQL are not impacted because they ship only version 1.1.1. No workaround exists.
For your stack: RDS needs no action; if you compiled pgcollection 2.0.0–2.1.1 on EC2 or elsewhere, upgrade to 2.1.2 now.
Python 3.11 remains security-only, EOL scheduled October 2027
The Python developer guide lists 3.11 in 'security' status with end of life scheduled for October 2027 (scheduled dates can be adjusted). Python 3.10 reached end of life on 2026-10-01, which matters if any tooling or images still run it.
Security-only means source releases as needed and no new binaries, so patched builds depend on your distro or your own builds.
For your stack: no action now; put 3.12 or 3.13 on the 2027 roadmap and confirm nothing in your fleet still runs 3.10.