CVE-2026-1287

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.9% (57th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. FilteredRelation is subject to SQL injection in column aliases via control characters, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to QuerySet methods annotate(), aggregate(), extra(), values(), values_list(), and alias(). Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Solomon Kebede for reporting this issue.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

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 (value × EchelonGraph’s weight)
Severity54% × 45%
The EG Score, 5.4 of 10.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 3, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 3, 2026
Patch available.
Web page

Django security releases issued: 6.0.2, 5.2.11, and 4.2.28 | Weblog | Django

https://www.djangoproject.com/weblog/2026/feb/03/security-releases/
Web page
https://groups.google.com/g/django-announce
Web page

Archive of security issues | Django documentation | Django

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

Vendor Advisories for CVE-2026-1287(10)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-django (3:4.2.11-1ubuntu1.14) @ noble2026-06-07ubuntu
redhatpython3.12-django-0:4.2.30-1.el9pc2026-05-07redhat
redhatsatellite/iop-advisor-backend-rhel9:17734510752026-03-31redhat
redhatyggdrasil-worker-forwarder-0:0.0.3-4.el9sat2026-03-26redhat
redhatpython-django-0:4.2.28-0.1.el9pc2026-03-26redhat
redhatpython3.12-django-0:4.2.28-1.el9ap2026-03-06redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17722146302026-03-06redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17725527882026-03-06redhat
redhatdiscovery/discovery-server-rhel9:17709135972026-02-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-django2:2.2.24-1 ... 2:2.2.28-1~deb11u9 (14 versions)
  • every version up to 2:2.2.28-1~deb11u12: fixed in 2:2.2.28-1~deb11u12
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:3.2.19-1 ... 3:3.2.25-0+deb12u1 (8 versions)
  • every version up to 3:3.2.25-0+deb12u2: fixed in 3:3.2.25-0+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:4.2.23-1 ... 3:4.2.27-2 (8 versions)
  • every version up to 3:4.2.28-0+deb13u1: fixed in 3:4.2.28-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:4.2.23-1 ... 3:4.2.27-2 (7 versions)
  • every version up to 3:4.2.28-1: fixed in 3:4.2.28-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
django4.2 ... 6.0.1 (41 versions)
  • 6.0a1 up to 6.0.2: fixed in 6.0.2
  • 5.2a1 up to 5.2.11: fixed in 5.2.11
  • 4.2a1 up to 4.2.28: fixed in 4.2.28
  • 4.2 up to 4.2.28: fixed in 4.2.28
  • 5.2 up to 5.2.11: fixed in 5.2.11
  • 6.0 up to 6.0.2: fixed in 6.0.2
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 158 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 63 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  3. 2026-10-12 16:36 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  5. 2026-10-11 20:12 UTCEG score recompute
  6. 2026-10-11 18:24 UTCEG score recompute
  7. 2026-10-11 14:57 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-10-08 18:04 UTCOSV refresh
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  18. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  20. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  22. 2026-09-18 23:42 UTCOSV refresh
  23. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  24. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  25. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.8% · 54th percentile
Show 70 more
  1. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  2. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  3. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  4. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  5. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  6. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  7. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  8. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  9. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  10. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  11. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  12. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  13. 2026-08-31 03:32 UTCOSV refresh
  14. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  15. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  16. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  17. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  18. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  19. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  20. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  21. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  22. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  23. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  24. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  25. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  26. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  27. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  28. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  29. 2026-08-14 11:35 UTCEG score recompute
  30. 2026-08-14 11:35 UTCVendor advisory
  31. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  32. 2026-08-13 03:45 UTCEG score recompute
  33. 2026-08-13 03:45 UTCVendor advisory
  34. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  35. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  36. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  37. 2026-08-09 16:05 UTCEG score recompute
  38. 2026-08-09 16:05 UTCVendor advisory
  39. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  40. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  41. 2026-08-07 22:56 UTCEG score recompute
  42. 2026-08-07 22:56 UTCVendor advisory
  43. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  44. 2026-08-06 04:29 UTCEG score recompute
  45. 2026-08-06 04:29 UTCVendor advisory
  46. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  47. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  48. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  49. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  50. 2026-08-02 21:37 UTCEG score recompute
  51. 2026-08-02 21:37 UTCVendor advisory
  52. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  53. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  54. 2026-07-31 00:50 UTCOSV refresh
  55. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  56. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  57. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  58. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  59. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  60. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  61. 2026-07-23 03:05 UTCEG score recompute
  62. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  63. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  64. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  65. 2026-07-19 14:31 UTCEPSS rescoreEPSS 0.8% · 50th percentile
  66. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.8% · 50th percentile
  67. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.8% · 50th percentile
  68. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.8% · 50th percentile
  69. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.8% · 50th percentile
  70. 2026-07-15 02:00 UTCEPSS rescoreEPSS 0.8% · 50th percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-1287?
CVE-2026-1287 is a medium-severity vulnerability; its CVE record was published on February 3, 2026. An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. FilteredRelation is subject to SQL injection in column aliases via control characters, using a suitably crafted dictionary, with dictionary expansion, as the kwargs passed to QuerySet methods annotate(),…
When was CVE-2026-1287 made public?
CVE-2026-1287 was made public on February 3, 2026: that is the date its CVE record's CNA, Django Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on February 3, 2026. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-1287 actively exploited?
CVE-2026-1287 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-1287?
CVE-2026-1287 has a CVSS v3.1 base score of 5.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-1287?
A fix for CVE-2026-1287 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-1287 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-1287

Explore →

Is Your Infrastructure Affected by CVE-2026-1287?

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

Book a Demo →Browse All CVEs