CVE-2020-36217: An issue was discovered in the may_queue crate through 2020-11-10 for Rust

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

may queue: upgrade to newer than 2020-11-10. Exact commands for each OS are on this page.

Q: Is CVE-2020-36217 being exploited?

CVE-2020-36217 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-36217 affect?

CVE-2020-36217 affects may queue. Severity is medium (CVSS 5.9). An issue was discovered in the may_queue crate through 2020-11-10 for Rust. Because Queue does not have bounds on its Send trait or Sync trait, memory corruption can occur.

Q: How urgent is CVE-2020-36217?

Priority 47/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.9REMOTEUPGRADE

CVE-2020-36217 is a medium-severity flaw (CVSS 5.9) affecting may queue. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in the may_queue crate through 2020-11-10 for Rust. Because Queue does not have bounds on its Send trait or Sync trait, memory corruption can occur.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-662, CWE-787
Published	2021-01-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: may queue project

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

Am I affected?

Timeline

2021-01-26 18:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

may queue project may queue UPGRADE

Affected: <= 2020-11-10

Fixed in: newer than 2020-11-10

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy may-queue || rpm -q may-queue || may-queue --version

2. UPGRADE to newer than 2020-11-10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade may-queue

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade may-queue

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-36217?

may queue: upgrade to newer than 2020-11-10. Exact commands for each OS are on this page.

Is CVE-2020-36217 being exploited?

CVE-2020-36217 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-36217 affect?

CVE-2020-36217 affects may queue. Severity is medium (CVSS 5.9). An issue was discovered in the may_queue crate through 2020-11-10 for Rust. Because Queue does not have bounds on its Send trait or Sync trait, memory corruption can occur.

How urgent is CVE-2020-36217?

Priority 47/100. Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs