CVE-2025-22239
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedArbitrary event injection on Salt Master. The master's "_minion_event" method can be used by and authorized minion to send arbitrary events onto the master's event bus.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Salt Master's '_minion_event' method lacks proper authorization controls, allowing any authenticated minion to inject arbitrary events onto the master's event bus. This enables a compromised or malicious authorized minion to publish events they should not be permitted to send.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Salt Master is runningRun 'ps aux | grep salt-master' or 'systemctl status salt-master' to confirm the Salt Master process is activeAffected if Salt Master process is running and the system uses Salt for management
-
Check Salt Master versionRun 'salt-master --version' or 'salt --version' to determine the installed versionAffected if The installed version is unpatched and falls within the vulnerable version range for CVE-2025-22239
-
Verify minion authentication is enabledInspect the Salt Master configuration file (typically /etc/salt/master) for 'acl' or 'auth' settings, or run 'salt-run acl.show' if availableAffected if Minion authentication is configured and minions are permitted to authenticate to the master
-
Confirm the _minion_event method is accessibleCheck Salt Master logs for events from minions using the _minion_event method, or review the master's event system configuration in the master config fileAffected if Authenticated minions can communicate with the master's event bus and send events
-
Review minion trust policiesExamine /etc/salt/master for 'minion_data_cache', 'auth_mode', and 'peer' settings to understand which minions are permitted to send eventsAffected if Untrusted or compromised minions are authorized to connect to the Salt Master
If you run a Salt Master with unpatched Salt version and allow authenticated minions to connect, a compromised minion can inject arbitrary events onto the master's event bus.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Salt to the patched version containing the authorization fix. Additionally, review minion authentication policies and consider network segmentation to limit exposure of the Salt Master event bus to only trusted minions.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22239 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data