CVE-2026-87975

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-10-06. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.3Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18. django.forms.models.BaseModelFormSet.save_existing_objects() used the presence of a primary key on a submitted form's instance as evidence that the instance belonged to the formset's limiting queryset. An object outside that queryset is represented by a newly constructed instance whose primary key can still be populated from submitted data when the model's primary key is a field accepted by the form, such as a OneToOneField or parent link used as the primary key of an inline formset's model, or a natural or UUID primary key included in the form's fields. This allows an authenticated user permitted to submit such a formset to delete rows outside the limiting queryset, without any permission on the targeted object, via forged management-form data marking an out-of-queryset object for deletion. Models using the default AutoField primary key are not affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Seonggwon Yoon for reporting this issue.

CVSS v3
4.3
EG Score
4.3MEDIUMhigh confidence
EG Risk
19
EG Risk 19/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 6, 2026

Last Modified

October 6, 2026

Advisory Details (7)

Auto-updated Oct 6, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

Django security releases issued: 6.1.2, 6.0.9, and 5.2.18 | Weblog | Django

https://www.djangoproject.com/weblog/2026/oct/06/security-releases/
github_commit

commit ff27883ca055 (django/django)

Fix landed in django/django commit ff27883ca055 — awaiting tagged release

https://github.com/django/django/commit/ff27883ca055aa9ab23015b50674a5b10dfe5a41
github_commit

commit b83ab92bc547 (django/django)

Fix landed in django/django commit b83ab92bc547 — awaiting tagged release

https://github.com/django/django/commit/b83ab92bc5474558b083a840ea4628b3261b2cfe
github_commit

commit cce6c57ed30e (django/django)

Fix landed in django/django commit cce6c57ed30e — awaiting tagged release

https://github.com/django/django/commit/cce6c57ed30ea83725f9d6abb2fe5ee932bab107
github_commit

commit 83cbd21be574 (django/django)

Fix landed in django/django commit 83cbd21be574 — awaiting tagged release

https://github.com/django/django/commit/83cbd21be57483e6b3eb6e4688a561c841aff75e
generic

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/dev/releases/security/

Vendor Advisories for CVE-2026-87975(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-10 19:26 UTCEG score recompute
  3. 2026-10-10 19:26 UTCGHSA enrichment
  4. 2026-10-09 20:07 UTCEPSS rescore
  5. 2026-10-09 18:17 UTCEG score recompute
  6. 2026-10-09 18:17 UTCGHSA enrichment
  7. 2026-10-08 17:13 UTCEPSS rescore
  8. 2026-10-08 17:09 UTCEG score recompute
  9. 2026-10-08 17:09 UTCGHSA enrichment
  10. 2026-10-07 23:48 UTCEPSS rescore
  11. 2026-10-07 16:01 UTCEG score recompute
  12. 2026-10-07 16:01 UTCGHSA enrichment
  13. 2026-10-06 14:30 UTCEG score recompute
  14. 2026-10-06 14:00 UTCEG score recompute
  15. 2026-10-06 13:40 UTCEG score recompute
  16. 2026-10-06 13:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87975?
CVE-2026-87975 is a medium vulnerability published on October 6, 2026. An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18. django.forms.models.BaseModelFormSet.saveexistingobjects() used the presence of a primary key on a submitted form's instance as evidence that the instance belonged to the formset's limiting queryset. An…
When was CVE-2026-87975 disclosed?
CVE-2026-87975 was first published on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87975 actively exploited?
CVE-2026-87975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87975?
CVE-2026-87975 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87975?
An upstream fix for CVE-2026-87975 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-87975 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-87975

Explore →

Is Your Infrastructure Affected by CVE-2026-87975?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.