CVE-2018-6596

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 2.6%, top 16% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

webhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the WEBHOOK_AUTHORIZATION secret, which allows remote attackers to post arbitrary e-mail tracking events.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

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
Severity91% × 45%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
84%
KEV
Not listed

Published

February 3, 2018

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Jul 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_commit, github_release.
github_release Patch Available

v1.2.1

Patch available: anymail/django-anymail v1.2.1

https://github.com/anymail/django-anymail/releases/tag/v1.2.1
github_commit Patch Available

commit db586ede1fbb (anymail/django-anymail)

Patch available: anymail/django-anymail v6.0.1 (contains commit db586ede1fbb)

https://github.com/anymail/django-anymail/commit/db586ede1fbb41dce21310ea28ae15a1cf1286c5
github_commit

commit c07998304b4a (anymail/django-anymail)

Fix landed in anymail/django-anymail commit c07998304b4a — awaiting tagged release

https://github.com/anymail/django-anymail/commit/c07998304b4a31df4c61deddcb03d3607a04691b
generic Patch Available🔴 Active Exploitation

#889450 - django-anymail: CVE-2018-6596: Security issue with timing attack on WEBHOOK_AUTHORIZATION - Debian Bug report logs

https://bugs.debian.org/889450
generic

[SECURITY] [DSA 4107-1] django-anymail security update

https://www.debian.org/security/2018/dsa-4107
github_release Patch Available

v1.3

Patch available: anymail/django-anymail v1.3

https://github.com/anymail/django-anymail/releases/tag/v1.3

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
django-anymail—1.3-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
django-anymail—1.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
django-anymail—1.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
django-anymail—1.3-1—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
django-anymail0.6.1-1, 0.7-1, 0.8-1, 0.8-20.8-2+deb9u1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
django-anymail0.1 ... 1.2 (22 versions)1.2.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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.

Showing the most recent 100 of 137 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2018-6596?
CVE-2018-6596 is a critical vulnerability published on February 3, 2018. webhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the WEBHOOK_AUTHORIZATION secret, which allows remote attackers to post arbitrary e-mail tracking events.
When was CVE-2018-6596 disclosed?
CVE-2018-6596 was first published in the National Vulnerability Database on February 3, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-6596 actively exploited?
CVE-2018-6596 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 15.6% of all scored CVEs.
What is the CVSS score of CVE-2018-6596?
CVE-2018-6596 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2018-6596?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6596, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-6596

Explore →

Is Your Infrastructure Affected by CVE-2018-6596?

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

Start Free Scan →Browse All CVEs