No. Junglewise Threat Intelligence has no report of CVE-2021-25282 being exploited in the wild.
How severe is CVE-2021-25282?
Low severity, with a CVSS score of 3.1, published 27 February 2021.
Which products and versions are affected?
salt (PyPI) ECOSYSTEM:introduced=0,fixed=2015.8.10,introduced=2015.8.11,fixed=2015.8.13,introduced=2016.3.0,fixed=2016.3.4,introduced=2016.3.5,fixed=2016.3.6,introduced=2016.3.7,fixed=2016.3.8,introduced=2016.11.0,fixed=2016.11.3,introduced=2016.11.4,fixed=2016.11.5,introduced=2016.11.7,fixed=2016.11.10,introduced=2017.7.0,fixed=2017.7.8,introduced=2018.3.0rc1,fixed=2019.2.0rc1,introduced=2019.2.0,fixed=2019.2.5,introduced=2019.2.6,fixed=2019.2.8,introduced=3000,fixed=3000.6,introduced=3001,fixed=3001.4,introduced=3002,fixed=3002.5, ECOSYSTEM:introduced=0,fixed=2015.8.13.
Is there a fix for CVE-2021-25282?
Yes. salt (PyPI): upgrade to 2015.8.13, 3002.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-25282?
Check whether you run salt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
salt (PyPI): upgrade to 2015.8.13, 3002.5 or later
pip install "salt>=3002.5"
Affected products
salt (PyPI) ECOSYSTEM:introduced=0,fixed=2015.8.10,introduced=2015.8.11,fixed=2015.8.13,introduced=2016.3.0,fixed=2016.3.4,introduced=2016.3.5,fixed=2016.3.6,introduced=2016.3.7,fixed=2016.3.8,introduced=2016.11.0,fixed=2016.11.3,introduced=2016.11.4,fixed=2016.11.5,introduced=2016.11.7,fixed=2016.11.10,introduced=2017.7.0,fixed=2017.7.8,introduced=2018.3.0rc1,fixed=2019.2.0rc1,introduced=2019.2.0,fixed=2019.2.5,introduced=2019.2.6,fixed=2019.2.8,introduced=3000,fixed=3000.6,introduced=3001,fixed=3001.4,introduced=3002,fixed=3002.5, ECOSYSTEM:introduced=0,fixed=2015.8.13