Skip to content
Noroxi
CVE-2025-22241· NVD / CVE Program· CNA vmware

CVE-2025-22241 salt advisory

File contents overwrite the VirtKey class is called when “on-demand pillar” data is requested and uses un-validated input to create paths to the “pki directory”. The functionality is used to auto-accept Minion authentication keys based on a pre-placed “authorization file” at a specific location and is present in the default configuration.

MediumCVSS 5.6 · v3.1—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Jun 13, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 7th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · vmware
5.6
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.

  • VMware SALT

    • 3006.x and later · before 3006.12affected · lts
    • 3007.x and later · before 3007.4affected · sts

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Leap 15.6salt-testbefore 3006.0-150500.4.55.13006.0-150500.4.55.1
openSUSE:Tumbleweedsaltbefore 3006.0-41.13006.0-41.1
PyPIsaltfrom 3006.0rc1 · before 3006.123006.12
PyPIsaltfrom 3007.0rc1 · before 3007.43007.4
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepybefore 3.11.11-1.32.13.11.11-1.32.1
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-corebefore 3.11.11-1.32.13.11.11-1.32.1
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-cythonbefore 0.29.37-1.12.20.29.37-1.12.2
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-jinja2before 3.1.2-1.12.23.1.2-1.12.2
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-lxmlbefore 4.9.4-1.21.14.9.4-1.21.1
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-m2cryptobefore 0.45.1-1.12.10.45.1-1.12.1
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-msgpackbefore 1.0.7-1.14.11.0.7-1.14.1
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-plybefore 3.11-1.8.13.11-1.8.1
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-tornadobefore 6.3.2-1.12.26.3.2-1.12.2
SUSE:EL-9:Update:Products:SaltBundle:Updatesaltbundlepy-zypp-pluginbefore 0.6.5-1.11.10.6.5-1.11.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSsaltbefore 3006.0-150300.53.94.13006.0-150300.53.94.1
SUSE:Linux Enterprise Micro 5.3saltbefore 3006.0-150400.8.80.13006.0-150400.8.80.1
SUSE:Linux Enterprise Micro 5.5saltbefore 3006.0-150500.4.55.13006.0-150500.4.55.1
SUSE:Linux Enterprise Micro 5.5saltbefore 3006.0-150500.4.55.13006.0-150500.4.55.1
SUSE:Linux Enterprise Module for Systems Management 15 SP7saltbefore 3006.0-150700.14.5.23006.0-150700.14.5.2
SUSE:Linux Micro 6.0saltbefore 3006.0-13.13006.0-13.1
SUSE:Linux Micro 6.1saltbefore 3006.0-slfo.1.1_4.13006.0-slfo.1.1_4.1
SUSE:Manager Client Tools 12venv-salt-minionbefore 3006.0-3.76.23006.0-3.76.2
SUSE:Manager Client Tools 15venv-salt-minionbefore 3006.0-150000.3.78.13006.0-150000.3.78.1
SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLSvenv-salt-minionbefore 3006.0-1.59.13006.0-1.59.1

+2

Other highest-scoring records for the same primary product.

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
VMware SALT3006.12Vendor (CNA)
VMware SALT3007.4Vendor (CNA)
opensuse:salt3006.0-150500.4.55.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:salt-test3006.0-150500.4.55.1 · openSUSE:Leap 15.6Package registry (OSV)
PyPI:salt3006.12Package registry (OSV)
PyPI:salt3007.4Package registry (OSV)
suse:release-notes-susemanager4.3.16-150400.3.140.1 · SUSE:Manager Server 4.3Package registry (OSV)
suse:release-notes-susemanager-proxy4.3.16-150400.3.98.1 · SUSE:Manager Proxy 4.3Package registry (OSV)
suse:salt3006.0-150500.4.55.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:saltbundlepy3.11.11-1.32.1 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:saltbundlepy-core3.11.11-1.32.1 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:saltbundlepy-cython0.29.37-1.12.2 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:saltbundlepy-jinja23.1.2-1.12.2 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:saltbundlepy-lxml4.9.4-1.21.1 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:saltbundlepy-m2crypto0.45.1-1.12.1 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:saltbundlepy-msgpack1.0.7-1.14.1 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:saltbundlepy-ply3.11-1.8.1 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:saltbundlepy-tornado6.3.2-1.12.2 · SUSE:EL-9:Update:Products:SaltBundle:UpdatePackage registry (OSV)
suse:venv-salt-minion3006.0-1.59.1 · SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records