CVE-2020-17495: django-celery-results through 1.2.1 stores task results in the database

Q: How do I fix CVE-2020-17495?

django-celery-results: upgrade to newer than 1.2.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-17495 being exploited?

CVE-2020-17495 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-17495 affect?

CVE-2020-17495 affects django-celery-results. Severity is high (CVSS 7.5). django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the dat

Q: How urgent is CVE-2020-17495?

Priority 46/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2020-17495 is a high-severity flaw (CVSS 7.5) affecting django-celery-results. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-312
Published	2020-08-11
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: django-celery-results project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-08-11 21:15 UTCPublished CVE record published
2026-06-17 02:59 UTCUpdated Record last modified

django-celery-results project django-celery-results UPGRADE

Affected: <= 1.2.1

Fixed in: newer than 1.2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy django-celery-results || rpm -q django-celery-results || django-celery-results --version

2. UPGRADE to newer than 1.2.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django-celery-results

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django-celery-results

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-17495?

django-celery-results: upgrade to newer than 1.2.1. Exact commands for each OS are on this page.

Is CVE-2020-17495 being exploited?

CVE-2020-17495 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-17495 affect?

CVE-2020-17495 affects django-celery-results. Severity is high (CVSS 7.5). django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the dat

How urgent is CVE-2020-17495?

Priority 46/100. High severity; Remotely exploitable, no login, no user action

Software pages

Django vulnerabilities

References

← Back to latest CVEs