May Queue Project develops a specialized message-queueing system, with the observed vulnerability footprint centered on its core May Queue product. The durable signal reflects concurrency and memory-management issues characteristic of queue implementations, with recurring weaknesses in improper synchronization and out-of-bounds writes. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by May Queue Project over time
Signals from CVEs in this vendor scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-36217MEDIUM 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. | Jan 26, 2021 | 5.9 | 20 | NO | NO |
Signals from CVEs in this vendor scope (1 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by May Queue Project.
Media articles that mention a CVE ID that affects a product developed by May Queue Project — matched by CVE ID, not by vendor name.