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.8% (58th 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

Also known asEUVD-2026-5249 (ENISA EUVD) · GHSA-gvg8-93h5-g6qq (GitHub Security Advisories) · PYSEC-2026-46 (OSV.dev)Source: ENISA EUVD

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.8%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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 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.8%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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(12)

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
pipDjango @ 6.0.2 (fixes >= 6.0a1, < 6.0.2)—ghsa
pipDjango @ 5.2.11 (fixes >= 5.2a1, < 5.2.11)—ghsa
pipDjango @ 4.2.28 (fixes >= 4.2a1, < 4.2.28)—ghsa

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

(7 across 7 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
py3-django—
  • every version up to 4.2.28-r0: fixed in 4.2.28-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-django—
  • every version up to 4.2.28-r0: fixed in 4.2.28-r0
—
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 7× in last 7d / 33× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 199 rows 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. None are among the latest 100 rows. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  2. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  3. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  4. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  5. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  6. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  7. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  8. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  9. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  10. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  11. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  12. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  13. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-gvg8-93h5-g6qq · GitHub severity HIGH
  14. 2026-11-01 07:59 UTCEchelonGraph re-scored
  15. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  16. 2026-10-31 09:25 UTCOSV refresh
  17. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  18. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  21. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  23. 2026-10-25 14:49 UTCEchelonGraph re-scored
  24. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  25. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
Show 75 more
  1. 2026-10-23 06:58 UTCEchelonGraph re-scored
  2. 2026-10-23 06:58 UTCVendor advisory
  3. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  4. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  5. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  6. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  7. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  8. 2026-10-18 05:04 UTCEchelonGraph re-scored
  9. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  10. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  12. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-10-12 16:36 UTCEchelonGraph re-scored
  15. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-10-11 20:12 UTCEchelonGraph re-scored
  17. 2026-10-11 18:24 UTCEchelonGraph re-scored
  18. 2026-10-11 14:57 UTCEchelonGraph re-scored
  19. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  20. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  21. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  22. 2026-10-08 18:04 UTCOSV refresh
  23. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  24. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  25. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  26. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  27. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  29. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  30. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  31. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  32. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  33. 2026-09-18 23:42 UTCOSV refresh
  34. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  35. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  36. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  37. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  38. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  39. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  40. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  41. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  42. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  43. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  44. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  45. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  46. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  47. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  48. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  49. 2026-08-31 03:32 UTCOSV refresh
  50. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  51. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  52. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  53. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  54. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  55. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  56. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  57. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  58. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  59. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  60. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  61. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  62. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  63. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  64. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  65. 2026-08-14 11:35 UTCEchelonGraph re-scored
  66. 2026-08-14 11:35 UTCVendor advisory
  67. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  68. 2026-08-13 03:45 UTCEchelonGraph re-scored
  69. 2026-08-13 03:45 UTCVendor advisory
  70. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  71. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  72. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.8% · 51st percentile
  73. 2026-08-09 16:05 UTCEchelonGraph re-scored
  74. 2026-08-09 16:05 UTCVendor advisory
  75. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.8% · 51st 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.8% probability of exploitation in the next 30 days (58th 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