MITRE marked CVE-2026-46237 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. a secondary CVSS source baseline 7.1; sources differ by 0.0.
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/vcn3: Avoid overflow on msg bound check
As pointed out by SDL, the previous condition may be vulnerable to overflow.
(cherry picked from commit db00257ac9e4a51eb2515aaea161a019f7125e10)
May 28, 2026
June 10, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
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 128 total refreshes for this CVE.
Explore the affected products and dependency analysis for CVE-2026-46237
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.